Removed references to Setuptools/easy_install in favor of pip. #687
Conversation
…Python user hardly needs to know that easy_install ever existed
|
Setuptools is still required for Pip to operate. I don't like how the virtualenv section was converted to Python3. |
| maintaining a project which requires Django 1.8. | ||
|
|
||
| If you are using Python 3, make sure you run something like the following (or | ||
| have it in your env variables in `~/.bashrc`): |
There was a problem hiding this comment.
To be valid reStructuredText, this should have two backticks on either side, e.g.,
in ``~/.bashrc``):
|
Setuptools is required for Pip but since users aren't directly using Setuptools in the installation section it seems ancillary. Any Setuptools discussion might better belong in the Packaging section since beginning users only need to know about pip IMHO. Anyway, I'm happy to undo that. As for the virtualenv changes, if a Python 3 user reads that section without the Python 3 information, they will get very lost. Virtualenv will appear to work but the environments will all be Python2. We need to help out users who have installed Python3 and want virtualenv to function the way the docs say it will. I've updated that change to be less vocal - let me know what you think. I still think the -p flag example should simply point to a python3 version since that is the common use case. These days more beginning people are likely to us Python 2 and 3 side by side rather than two different Python 2s. Non-beginners will understand that -p allows for any python interpreter. |
|
@adamn I think a better approach for the virtualenv section is to return it to it's previous (Python 2) state, and perhaps add a section explaining the use of the |
|
seutptools still needs to be restored to |
| You do not need to install or configure anything else to use Python. Having | ||
| said that, I would strongly recommend that you install the tools and libraries | ||
| described in the next section before you start building Python applications | ||
| for real-world use. In particular, you should always install Setuptools, as it |
There was a problem hiding this comment.
I also don't think removing setuptools here is a good idea. It's important to know about these tools, even if you aren't going to use them directly.
|
According to @dstufft, pip plans to automatically install setuptools in the future. Let's hold off on this until then. |
|
I re-instated the setuptools references. Maybe we can just try to get the Python3 Mac docs up and close this? A new ticket can be opened if/when pip automatically installs setuptools in the future. |
|
+1 |
|
This appears to require a rebase. One of these days, I intend to sit down and refactor these with Python 3 guides available as well. I have a feeling I'll start spending more time on this project very soon. Hopefully I'm right :) |
|
Should I rebase this or just delete it? |
|
i think i will merge it, with a few changes |
|
I'm also happy to rebase/update, just let me know. Otherwise, maybe we should just get this in and do other updates in another PR |
|
whatever lets me do the "merge" button easily :) |
|
"This branch has conflicts that must be resolved" |
|
I could always resolve myself, but.. you know :) |
|
are you ever going to make these changes? |
|
If there's more you need, just let me know. |
|
i made the changes myself :) |
|
thank you very much! We need to update the other two installation guides now :) |
A new Python user hardly needs to know that easy_install ever existed.
Also addresses #676 for OS X. Open to suggestions.