This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Title: Python 3.3.0rc1 release notes claims PEP-405 support, yet pysetup is not in the package (needs more usage documentation, to get pip working)
Type: Stage:
Components: Documentation Versions: Python 3.3
Status: closed Resolution:
Dependencies: Superseder:
Assigned To: docs@python Nosy List: docs@python, jcea, pas, ronaldoussoren
Priority: normal Keywords:

Created on 2012-08-27 11:41 by pas, last changed 2022-04-11 14:57 by admin. This issue is now closed.

Messages (5)
msg169194 - (view) Author: Pas (pas) Date: 2012-08-27 11:41
Python 3.3.0rc1 release notes ( ) claims PEP-405 support, yet pysetup is not in the tarball. (After reading through mailing lists and bugs it's clear that the move to "packaging" module got pulled, so it's still just distutils in there.)

There is no documentation on how to get a pyvenv (or virtualenv, or any other virtual enviroment solution) built venv to gain setuptools/pip support.
msg169195 - (view) Author: Ronald Oussoren (ronaldoussoren) * (Python committer) Date: 2012-08-27 11:53
PEP 405 is for "venv" support and that is available. Documenting how to use pip/distribute/setuptools with venv is IMHO beyond the scope of the stdlib documentation (and should be easy enough: create a virtual environment using pyvenv, then install pip using its file).

The pep mentions the pysetup script from the packaging module, but as the packaging module got pulled for python 3.3 the pysetup script is not present in the python 3.3 installation and therefore also not in venv-s.
msg169197 - (view) Author: Pas (pas) Date: 2012-08-27 12:56
It's not straightforward, at all.

# (v3.3rc1) /home/pas/wololo/pip-1.1$ python install

Traceback (most recent call last):
  File "", line 3, in <module>
    from setuptools import setup
ImportError: No module named 'setuptools'

Then, of course one can try installing setuptools, but it won't work.

Traceback (most recent call last):
  File "", line 7, in <module>
    execfile(convert_path('setuptools/command/'), d)
NameError: name 'execfile' is not defined

So, yes, venv is available. Great. But Python is not so great without those batteries, which are allegedly included.
msg169198 - (view) Author: Ronald Oussoren (ronaldoussoren) * (Python committer) Date: 2012-08-27 13:03
pyvenv won't install setuptools because setuptools is not a stdlib package. Having packaging would have been nice, but that library was not in a good enough shape for the 3.3 release.

I don't understand what you try to do in the second traceback. Installing distribute works fine though:

1) Create environment using pyvenv: $ pyenv myenv
2) Download distribute archive from PyPI
3) Extract this archive
4) Install: $ cd distribute-0.6.28; ../pyenv/bin/python install

If you have a file where you want to use the distribute package you can use distribute_setup, as described in <>. I'm using this in my own packages and this works fine with pyvenv as well.
msg169201 - (view) Author: Pas (pas) Date: 2012-08-27 14:34
Thank you. The missing detail was to install distribute when a package needs setuptools.

So, documentation. The setuptools page doesn't even mention distribute. The PEP mentions both, even though setuptools pretty much looks incompatible with Py3.3.

Anyway. I'm honestly grateful for your immediate responses. Thanks again for sorting this out, let's hope others will find this via a search engine.
Date User Action Args
2022-04-11 14:57:35adminsetgithub: 59994
2012-08-27 23:53:51jceasetnosy: + jcea
2012-08-27 14:34:56passetstatus: open -> closed

messages: + msg169201
2012-08-27 13:03:19ronaldoussorensetmessages: + msg169198
2012-08-27 12:56:08passetmessages: + msg169197
2012-08-27 11:53:20ronaldoussorensetnosy: + ronaldoussoren
messages: + msg169195
2012-08-27 11:41:36pascreate