Skip to content

drf resources#96

Closed
ghost wants to merge 1673 commits intomasterfrom
gh-pages
Closed

drf resources#96
ghost wants to merge 1673 commits intomasterfrom
gh-pages

Conversation

@ghost
Copy link
Copy Markdown

@ghost ghost commented Jun 28, 2016

No description provided.

mattmakai and others added 28 commits June 9, 2016 17:45
update Django version number accordingly
Thank you for the write-up! Following are my suggestions for corrections.

- Pin version of Pyramid to 1.7, else pip will install the latest release on PyPI. This will future-proof your instructions and make them consistent with your Required Tools.
- virtualenv and pip do not need to be installed with Python 3.5 because it now includes venv and pip. You do, however, need to update both. You'll need to update your PNG, though.
- Use `python3 -m venv` to create a virtual environment, as this is now the recommended way, although it is not yet documented, per https://bugs.python.org/issue27285
- Use proper term for a Python virtual environment. venv, virtualenv, and pyvenv (which is merely a script that wraps venv) are all implementations of a virtual environment.
- Use official, canonical URL for Pyramid docs.

Although I did not include it in this PR, I thought I would mention that Pyramid comes with three scaffolds—starter, alchemy, and zodb—the latter two of which have full tutorials at http://docs.pylonsproject.org/projects/pyramid/en/latest/tutorials/wiki2/index.html and http://docs.pylonsproject.org/projects/pyramid/en/latest/tutorials/wiki/index.html Additionally, we now have four cookiecutters that perform a similar function to the scaffolds, but go further by simplifying the entire installation process. Those are located at https://github.com/Pylons/?utf8=%E2%9C%93&query=cookiecutter
Corrections to instructions, terminology, and docs link
Update dead links in file 14-logging.markdown.
@mattmakai
Copy link
Copy Markdown
Owner

hey @mmaiasouto, thanks for the pull request! It looks like you're trying to merge the entire gh-pages branch commit history from your master branch into this gh-pages branch. Can you incorporate your changes into a clean gh-pages branch so I can take a look at what's really changing here?

@mattmakai mattmakai closed this Jun 28, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants