Mailman 3 January 2011 - Distutils-SIG

ImportError running 'test' on namespace package - other package in namespace not found
by Jason R. Coombs 17 Apr '20

17 Apr '20

I've got two projects: mynamespace.myprojectA and mynamespace.myprojectB myprojectB depends on myprojectA. I'm using setuptools 0.6c8 to manage both projects. Both projects are registered using 'setup develop'. Both projects are accessible from an interactive interpreter: PS C:\Users\me\projects> python Python 2.5.2 (r252:60911, Feb 21 2008, 13:11:45) [MSC v.1310 32 bit (Intel)] on win32 Type "help", "copyright", "credits" or "license" for more information. >>> import mynamespace.myprojectA >>> import mynamespace.myprojectB >>> from mynamespace.myprojectA import mymoduleZ However, when I run 'setup test' in myprojectB, the tests fail with File ".mymoduleZ.py", line NNN, in [some context] from mynamespace.myprojectA.mymoduleZ import MyClassC ImportError: No module named myprojectA.mymoduleZ In setup.py, the test_suite is nose.collector. I searched and couldn't find anyone else with this problem. Is this a supported configuration? Is there something I can do to make tests work with interdependent projects with the same root namespace? If there's not something obvious I should be doing differently, I'm happy to put together a minimal test case that reproduces the problem. Any suggestions are appreciated. Sincerely, Jason R. Coombs

3 6

Upgrading dependencies
by Charlie Moad 29 Apr '18

29 Apr '18

Is it currently possible to upgrade dependencies as well when upgrading a packages? If not, this would be a really nice feature to add to easy_install. Maybe a call like: easy_install --upgrade --upgrade-deps Package Obviously it makes sense to leave this off by default. Thanks, Charlie

2 1

Changes to --find-links and --upgrade in SVN
by Phillip J. Eby 29 Apr '18

29 Apr '18

Elvelind Grandin reported a problem with the "develop" command that turned out to be a flaw in its --find-links support. Specifically, it wasn't ever processing the links. :) In the process of fixing it, I wound up cleaning up an annoying (to me, at least) quirk of the previous workings of --find-links. It used to be that find-links would always be processed first, no matter what, even if you were doing a completely local operation. This would've been especially annoying if it carried over into "develop", so I made some changes. Now, if an item passed to --find-links is local (a filename or file: URL), or a direct link to an egg or other distribution, it is indexed immediately. Remote URLs are now only retrieved if a dependency can't be resolved locally, or if you use the -U or --upgrade options (this goes for "develop" too). Note that this is a behavior change for easy_install, which was effectively treating --find-links as though you'd specified --upgrade in certain cases. So, if you're used to getting upgrades downloaded as a result of using --find-links, please note that this will no longer happen. EasyInstall will now *only* go online if a dependency can't be resolved locally, if -U or --upgrade is used, or if you provided suitable direct URLs via an argument or --find-links, or via a link in a local .html file.

2 1

Problems with svn in windows
by Sharky On PTNet 29 Apr '18

29 Apr '18

Hi, I´m trying to do "easy_install setuptools==dev" in a windows box but have an error with svn command. """... 'svn' is not recognized as an internal or external command, ...""" I have installed TortoiseSVN but it seems that don't have command line, is all with the Explorer. Can you tell me what client I may use in windows? Thanks for all, Helio Pereira Sharky @ PTNet

3 2

local development scenarios
by tgreenwood 29 Apr '18

29 Apr '18

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I'm new to distutils/and the egg system. I have not researched the archives as much as I should, so please excuse me if this is familiar territory... Q: Is it possible for dependency checks to work for non pipy deployed eggs? - A.egg - B.egg (setup_requires and install_requires A.egg) - email A and B eggs to friend - tell friend to : easy_install B - but B.egg does not install A...in fact, in my test case, it fails b/c it cannot find A in pipy - in this example, what happens if friend does not have net connection on target machine? how can they install from the eggs alone and get the dep checking to work? Q: How does my friend run the unittests on the egg that they have just installed? As I am developing, I frequently run the unittests and after every bdist_egg build, I also run the unit tests that way, too. How can the consumer do the same? Q: One of my apps is a command line app, say foo.py is a command line app that takes arg1, arg2,... How can the user run this app when it is encased in an egg? Q: How do I define my own pipy? While I like the idea of deploying there for the overall community, I don't want to send my half baked code into the wild. But I'd like to try the general functionality of having a deploy site for my beta customers. How can I set this up? Thanks in advance. - -Todd -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (GNU/Linux) iD8DBQFDl9Hfz6uXX4lQc/URAnY4AJ47DFHL/cpEltmqoUyGqzhsK5FjRACgt01v akc3Wh3IOXVv2jiS8TszhuE= =Rv/x -----END PGP SIGNATURE-----

5 12

Choice of dependencies?
by John J Lee 29 Apr '18

29 Apr '18

Is it possible for a package to depend on one of several packages, with the user having the option to pick? For example, my package P might depend on package A, plus either package B or package C. I know I could (ab)use extras_require, but in my case this is a real dependency rather than an optional extra. The other option I have is to just pick one of the dependencies (B or C in my example above), and thereby force people to install it even though it's not strictly required. Neither option seems particularly attractive. John

3 6

setuptools doc patch
by John J Lee 29 Apr '18

29 Apr '18

The comma removed by the patch below implies that users working from a Subversion checkout should not use EasyInstall to periodically fetch the latest version. That's not what you intended to say, I assume? http://peak.telecommunity.com/DevCenter/setuptools You should also inform your users of the need to run this command, if they -are working from a Subversion checkout, rather than using EasyInstall to +are working from a Subversion checkout rather than using EasyInstall to periodically fetch the latest version. Hmm, probably much better than the patch above: -You should also inform your users of the need to run this command, if they -are working from a Subversion checkout, rather than using EasyInstall to -periodically fetch the latest version. +If your users are working from a Subversion checkout rather than using +EasyInstall, you should also inform them of the need to run this command +to periodically fetch the latest version. John

2 2

Re: [Distutils] distutils install probs on suse 9.0
by Mats Wichmann 29 Apr '18

29 Apr '18

At 05:43 AM 5/18/2004, David Handy wrote: >On Tue, 18 May 2004, Floris van der Tak wrote: > >> my attempt to install the distutils on suse 9.0 (which provides python >> 2.3) fails: > >Why are you installing distutils on a system that already has Python 2.3 >installed? Python 2.3 normally comes with distutils as part of the Python >standard library. > >Did suse distribute a version of Python that had distutils removed? It should come from python-devel

2 1

Sample setup.py for Numeric Python
by Greg Ward 29 Apr '18

29 Apr '18

Hi again -- [cc'd to Paul Dubois: you said you weren't following the distutils sig anymore, but this directly concerns NumPy and I'd like to get your input!] here's that sample setup.py for NumPy. See below for discussion (and questions!). ------------------------------------------------------------------------ #!/usr/bin/env python # Setup script example for building the Numeric extension to Python. # This does sucessfully compile all the .dlls. Nothing happens # with the .py files currently. # Move this file to the Numerical directory of the LLNL numpy # distribution and run as: # python numpysetup.py --verbose build_ext # # created 1999/08 Perry Stoll __rcsid__ = "$Id: numpysetup.py,v 1.1 1999/09/12 20:42:48 gward Exp $" from distutils.core import setup setup (name = "numerical", version = "0.01", description = "Numerical Extension to Python", url = "http://www.python.org/sigs/matrix-sig/", ext_modules = [ ( '_numpy', { 'sources' : [ 'Src/_numpymodule.c', 'Src/arrayobject.c', 'Src/ufuncobject.c' ], 'include_dirs' : ['./Include'], 'def_file' : 'Src/numpy.def' } ), ( 'multiarray', { 'sources' : ['Src/multiarraymodule.c'], 'include_dirs' : ['./Include'], 'def_file': 'Src/multiarray.def' } ), ( 'umath', { 'sources': ['Src/umathmodule.c'], 'include_dirs' : ['./Include'], 'def_file' : 'Src/umath.def' } ), ( 'fftpack', { 'sources': ['Src/fftpackmodule.c', 'Src/fftpack.c'], 'include_dirs' : ['./Include'], 'def_file' : 'Src/fftpack.def' } ), ( 'lapack_lite', { 'sources' : [ 'Src/lapack_litemodule.c', 'Src/dlapack_lite.c', 'Src/zlapack_lite.c', 'Src/blas_lite.c', 'Src/f2c_lite.c' ], 'include_dirs' : ['./Include'], 'def_file' : 'Src/lapack_lite.def' } ), ( 'ranlib', { 'sources': ['Src/ranlibmodule.c', 'Src/ranlib.c', 'Src/com.c', 'Src/linpack.c', ], 'include_dirs' : ['./Include'], 'def_file' : 'Src/ranlib.def' } ), ] ) ------------------------------------------------------------------------ First, what d'you think? Too clunky and verbose? Too much information for each extension? I kind of think so, but I'm not sure how to reduce it elegantly. Right now, the internal data structures needed to compile a module are pretty obviously exposed: is this a good thing? Or should there be some more compact form for setup.py that will be expanded later into the full glory we see above? I've already made one small step towards reducing the amount of cruft by factoring 'include_dirs' out and supplying it directly as a parameter to 'setup()'. (But that needs code not in the CVS archive yet, so I've left the sample setup.py the same for now.) The next thing I'd like to do is get that damn "def_file" out of there. To support it in MSVCCompiler, there's already an ugly hack that unnecessarily affects both the UnixCCompiler and CCompiler classes, and I want to get rid of that. (I refer to passing the 'build_info' dictionary into the compiler classes, if you're familiar with the code -- that dictionary is part of the Distutils extension-building system, and should not propagate into the more general compiler classes.) But I don't want to give these weird "def file" things standing on the order of source files, object files, libraries, etc., because they seem to me to be a bizarre artifact of one particular compiler, rather than something present in a wide range of C/C++ compilers. Based on the NumPy model, it seems like there's a not-too-kludgy way to handle this problem. Namely: if building extension "foo": if file "foo.def" found in same directory as "foo.c" add "/def:foo.def" to MSVC command line this will of course require some platform-specific code in the build_ext command class, but I figured that was coming eventually, so why put it off? ;-) To make this hack work with NumPy, one change would be necessary: rename Src/numpy.def to Src/_numpy.def to match Src/_numpy.c, which implements the _numpy module. Would this be too much to ask of NumPy? (Paul?) What about other module distributions that support MSVC++ and thus ship with "def" files? Could they be made to accomodate this scheme? Thanks for your feedback -- Greg -- Greg Ward - software developer gward(a)cnri.reston.va.us Corporation for National Research Initiatives 1895 Preston White Drive voice: +1-703-620-8990 Reston, Virginia, USA 20191-5434 fax: +1-703-620-0913

4 5

Can now compile simple extensions
by Greg Ward 29 Apr '18

29 Apr '18

Hi all -- at long last, I found the time to hack in the ability to compile extension modules to the Distutils. Mainly, this meant adding a 'build_ext' command which uses a CCompiler instance for all its dirty work. I also had to add a few methods to CCompiler (and, of course, UnixCCompiler) to make this work. And I added a new module, 'spawn', which takes care of running sub-programs more efficiently and robustly (no shell involved) than os.system. That's needed, obviously, so we can run the compiler! If you're in the mood for grubbing over raw source code, then get the latest from CVS or download a current snapshot. See http://www.python.org/sigs/distutils-sig/implementation.html for a link to the code snapshot. I'm still waiting for more subclasses of CCompiler to appear. At the very least, we're going to need MSVCCompiler to build extensions on Windows. Any takers? Also, someone who knows the Mac, and how to run compilers programmatically there, will have to figure out how to write a Mac-specific concrete CCompiler subclass. The spawn module also needs a bit of work to be portable. I suspect that _win32_spawn() (the intended analog to my _posix_spawn()) will be easy to implement, if it even needs to go in a separate function at all. It looks from the Python Library documentation for 1.5.2 that the os.spawnv() function is all we need, but it's a bit hard to figure out just what's needed. Windows wizards, please take a look at the 'spawn()' function and see if you can make it work on Windows. As for actually compiling extensions: well, if you can figure out the build_ext command, go ahead and give it a whirl. It's a bit cryptic right now, since there's no documentation and no example setup.py. (I have a working example at home, but it's not available online.) If you feel up to it, though, see if you can read the code and figure out what's going on. I'm just hoping *I'll* be able to figure out what's going on when I get back from the O'Reilly conference next week... ;-) Enjoy -- Greg -- Greg Ward - software developer gward(a)cnri.reston.va.us Corporation for National Research Initiatives 1895 Preston White Drive voice: +1-703-620-8990 Reston, Virginia, USA 20191-5434 fax: +1-703-620-0913

2 1

Two fixes (at last)
by Greg Ward 29 Apr '18

29 Apr '18

Hi all -- at long last, I have fixed two problems that a couple people noticed a while ago: * I folded in Amos Latteier's NT patches almost verbatim -- just changed an `os.path.sep == "/"' to `os.name == "posix"' and added some comments bitching about the inadequacy of the current library installation model (I think this is Python's fault, but for now Distutils is slavishly aping the situation in Python 1.5.x) * I fixed the problem whereby running "setup.py install" without doing anything else caused a crash (because 'build' hadn't yet been run). Now, the 'install' command automatically runs 'build' before doing anything; to make this bearable, I added a 'have_run' dictionary to the Distribution class to keep track of which commands have been run. So now not only are command classes singletons, but their 'run' method can only be invoked once -- both restrictions enforced by Distribution. The code is checked into CVS, or you can download a snapshot at http://www.python.org/sigs/distutils-sig/distutils-19990607.tar.gz Hope someone (Amos?) can try the new version under NT. Any takers for Mac OS? BTW, all parties involved in the Great "Where Do We Install Stuff?" Debate should take a good, hard look at the 'set_final_options()' method of the Install class in distutils/install.py; this is where all the policy decisions about where to install files are made. Currently it apes the Python 1.5 situation as closely as I could figure it out. Obviously, this is subject to change -- I just don't know to *what* it will change! Greg -- Greg Ward - software developer gward(a)cnri.reston.va.us Corporation for National Research Initiatives 1895 Preston White Drive voice: +1-703-620-8990 Reston, Virginia, USA 20191-5434 fax: +1-703-620-0913

2 1

Package versioning
by Timothy Docker 29 Apr '18

29 Apr '18

Hi all, I've been aware that the distutils sig has been simmerring away, but until recently it has not been directly relevant to what I do. I like the look of the proposed api, but have one question. Will this support an installed system that has multiple versions of the same package installed simultaneously? If not, then this would seem to be a significant limitation, especially when dependencies between packages are considered. Assuming it does, then how will this be achieved? I am presently managing this with a messy arrangement of symlinks. A package is installed with its version number in it's name, and a separate directory is created for an application with links from the unversioned package name to the versioned one. Then I just set the pythonpath to this directory. A sample of what the directory looks like is shown below. I'm sure there is a better solution that this, and I'm not sure that this would work under windows anyway (does windows have symlinks?). So, has this SIG considered such versioning issues yet? Cheers, Tim -------------------------------------------------------------- Tim Docker timd(a)macquarie.com.au Quantative Applications Division Macquarie Bank -------------------------------------------------------------- qad16:qad $ ls -l lib/python/ total 110 drwxr-xr-x 2 mts mts 512 Nov 11 11:23 1.1 -r--r----- 1 root mts 45172 Sep 1 1998 cdrmodule_0_7_1.so drwxr-xr-x 2 mts mts 512 Sep 1 1998 chart_1_1 drwxr-xr-x 3 mts mts 512 Sep 1 1998 Fnorb_0_7_1 dr-xr-x--- 3 mts mts 512 Nov 11 11:21 Fnorb_0_8 drwxr-xr-x 3 mts mts 1536 Mar 3 12:45 mts_1_1 dr-xr-x--- 7 mts mts 512 Nov 11 11:22 OpenGL_1_5_1 dr-xr-x--- 2 mts mts 1024 Nov 11 11:23 PIL_0_3 drwxr-xr-x 3 mts mts 512 Sep 1 1998 Pmw_0_7 dr-xr-x--- 2 mts mts 512 Nov 11 11:21 v3d_1_1 qad16:qad $ ls -l lib/python/1.1 total 30 lrwxrwxrwx 1 root other 29 Apr 10 10:43 _glumodule.so -> ../OpenGL_1_5_1/_glumodule.so lrwxrwxrwx 1 root other 30 Apr 10 10:43 _glutmodule.so -> ../OpenGL_1_5_1/_glutmodule.so lrwxrwxrwx 1 root other 22 Apr 10 10:43 _imaging.so -> ../PIL_0_3/_imaging.so lrwxrwxrwx 1 root other 36 Apr 10 10:43 _opengl_nummodule.so -> ../OpenGL_1_5_1/_opengl_nummodule.so lrwxrwxrwx 1 root other 27 Apr 10 10:43 _tkinter.so -> ../OpenGL_1_5_1/_tkinter.so lrwxrwxrwx 1 mts mts 21 Apr 10 10:43 cdrmodule.so -> ../cdrmodule_0_7_1.so lrwxrwxrwx 1 mts mts 12 Apr 10 10:43 chart -> ../chart_1_1 lrwxrwxrwx 1 root other 12 Apr 10 10:43 Fnorb -> ../Fnorb_0_8 lrwxrwxrwx 1 mts mts 12 Apr 10 10:43 mts -> ../mts_1_1 lrwxrwxrwx 1 root other 15 Apr 10 10:43 OpenGL -> ../OpenGL_1_5_1 lrwxrwxrwx 1 root other 33 Apr 10 10:43 opengltrmodule.so -> ../OpenGL_1_5_1/opengltrmodule.so lrwxrwxrwx 1 root other 33 Apr 10 10:43 openglutil_num.so -> ../OpenGL_1_5_1/openglutil_num.so lrwxrwxrwx 1 root other 10 Apr 10 10:43 PIL -> ../PIL_0_3 lrwxrwxrwx 1 mts mts 10 Apr 10 10:43 Pmw -> ../Pmw_0_7 lrwxrwxrwx 1 root other 10 Apr 10 10:43 v3d -> ../v3d_1_1

3 2

[Distutils-sig] distutils charter and interscript
by John Skaller 29 Apr '18

29 Apr '18

3 2

[buildout] branches languishing? (site-packages and distutils scripts)
by Chris Withers 02 Apr '12

02 Apr '12

Hi All, I'm wondering what the state of play is with the following branches: reinout-scripts gary-4-include-site-packages What more needs to happen for these to get merged to trunk and a release made? cheers, Chris

10 28

[PEP376] RECORD line separator
by Atsushi Odagiri 09 Jun '11

09 Jun '11

Hi I read pep276, and I have a question. This PEP says that line separator of RECORD file is `os.separator`. and 'bdist-*' command will also create RECORD file. Does it even work with the package which doesn't depend on the OS like bdist_egg ? I think that file format should not depend on os environment and good choice is CRLF. It's standard line separator as used in email headers. by aodag -- /* Atsushi Odagiri http://blog.aodag.jp mailto:aodagx@gmail.com */

2 1

Including symlinked data files in an egg
by Wichert Akkerman 22 Apr '11

22 Apr '11

I have a package with a source that looks like this: setup.py MANIFEST.in Prototype/libraries/jquery.js Prototype/style/main.css my/ my/package/ my/package/templates/libraries -> ../../../Prototype/libraries my/package/templates/style -> ../../../Prototype/style what I would like to accomplish is that when a bdist is made either Prototype/ is installed somewhere and the symlinks point to it, or the symlinks are replaced with a copy of the data they point to. For a package maintained in subverion this works: when the sdist is created the symlink is replaced with a copy of the thing it points to, which is then included in the bdist. For a package maintained in git this does not work: the symlink always appears to be ignored. Is there a way to accomplish this? Wichert. -- Wichert Akkerman <wichert(a)wiggy.net> It is simple to make things. http://www.wiggy.net/ It is hard to make things simple.

3 11

docs/ vs doc/
by anatoly techtonik 23 Feb '11

23 Feb '11

Hi, I see that distutils2 promotes storing documentation in docs/ directory while Python sources use Doc/ I'd like to see this changed before distutils2 is released beta. In my projects checkouts there are 80 project that use doc/ directories. Among these are: - subversion - hg - sphinx - trac - scons - twisted docs/ directory is used by 61 project, the most famous are: - xalan - fop - moinmoin - cmd2 - googlecl There are some arguments for 'doc/': 1. there is no plural for 'documentation' 2. bin/ is a common name for storing executables, although there is plural for 'binary' 3. we still use src/ instead of sources/ Any thoughts/objections? -- anatoly t.

9 19

buildout download utility and failed checksums in cache
by Łukasz Nowak 19 Feb '11

19 Feb '11

Hello, Buildout download utility allows to provide md5sum to check if downloaded (or available file from cache) is correct. In case of using download-cache and having wrong file in this cache it is required to manually remove this file and redownload. Is it possible to have redownload "request" inside of download utility? In case if file exists in cache, but passed checksum does not match, download utility cloud redownload this file, re check sum and eventually succeed. Is it ok to have such change of buildout download cache behaviour? Regards, Luke -- Łukasz Nowak IT Specialist email(a)lnowak.com http://lnowak.com/ Skype: Shufla jid: shufla(a)jabster.pl gg: 1157726 ``Use the Source, Luke...''

2 3

Buildout and non-pypi hosted packages
by Tom Aratyn 31 Jan '11

31 Jan '11

Hello, I work for an organization which would like to use buildout but we're hitting a problem with buildout and pyrtf (which is not hosted in the cheeseshop but is available off a url form sourceforge). Pip has no problem with this but I'm not sure how to get buildout to understand it. We're listing all our dependencies using install_requires. Is there a way to do this? Cheers, Tom

3 3

Fwd: [Catalog-sig] Trove categories for Buildout recipes and extensions
by Baiju M 26 Jan '11

26 Jan '11

Hi, I am forwarding a mail from Catalog-sig regarding two new trove categories for Buildout recipes and extensions. Those who publish Buildout recipes and extensions to PyPI, please use the new trove classifiers in addition to the existing "Framework :: Buildout". If you are developing a recipe, use this classifier: classifiers=[ ... "Framework :: Buildout", "Framework :: Buildout :: Recipe", ... ], If you are developing an extension, use this classifier: classifiers=[ ... "Framework :: Buildout", "Framework :: Buildout :: Extension", ... ], If the distribution contains both extension and recipe, use: classifiers=[ ... "Framework :: Buildout", "Framework :: Buildout :: Extension", "Framework :: Buildout :: Recipe", ... ], Regards, Baiju M ---------- Forwarded message ---------- From: Richard Jones <richard(a)python.org> Date: Wed, Jan 26, 2011 at 4:08 AM Subject: Re: [Catalog-sig] Trove categories for Buildout recipes and extensions To: Baiju M <baiju.m.mail(a)gmail.com> Cc: catalog-sig(a)python.org On Tue, Jan 18, 2011 at 5:33 PM, Baiju M <baiju.m.mail(a)gmail.com> wrote: > It would be nice if we can add two sub categories: > > Framework :: Buildout :: Recipe > Framework :: Buildout :: Extension There being no objections I've added these classifiers. Richard

4 5

setuptools and man pages
by Andrew McNabb 26 Jan '11

26 Jan '11

I am maintaining a package that includes several scripts, and I recently added a man page. Unfortunately, I was unable to figure out how to specify the man page with setuptools. I ended up switching back to vanilla distutils, which allowed me to specify the man page in setup.py: data_files=[('man/man1', ['man/man1/pssh.1'])] Is there an equivalent way to do this with setuptools? The closest thing I could find in the setuptools documentation was, "Note, by the way, that this encapsulation of data files means that you can't actually install data files to some arbitrary location on a user's machine; this is a feature, not a bug." I appreciate the well-intended thought, but I can't find any feature for specifying man pages. I don't want to install to an arbitrary location, but I need to be able to install to $PREFIX/man/man1). Is there a way to do this with setuptools, or do I need to keep using distutils? I would love to be able to use the "console_scripts" feature, so it would be great if I could use setuptools, but obviously the man pages are higher priority. I feel like I must be missing something obvious. Thanks. -- Andrew McNabb http://www.mcnabbs.org/andrew/ PGP Fingerprint: 8A17 B57C 6879 1863 DE55 8012 AB4D 6098 8826 6868

2 5

zc.buildout socket-timeout option
by Dave Peticolas 24 Jan '11

24 Jan '11

A quick question about this buildout option. Am I right that it isn't actually enabled yet? It doesn't seem to have any effect for me (this is on buildout 1.5.2), but using -t has a noticeable effect. thanks, dave

1 0

current ez_setup.py appears to refers a non existing URL?
by Jan-Wijbrand Kolman 21 Jan '11

21 Jan '11

Hi, Since about an hour or so, when I run ez_setup.py (by way of a zc.buildout bootstrap.py script), I get this: Downloading http://pypi.python.org/packages/2.7/s/setuptools/setuptools-0.6c12-py2.7.egg Traceback (most recent call last): File "bootstrap.py", line 172, in <module> ez['use_setuptools'](**setup_args) File "<string>", line 76, in use_setuptools File "<string>", line 70, in do_download File "<string>", line 131, in download_setuptools File "/home/jw/runtime/2.7/lib/python2.7/urllib2.py", line 126, in urlopen return _opener.open(url, data, timeout) File "/home/jw/runtime/2.7/lib/python2.7/urllib2.py", line 398, in open response = meth(req, response) File "/home/jw/runtime/2.7/lib/python2.7/urllib2.py", line 511, in http_response 'http', request, response, code, msg, hdrs) File "/home/jw/runtime/2.7/lib/python2.7/urllib2.py", line 436, in error return self._call_chain(*args) File "/home/jw/runtime/2.7/lib/python2.7/urllib2.py", line 370, in _call_chain result = func(*args) File "/home/jw/runtime/2.7/lib/python2.7/urllib2.py", line 519, in http_error_default raise HTTPError(req.get_full_url(), code, msg, hdrs, fp) urllib2.HTTPError: HTTP Error 404: Not Found And indeed, when I download ez_setup.py myself: $ wget http://peak.telecommunity.com/dist/ez_setup.py and run it, I also get the 404 on the URL: http://pypi.python.org/packages/2.7/s/setuptools/setuptools-0.6c12-py2.7.egg. I have been bootstrap.py-ing packages all day long and suddenly they stopped to work. Am I doing something wrong, or is the ez_setup.py broken? Kind regards, jw

3 2

[issue120] cli.exe quits on ctrl-c, but python doesn't
by Guy Rozendorn 21 Jan '11

21 Jan '11

New submission from Guy Rozendorn <guy(a)rzn.co.il>: the cli should use SetConsoleCtrlHandler to ignore CTRL-C and pass it to its child process ---------- messages: 573 nosy: guyroz priority: bug status: unread title: cli.exe quits on ctrl-c, but python doesn't _______________________________________________ Setuptools tracker <setuptools(a)bugs.python.org> <http://bugs.python.org/setuptools/issue120> _______________________________________________

1 0

Re: [Distutils] Bootstrap use_setuptools() in ez_setup.py failure
by P.J. Eby 20 Jan '11

20 Jan '11

At 01:55 PM 1/20/2011 +0800, Pherl Liu wrote: >Hmm, I think it now only delete pkg_resource when >pkg_resrouces.VersionConflict is caught, but the fix should be also >delete pkg_resources when pkg_resources.DistributionNotFound is caught. Good catch. Under previous use cases, the only time you'd have pkg_resources and *not* setuptools, it would be if you were bundling pkg_resources. Nowadays, though, some distros split setuptools from pkg_resources, so you can have an older, distro-supplied pkg_resources, but no setuptools. Anyway, I've fixed this in SVN and on the website now. Thanks!

1 0

Re: [Distutils] Bootstrap use_setuptools() in ez_setup.py failure
by P.J. Eby 20 Jan '11

20 Jan '11

At 03:40 PM 1/19/2011 +0800, Pherl Liu wrote: >Well.. > >I think I can fix this by editing ez_setup.py > >adding oneline after pkg_resources.DistributionNotFound is caught, >in use_setuptools() > >del pkg_resources, sys.modules['pkg_resources'] > >Not sure if this makes sense. That's already in current versions of ez_setup.py; 0.6c9 is several years old. I'd suggest you use the svn externals to keep it up-to-date. See: http://peak.telecommunity.com/DevCenter/setuptools#managing-multiple-projec… for details.

2 1

Re: [Distutils] Bootstrap use_setuptools() in ez_setup.py failure
by P.J. Eby 19 Jan '11

19 Jan '11

At 04:42 PM 1/12/2011 +0800, Pherl Liu wrote: >Hi, > >I got some error messages when using ez_setup to download and use >the easy_install. > ># setup.py >from ez_setup import use_setuptools >use_setuptools() > >from setuptools import setup > >setup(name = "blabla", > test_suite = "some_test", > namespace_package = ["some_namespace"], > # many other options >) > > >So I guess there might be some import problem in my machine (ubuntu >lucid) that the pkg_resources.py cannot be loaded from the egg? Try running this script in your project directory: from ez_setup import use_setuptools use_setuptools() import sys, setuptools, pkg_resources print sys.path print pkg_resources.__file__ print setuptools.__file__ This should tell us what's going on with your "import problem" more specifically. ;-)

2 2

Re: [Distutils] PEP 345: real-world examples of "virtual" projects (Provides-Release)
by Sridhar 17 Jan '11

17 Jan '11

Hi, > From: Alexis Métaireau <alexis(a)notmyidea.org> > On 12/21/2010 09:41 PM, Sridhar Ratnakumar wrote: >> >> 3. Did anyone--Alexis and Tarek, in particular--think of real-world use >> cases for virtual projects (and even "provides" in general) other than >> the Zope transaction case? If yes, what are they? > > "Provides-Release" lists the specific projects provided with this > distribution. One case I can think about is having a distribution > providing two different projects. > > A software can have a project for the "core" features and a project for > the "default-plugins". It can then provides the two projects in only one > distribution. > > Those can be two virtual projects 'core' and 'defaultplugins', which can > be *provided* by different projects then. This allows to choose between > the possible projects when resolving the dependencies. What is the benefit of distributing two projects in a single distribution, compared to the more simpler (traditional) solution of distributing them in separate distributions (and, optionally, making one depend on another; eg: 'core' depend on 'defaultplugins')? Does this benefit justify the cost of introducing a new metadata field? > setuptools and distribute can be both provided by the same virtual project. Is this the only real-world use of virtual projects? Are there (potential) others? >> 4. Personally, I have needs for "virtual" packages from a binary (not >> source) distribution perspective. For example, "MySQL-python" can be a >> virtual package "provided by" the binary distributions: mysql5.1-python, >> mysql5.0-python; > [...] >> How would PEP 345's "Provides-Release" help, if at >> all, in describing this scenario? > > I'm not sure it will help in this case, unfortunately. Ok. -Sridhar ActiveState

2 1

Setting version from commandline or setup.cfg?
by Alan Franzoni 16 Jan '11

16 Jan '11

Hello, I'm trying to automate my release process from vcs - something like: run tests -> fetch current major, minor from branch (e.g. release_1.2) and revision from tag (e.g. v1.2.1) -> upload with current major, minor and revision +1 > tag with such current major, minor and incremented revision. I'd like to set my version from outside my setup.py file, either via setup.py or a commandline option - I don't want to execute code in my setup.py since this usually causes all sort of headaches with missing dependencies. Is there any proper way to do it? Might I break other things unexpectedly? -- Alan Franzoni -- contact me at public(a)[mysurname].eu

2 4

buildout download cache
by rafael＠nexedi.com 14 Jan '11

14 Jan '11

Hi, We are using extensively buildout to build ERP5 [1]: - https://svn.erp5.org/repos/public/erp5/trunk/buildout/ We are planning to extend buildout download API to provide a distributed automatic packaging and caching system so that even if original source web site is down, the buildout process can stil run. This could also be useful to build software in secured networks. Do you know of any similar project before we start? [1] www.erp5.com Regards, Rafael Monnerat ---------------------------------------------------------------- This message was sent using IMP, the Internet Messaging Program.

4 4

buildout pinning versions and egg requires
by Jeff Kunce 14 Jan '11

14 Jan '11

Hi - I'm having trouble pinning versions in my buildout. It looks like "requires.txt" for the recipe eggs are overriding what I specify in versions.cfg. Here's the scenario: 1) I am pinning my buildout with a versions.cfg file that specifies zope2 = 2.13.0 2) One of my parts is based on recipe = plone.recipe.zope2instance 3) The plone.recipe.zope2instance egg has a requires.txt file containing Zope2 >= 2.12.1 Here's what happens: When I run buildout, it looks the recipe eggs are downloaded first, along with eggs specified in the requires.txt for each egg. So, buildout gets Zope2 2.13.1 (>=2.12.1) for plone.recipe.zope2instance without looking at what I specified for versions. How can I make sure I only get Zope 2.13.0 ? An excerpt of my buildout.cfg is below. Thanks. -- Jeff [buildout] ... extends = versions.cfg versions = versions ... parts = mydeps zeo inst1 inst2 inst3 inst4 myproducts siteconfig [mydeps] ... [inst1] recipe = plone.recipe.zope2instance zeo-client = true ... [inst2] ...

5 7

Re: [Distutils] .exe for script in Windows doesn't work
by P.J. Eby 14 Jan '11

14 Jan '11

At 10:45 PM 1/13/2011 +0100, Martin v. Löwis wrote: >How is that generated (i.e. what piece of code specifically generates it)? See setuptools.command.install_scripts.run() - it makes .exe and -script.py/-script.pyw files. It has some hackery to detect bdist_wininst and use a relative #! line in that case, but it doesn't have equivalent hackery for bdist_msi.

1 0

Re: [Distutils] .exe for script in Windows doesn't work
by P.J. Eby 13 Jan '11

13 Jan '11

At 09:54 AM 1/13/2011 +0200, cool-RR wrote: >On Thu, Jan 13, 2011 at 2:25 AM, P.J. Eby ><<mailto:pje@telecommunity.com>pje(a)telecommunity.com> wrote: >At 09:31 PM 1/12/2011 +0200, cool-RR wrote: >Hi guys, > >I made a release of my project today, and now I see there's >something wrong with it. > >When you install it on Windows using the windows binaries (that I >made with `bdist_msi` under Python 2.7), the .exe scripts in the >"Scripts" folder don't work. When you launch them, nothing happens. >You can launch the associated *-script.pyw files and those *do* work. > >I investigated a little and possibly I figured it out. The shebang >line says "#!c:\Python27\pythonw.exe". This is the interpreter with >which I *created* the binaries. But why should it be the interpreter >with which the *user* works? The user could have >"c:\Python26\pythonw.exe" as his interpreter or >"c:\Programs\Python25\pythonw.exe" or "g:\Pypy\pypy.exe" as his interpreter. > >I tried editing the shebang line with notepad, and this caused the >exe files to start working! (Of course this is not a real solution, >I can't ask my users to do that.) > >Is this a bug in distribute? > > >It's a limitation of setuptools+bdist_msi - when you build a >bdist_wininst, setuptools writes a generic #! line, but when you >build a bdist_msi, it doesn't realize you're building a distribution. > > >So which project exactly is responsible for this limitation? Distribute? Setuptools. >Do you think there's a good reason not to have the MSI put the path >to python.exe itself into the shebang upon installation? I don't know how to have bdist_msi do that. Do you? >As a quick workaround, you could try setting sys.executable to >'pythonw.exe' in your setup.py, *before* setuptools is imported, >then build the .msi. > > >I'd be reluctant to do that, since many users don't have the Python >folder on their PATH, so it won't work for them at all. That's not how it works. When the #! line doesn't contain an absolute path, the .exe stub looks in the parent directory relative to where the script was installed. So, as long as the .exe and .pyw are in an immediate subdirectory of the Python directory (usually Scripts), it will work correctly.

3 4

simpler distutils.cmd.Command
by kost BebiX 13 Jan '11

13 Jan '11

hi! I am really confused about all the setuptools/distutils/distribute/distutils2/easy_install/pip situation, but still have a little frustration about writing your own command for python setup.py your_command_name. Right now, for example, babel package provides it's command:: python setup.py extract_messages To do that, the part:: [distutils.commands] extract_messages = babel.messages.frontend:extract_messages is ok, but what I dislike is the whole:: from distutils.cmd import Command class extract_messages(Command): # provide user_options and 3 more function implementations in here pass thing. I find it really implicit. I mean, how do I run the command extract_messages from python? Maybe implementation of command should be that it can be called from regular python code like:: extract_messages(my_custom_kwargs=here) ? -- jabber: k.bx(a)ya.ru

1 0

Re: [Distutils] .exe for script in Windows doesn't work
by P.J. Eby 13 Jan '11

13 Jan '11

At 09:31 PM 1/12/2011 +0200, cool-RR wrote: >Hi guys, > >I made a release of my project today, and now I see there's >something wrong with it. > >When you install it on Windows using the windows binaries (that I >made with `bdist_msi` under Python 2.7), the .exe scripts in the >"Scripts" folder don't work. When you launch them, nothing happens. >You can launch the associated *-script.pyw files and those *do* work. > >I investigated a little and possibly I figured it out. The shebang >line says "#!c:\Python27\pythonw.exe". This is the interpreter with >which I *created* the binaries. But why should it be the interpreter >with which the *user* works? The user could have >"c:\Python26\pythonw.exe" as his interpreter or >"c:\Programs\Python25\pythonw.exe" or "g:\Pypy\pypy.exe" as his interpreter. > >I tried editing the shebang line with notepad, and this caused the >exe files to start working! (Of course this is not a real solution, >I can't ask my users to do that.) > >Is this a bug in distribute? It's a limitation of setuptools+bdist_msi - when you build a bdist_wininst, setuptools writes a generic #! line, but when you build a bdist_msi, it doesn't realize you're building a distribution. >I'd appreciate if you can reply soon since I already started the >release process and I don't want to confuse users. As a quick workaround, you could try setting sys.executable to 'pythonw.exe' in your setup.py, *before* setuptools is imported, then build the .msi.

2 1

.exe for script in Windows doesn't work
by cool-RR 12 Jan '11

12 Jan '11

Hi guys, I made a release of my project today, and now I see there's something wrong with it. When you install it on Windows using the windows binaries (that I made with `bdist_msi` under Python 2.7), the .exe scripts in the "Scripts" folder don't work. When you launch them, nothing happens. You can launch the associated *-script.pyw files and those *do* work. I investigated a little and possibly I figured it out. The shebang line says "#!c:\Python27\pythonw.exe". This is the interpreter with which I *created* the binaries. But why should it be the interpreter with which the *user* works? The user could have "c:\Python26\pythonw.exe" as his interpreter or "c:\Programs\Python25\pythonw.exe" or "g:\Pypy\pypy.exe" as his interpreter. I tried editing the shebang line with notepad, and this caused the exe files to start working! (Of course this is not a real solution, I can't ask my users to do that.) Is this a bug in distribute? I'd appreciate if you can reply soon since I already started the release process and I don't want to confuse users. Thanks, Ram.

1 0

Bootstrap use_setuptools() in ez_setup.py failure
by Pherl Liu 12 Jan '11

12 Jan '11

Hi, I got some error messages when using ez_setup to download and use the easy_install. # setup.py from ez_setup import use_setuptools use_setuptools() from setuptools import setup setup(name = "blabla", test_suite = "some_test", namespace_package = ["some_namespace"], # many other options ) It can download the setuptools-0.6c9-py2.6.egg file correctly, but when I run "python setup.py test" it complains: /usr/lib/python2.6/distutils/dist.py:266: UserWarning: Unknown distribution option: 'namespace_packages' warnings.warn(msg) /usr/lib/python2.6/distutils/dist.py:266: UserWarning: Unknown distribution option: 'test_suite' warnings.warn(msg) usage: setup.py [global_opts] cmd1 [cmd1_opts] [cmd2 [cmd2_opts] ...] or: setup.py --help [cmd1 cmd2 ...] or: setup.py --help-commands or: setup.py cmd --help error: invalid command 'test' It seems the easy_install egg isn't used, and the "setup" is just from the built-in distutil. I did several things: 1) update the ez_setup.py but the only difference is it downloads the c11 egg, which doesn't work either. 2) unzip the egg to the current directory. "python setup.py test" passed... 3) install the easy_install. "python setup.py test" passed... 4) unzip the egg to the current directory, remove other files but only reserve pkg_resources.py and the egg. "python setup.py test" passed.. So I guess there might be some import problem in my machine (ubuntu lucid) that the pkg_resources.py cannot be loaded from the egg? Thanks, Pherl

1 0

distutils and MSVCR90.DLL
by Mark Sienkiewicz 05 Jan '11

05 Jan '11

Hi, I have a python package with C extensions. In Python 2.5 on Windows, it works as expected. In Python 2.7, it compiles and installs, but the import fails with: ImportError: DLL load failed: The specified procedure could not be found. I found a program called "Dependecy Walker" that tells me this about the .pyd file: Error: At least one required implicit or forwarded dependency was not found. Warning: At least one delay-load dependency module was not found. Warning: At least one module has an unresolved import due to a missing export function in a delay-load dependent module. It also says the missing library is MSVCR90.DLL which contains things like malloc and printf. (It is also missing IESHIMS.DLL and WER.DLL but those are required by IEFRAME.DLL, so they may be a secondary problem.) Apparently, MSVCR90 is a newer version of the C runtime library. I have several copies of MSVCR71.DLL on my machine, but nothing named MSVCR90.DLL. This leads to an obvious question: How did I manage to compile C source code that depends on a shared library that is not even present on my machine? I suspect it is because whoever built the Python distribution did it with a compiler that did have MSVCR90, and python remembered and told distutils. Some web searching led me to find "vcredist_x86.exe" on Microsoft's web site, but installing that did not fix anything and did not create a file on my system name MSVCR90.DLL. From http://support.microsoft.com/kb/326922 , I get the impression that MSVCR90.DLL should have been distributed with Python. Or maybe not... I'm about at the limit of my Windows expertise here. Can anybody help? Mark S.

2 5

Distribute comments
by K. Richard Pixley 04 Jan '11

04 Jan '11

I've just read through the Distribute doc for the first time and I have a few comments. First, I just want to say that the state of python packaging is a sad morass. It's not easy for someone to sort out distutils/setuptools/distribute to figure out how to get a package built and released on pypi. Distutils is official and available, but the documentation is only slightly relevant with much time and space given to features that aren't clear, aren't relevant, or don't solve today's problems. Setuptools is messy, confusing, ill documented, and difficult to use. The Distribute documentation helps in this considerably but it could be better. For instance... I wish that the Distribute documentation didn't refer to itself as "setuptools". This is confusing. From where I'm sitting, Distribute is a fork. It may have started life once upon a time in a distant past that I don't care about as a fork of setuptools but as of today, it's a separate package which just happens to provide a superset of the setuptools features along with a setuptools compatible replacement interface. To say that one can use a Distribute script to install "setuptools" is a misnomer. It suggests that the original setuptools is being installed rather than installing Distribute, (which just happens to provide functional replacements for setuptools). That's not what I want. I want Distribute and Distribute alone. I'm willing to go to some effort to make sure that people who use my package never need to know about, read about, or even think about setuptools. Toward that end, I wish that the documentation would explain how to import Distribute specifically, in a non-setuptools compatible way. I don't need or want a setuptools compatible replacement. I have a new package and I'm completely willing to make my package wholly dependent on Distribute rather than setuptools. Even attempting to support setuptools at this point in history seems like a mistake to me. If I'm going to include distribute_setup.py in my package, then it seems to me that I'm already committed to Distribute, not setuptools. Leaving the illusion that an installer might be able to make setuptools work for my package seems misguided. I'd like to eliminate that thought. The section on "What Your Users Should Know" sounds like the sort of information which has traditionally been released in an INSTALL file with GNU software. Is there a reusable, sample template which explains this information in a package agnostic sort of way that I can simply include in my package? Thanks for reading. --rich <http://packages.python.org/distribute/setuptools.html#id25>

3 4