Mailman 3 November 2010 - 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

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

distributing only .pyc with stdeb
by Karel Antonio Verdecia Ortiz 29 Nov '10

29 Nov '10

Hi, I'm using stdb to generate .deb packages for ubuntu but I need this packages to contain only the compiled modules (.pyc) and not the source modules (.py). ¿What parameters have I to use to get only the .pyc files? Thanks.

4 3

64-bit vs 32-bit (Re: An observation on how system packagers and developers can be friends)
by Jim Fulton 29 Nov '10

29 Nov '10

On Fri, Nov 5, 2010 at 11:55 AM, Mark Sienkiewicz <sienkiew(a)stsci.edu> wrote: > >> In the same direction, I wish people would understand that 64-bit Python >> builds just waste memory, and that they were better off with 32-bit >> implementations. > > There are certain irrational reasons to believe that "64 bits is better than > 32", but there is also some logic to it. > > I support an application that can't run in a 32 bit python because there > literally is not enough memory available. It needs a larger address space. Me too. I've found that on 32-bit linux systems, when programs get above around 2G, mallocs of a few tens of megs will fail. What's worse -- much much worse -- when a memory error occurs, it can leave an application in an unpredictable state. (Think memory errors in the bowels of your database.) These errors tend to lead to really odd symptoms and be be hard to diagnose. This is bad enough, but I really want to restart an app when a memory error occurs, but MemoryError is a subclass of Exception so it tends to be caught a lot. I really wish MemoryError was one of those errors you had to go way out of your way to catch. Because of the havoc that can be caused by even infrequent memory errors, we're moving most of our apps to 64 bits, even though they rarely use more than 2G. Jim -- Jim Fulton

2 1

Building Python (Re: An observation on how system packagers and developers can be friends)
by Jim Fulton 29 Nov '10

29 Nov '10

On Thu, Oct 28, 2010 at 6:08 PM, Tres Seaver <tseaver(a)palladion.com> wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > On 10/28/2010 05:54 PM, Benji York wrote: >> On Thu, Oct 28, 2010 at 5:44 PM, Tres Seaver <tseaver(a)palladion.com> wrote: >>> Heh, "untar + CMMI into a non-system prefix" works for me. ;) >> >> +1 with the small addition of "after making sure the dev dependencies Python >> sniffs out to build modules for (zlib, crypto bits, etc.) are available." > > Heh, agreed. That bites me on about every third machine I set up for > the first time. An advantage of automating building of clean Python's with system packaging tools is that you can make sure the sane dependencies are present. My clean Python RPM spec file lists the libraries I need before a build, so I can't accidentally build a crippled Python due to forgotten libraries. Of course, you also end up with a binary package that is quicker to install on similar hosts than building on each host. It would be nice if Python's standard build required more dependencies and had options to turn them off is desired, rather than sniffing to tell whether they are there and silently building badly. Jim -- Jim Fulton

2 1

Re: [Distutils] Distutils fails to build
by Tarek Ziadé 29 Nov '10

29 Nov '10

> On Mon, Nov 29, 2010 at 1:43 PM, Oisin O'Maley <ninja.gofer(a)gmail.com> wrote: ... > > I would appear distribute.egg-info/entry_points.txt is being read > correctly. I fail to see the problem in Distribute original source then. Did you try that on the original source ? If yes, I fail to understand what's wrong. You need to trace the code using PDB, to find out why this error is raised/ Please keep Distutils-SIG so everyone can participate to the thread Regards Tarek -- Tarek Ziadé | http://ziade.org

1 0

stdeb gzipping some data_files
by Lee Harr 29 Nov '10

29 Nov '10

I am using stdeb (https://github.com/astraw/stdeb) to create debian .deb packages from a python project. (That page says this is the place to ask questions...) stdeb is working quite well, but some of the files that I mention in the data_files part of the setup.py are being gzipped at some point in the process. Is there any way to prevent (hopefully from setup.py, setup.cfg, or stdeb.cfg) the alteration of those files? Thanks for any pointers.

3 2

something like pkg==dev in distutils2?
by Aljoša Mohorović 29 Nov '10

29 Nov '10

pip enables "pip install mypackage==dev" if link (with #egg=mypackage-dev) exists in long_description for pypi. are there some plans for an official way to do this? Aljosa Mohorovic

2 2

Re: [Distutils] Distutils fails to build
by Tarek Ziadé 29 Nov '10

29 Nov '10

On Mon, Nov 29, 2010 at 12:29 AM, Oisin O'Maley <ninja.gofer(a)gmail.com> wrote: > There doesn't appear to be anything anything wrong with > "distribute.egg-info/entry_points.txt" It's the same file indeed. .. > The error is thrown on both the Gentoo and PyPi version. ... Ok. I cannot reproduce this. >> >>> import pkg_resources >> >>> >> >>> list(pkg_resources.split_sections(open('distribute.egg-info/entry_points.txt').read())) > > This seems to run fine on both Gentoo and PyPi versions. But running "python > setup.py egg_info" throws the same error as I mentioned above. Can you show us the output ? The error happens because split_sections() returns at some point a (group, lines) where group is None. >>> import pkg_resources >>> for group, lines in pkg_resources.split_sections(open('distribute.egg-info/entry_points.txt').read()): ... if group is None and lines is not None: ... print 'ha!' ... print lines ... You can also add a pdb in the code just before the raise, and call egg_info -- Tarek Ziadé | http://ziade.org

1 0

What alternatives DJV?
by Garciahh 29 Nov '10

29 Nov '10

What alternatives For me problemma. Komp of not want to perceive the program DJV. Whether there are alike, which can facilitate work with pictures in DJV? ----- http://uk.bestessays.com/ uk essays -- View this message in context: http://old.nabble.com/What-alternatives-DJV--tp30328499p30328499.html Sent from the Python - distutils-sig mailing list archive at Nabble.com.

1 0

disutils2 tests and python 2.5
by Roumen Petrov 29 Nov '10

29 Nov '10

Hello all, I would like to ask to compare/check unit test results of distutils2 (repository) with someone. In my build environment the unit test exit without errors: ---------------- test_check_metadata (distutils2.tests.test_command_check.CheckTestCase) ... ok test_check_restructuredtext (distutils2.tests.test_command_check.CheckTestCase) ... skipped 'requires docutils' test_config (distutils2.tests.test_config.ConfigTestCase) ... ---------------- Note that test_config is without ok at the end. Did someone get same results with python 2.5 ? Roumen

5 9

Distutils fails to build
by Oisin O'Maley 28 Nov '10

28 Nov '10

Hi, I have been trying to reinstall distutils-0.6.14 on my gentoo system after some file corruption and now distutils fails to build. When manually building from source it throws the following error: *python2.6 setup.py build* Traceback (most recent call last): File "setup.py", line 211, in <module> scripts = scripts, File "/usr/lib64/python2.6/distutils/core.py", line 113, in setup _setup_distribution = dist = klass(attrs) File "/home/oisin/source/distribute-0.6.14/setuptools/dist.py", line 222, in __init__ for ep in pkg_resources.iter_entry_points('distutils.setup_keywords'): File "/home/oisin/source/distribute-0.6.14/pkg_resources.py", line 454, in iter_entry_points entries = dist.get_entry_map(group) File "/home/oisin/source/distribute-0.6.14/pkg_resources.py", line 2252, in get_entry_map self._get_metadata('entry_points.txt'), self File "/home/oisin/source/distribute-0.6.14/pkg_resources.py", line 2038, in parse_map raise ValueError("Entry points must be listed in groups") ValueError: Entry points must be listed in groups Anyone got any idea what is causing this? This is preventing me from reinstalling allot of packages on my system, so any help would be greatly appreciated. I have a tread on the gentoo forums with more info on the problem if anyone is interested; http://forums.gentoo.org/viewtopic-t-854323.html Thanks.

2 1

mercurial update problem with pip
by Fabian Sturm 21 Nov '10

21 Nov '10

Hi, I am using pip version 0.3.1 on Ubuntu Linux 9.10 to install django-piston in a virtualenv. Since I need a specific version of django-piston I have the following entry in the requirements.txt file: -e hg+http://bitbucket.org/jespern/django-piston@dc0ee00d3bfc#egg=django-piston The first time the install works fine with pip but on the second time I get the following error: Command hg fetch -q failed with error code 255 Exception information: Traceback (most recent call last): File "/usr/lib/python2.6/dist-packages/pip.py", line 252, in main self.run(options, args) File "/usr/lib/python2.6/dist-packages/pip.py", line 408, in run requirement_set.install_files(finder, force_root_egg_info=self.bundle) File "/usr/lib/python2.6/dist-packages/pip.py", line 1741, in install_files req_to_install.update_editable() File "/usr/lib/python2.6/dist-packages/pip.py", line 1486, in update_editable version_control(self.url).obtain(self.source_dir) File "/usr/lib/python2.6/dist-packages/pip.py", line 2942, in obtain call_subprocess(['hg', 'fetch', '-q'], cwd=dest) File "/usr/lib/python2.6/dist-packages/pip.py", line 3543, in call_subprocess % (command_desc, proc.returncode)) InstallationError: Command hg fetch -q failed with error code 255 If I run "hg fetch -q" manually in the django-piston repository I get: abort: working dir not at branch tip (use "hg update" to check out branch tip) mercurial is at version 1.3.1. Any ideas what is wrong and how I get it to work? Thanks a lot, Fabian ---------------------------------------------------------------- This message was sent using IMP, the Internet Messaging Program.

2 1

installing to a non-standard directory
by K. Richard Pixley 21 Nov '10

21 Nov '10

I'm trying to install to a non-standard directory. Something akin to "python setup.py install --prefix=`pwd`/junk" using gnu makefile standards semantics for --prefix but I can't seem to find the right arguments to install to make this happen. The closest I can seem to find is: python setup.py install --prefix=`pwd`/junk --install-layout=unix But that returns errors: distutils.errors.DistutilsError: can't create or remove files in install directory The following error occurred while trying to add or remove files in the installation directory: [Errno 2] No such file or directory: '/home/rich/projects/rcmp/junk/lib/python2.6/site-packages/test-easy-install-12743.pth' The installation directory you specified (via --install-dir, --prefix, or the distutils default setting) was: /home/rich/projects/rcmp/junk/lib/python2.6/site-packages/ This directory does not currently exist. Please create it and try again, or choose a different installation directory (using the -d or --install-dir option). Although there doesn't appear to be any --install-dir option. Can anyone explain what any of the 13 options related to this are intended to do? Or better, can anyone tell me which one I want? --rich

2 3

setuptools vs distribute on Debian
by Manlio Perillo 18 Nov '10

18 Nov '10

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 No, this is not a flame. I'm on Debian Squeeze and I noticed this strange thing: $sudo easy_install -U setuptools install_dir /usr/local/lib/python2.6/dist-packages/ Searching for distribute Reading http://pypi.python.org/simple/distribute/ Reading http://packages.python.org/distribute Best match: distribute 0.6.14 Processing distribute-0.6.14-py2.6.egg distribute 0.6.14 is already the active version in easy-install.pth Installing easy_install script to /usr/local/bin Installing easy_install-2.6 script to /usr/local/bin Using /usr/local/lib/python2.6/dist-packages/distribute-0.6.14-py2.6.egg Processing dependencies for distribute Finished processing dependencies for distribute Now, I read that this is a Debian policy: for some reasons they force me to use distribute instead setuptools. However, I *do* want to use setuptools, and I'm unable to do what I want. I checked the "fake" setuptools source code but I can't see what I need to modify in order to get setuptools when I ask for setuptools. By the way, I suspect there is a bug in Debian setuptools: if dist.key=='distribute': # Ensure that setuptools itself never becomes unavailable! # XXX should this check for latest version? filename = os.path.join(self.install_dir,'setuptools.pth') if os.path.islink(filename): os.unlink(filename) f = open(filename, 'wt') f.write(self.pth_file.make_relative(dist.location)+'\n') f.close() However if `easy_install setuptools` is an alias for `easy_install distribute`, that code may not executed (?) Thanks Manlio -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkzlS4wACgkQscQJ24LbaUQVMgCfV0oIvuUJ3xRPlNhftTJZ3HMR 0BoAn2rb8DJFaPHhRRKcDNyRNN28uUfl =Lg51 -----END PGP SIGNATURE-----

4 8

Python Deb Packages
by Damian Johnson 18 Nov '10

18 Nov '10

Hi, I'm working on deb/rpm packaging for a terminal monitor of tor relays [1] and running into an issue with the egg-info distutil autogenerates. My project currently installs to the default '/usr/share/pyshared' [2] but according to the debian policy for private python modules [3] it should be installed to '/usr/share' instead (my program is an application and there's no reason for it to be importable by other modules). The problem with doing this is that the egg-info metadata is hardcoded in 'distutils/command/install.py' to be added on install, and having an egg-info file on '/usr/share' causes a lintian error when generating the deb. Also, most things I've been reading seems to say that the package belongs in '/usr/share/pyshared' and that removing the egg-info is kinda evil [4]. Help would be appreciated. Cheers! -Damian [1] http://www.atagar.com/arm/ [2] https://svn.torproject.org/svn/arm/trunk/setup.py [3] http://www.debian.org/doc/packaging-manuals/python-policy/ch-programs.html#… [4] http://mail.python.org/pipermail/distutils-sig/2007-September/008225.html

3 4

setuptools.archive_util.unpack_archive dies in case of bad tarball
by Łukasz Nowak 18 Nov '10

18 Nov '10

Hello, Please see attached tarkill.tar.gz and buildout profile. This tarball containts dead link: ls -l tarkill lrwxrwxrwx 1 luke users 4 2010-11-18 19:56 kill -> kill After running attached buildout profile and having python shell setuptools will enter infinite loop: >>> import sys >>> sys.version_info sys.version_info(major=2, minor=7, micro=0, releaselevel='final', serial=0) >>> import tempfile >>> import setuptools.archive_util >>> tempdir = tempfile.mkdtemp() >>> setuptools.archive_util.unpack_archive('tarkill.tar.gz', tempdir) ^CTraceback (most recent call last): File "<console>", line 1, in <module> File "/srv/home/luke/python2.7/setup/eggs/setuptools-0.6c12dev_r85381-py2.7.egg/setuptools/archive_util.py", line 67, in unpack_archive driver(filename, extract_dir, progress_filter) File "/srv/home/luke/python2.7/setup/eggs/setuptools-0.6c12dev_r85381-py2.7.egg/setuptools/archive_util.py", line 190, in unpack_tarfile member = tarobj._getmember(linkpath) File "/srv/home/luke/python2.7/parts/python2.7/lib/python2.7/tarfile.py", line 2357, in _getmember members = self.getmembers() File "/srv/home/luke/python2.7/parts/python2.7/lib/python2.7/tarfile.py", line 1801, in getmembers self._check() KeyboardInterrupt Attached workaround which breaks the loop, but I think that such deadlink shall be created, just like tar does it. 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...''

1 0

M2Crypto install failing
by Leonardo Rochael Almeida 18 Nov '10

18 Nov '10

Hi, With this simple buildout: [buildout] parts = m2c [m2c] recipe = zc.recipe.egg eggs = M2Crypto I'm getting this failure: Installing 'M2Crypto'. We have no distributions for M2Crypto that satisfies 'M2Crypto'. Getting distribution for 'M2Crypto'. Running easy_install: /usr/bin/python "-c" "from setuptools.command.easy_install import main; main()" "-mUNxd" "/home/leo/opt/m2cryptotest/eggs/tmp5wm_oK" "-q" "/tmp/tmphof_2Jget_dist/M2Crypto-0.20.2.win32.zip" path=/home/leo/opt/m2cryptotest/eggs/setuptools-0.6c12dev_r85381-py2.6.egg error: Couldn't find a setup script in /tmp/tmphof_2Jget_dist/M2Crypto-0.20.2.win32.zip An error occured when trying to install M2Crypto 0.20.2.win32. Look above this message for any errors that were output by easy_install. While: Installing m2c. Getting distribution for 'M2Crypto'. Error: Couldn't install: M2Crypto 0.20.2.win32 AFAICT, This is due to the fact that M2Crypto win32 egg available here: http://chandlerproject.org/pub/Projects/MeTooCrypto/M2Crypto-0.20.2.win32.z… And linked from the project "Home Page" as registered on PyPI takes precedence over the package stored here: http://pypi.python.org/packages/source/M/M2Crypto/M2Crypto-0.20.2.tar.gz And linked from the PyPI page itself. If I'm not mistaken, this is also because "win32" in M2Crypto-0.20.2.win32.zip looks like part of the version, and not the architecture. Is this analysis correct? Is there a quick way to blacklist this package in buildout or setuptools? For the record, I can work-around this by downloading the right M2Crypto package, then doing: bin/buildout setup src/M2Crypto-0.20.2 bdist_egg and moving and unpacking the generated egg in the egg cache directory, but this is really ugly. Cheers, Leo

1 0

Retrieval of python PKG-INFO data for installed packages
by Alan Franzoni 17 Nov '10

17 Nov '10

Hello, is it possible to retrieve the same info which is stored in PKG-INFO for an installed package? I've seen this project: http://pypi.python.org/pypi/pkginfo doesn't anything built in setuptools/distribute/pkg_resources achieve a similar result? e.g., while in a lib, I'd like to do something like: import mymodule get_pkg_info(mymodule).project_name ? -- Alan Franzoni -- contact me at public(a)[mysurname].eu

2 1

Where should I put my tests in my package?
by W. Matthew Wilson 17 Nov '10

17 Nov '10

Right now, I've got a project that started off looking sort of like this: pitz/ pitz/ cmdline/ webapp/ entity/ tests/ test_cmdline.py test_entity.py test_webapp.py In my setup.py file, I have this line packages=find_packages(exclude=[''tests']), so that the tests don't get installed when the code is installed. This works OK for now, but I'm adding more folders under the original folders, like this: pitz/ pitz/ cmdline/ webapp/ handlers/ __init__.py statichandler.py entity/ tests/ test_cmdline.py test_entity.py test_webapp.py test_handlers.py test_statichandler.py It is getting more difficult to figure out the links between test files and code files. I have a few questions: 1. I would like to put lots of tests/ folders next to the code they test, rather than at the top level of the project. How do I make sure the tests folders don't get installed? 2. Should I worry about not installing tests? Should I install them? 3. Is there any pattern I should follow for organizing my tests within my project? Thanks for the help. Matt -- W. Matthew Wilson matt(a)tplus1.com http://tplus1.com

4 3

setup.py script using python interpreter from previous run
by Geoff Bache 10 Nov '10

10 Nov '10

Hi all, I have the following setup.py script: #!/usr/bin/env python from distutils.core import setup scripts=["hello.py"] setup(scripts=scripts) I have two different python installations (using virtualenv) where I wish to install this program. So I do ~/tmp/test_setup/python1/bin/python setup.py install which creates a file at /users/geoff/tmp/test_setup/python1/bin/hello.py, that looks like this: #!/users/geoff/tmp/test_setup/python1/bin/python print "Hello" So far so good. But then I also install it somewhere else: ~/tmp/test_setup/python2/bin/python setup.py install which creates a file at /users/geoff/tmp/test_setup/python2/bin/hello.py which refers to "python1", i..e it has the same contents as the first one. Which is clearly not what I want. Is this a bug? Or have I missed something in my setup.py? It works of course if I remove the generated "build" directory by hand, but it's not so nice to have to remember to do that. (I'm using Python2.6 on Linux) Regards, Geoff Bache

4 6

[RFC] eggbuild
by Manlio Perillo 06 Nov '10

06 Nov '10

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi. I'm pleased to announce the eggbuild package. This is a proof of concept for some ideas I have in mind for Python packages distribution. The package name, the implemented setuptools command names and the API are unstable, and may change in the future. The project is currently available at: http://hg.mperillo.ath.cx/eggbuild. The README and TODO file contain some informations, and I will try to not replicate them here. Basically, the idea is to build a setuptools distribution format that, like PyInstaller, is *self contained* (containing all required packages and all external shared libraries). However, unlike PyInstaller, there are some important differences, listed in the README file. I have tested the eggbuild command with a patched psycopg2 package, on a Linux Debian Squeeze system. Just for information, the resulting egg is 1.4 Mb big, when a normal egg is 156 Kb big. The resulting EGG-INFO\native_libs file is available here: http://paste.pocoo.org/show/285677/ The patch for psycopg2 is available here: http://paste.pocoo.org/show/285662/ The code *seems* to work. When importing the psycopg2 module, the *correct* shared libraries are loaded. At least the correct libpq.so.5 library is used. The other libraries required by libpq.so.5 are searched in the system default location, and I need to check if this can be solved without having to patch each library (adding LD_RPATH). A simple solution is to set LD_LIBRARY_PATH environment variable (but there are some issues to be solved). Now, what I want to implement is a setuptools command that will build a Debian package, with the following features: * pre-install script will create a virtual environment, using virtualenv. The virtualenv should be created in /opt/<pkg-name>. * the package and required packages are stored in the deb data file, in egg binary format, and will be automatically copied to the virtual python installation. The main feature to implement is, however, a full MSI installer. However I don't know how MSI is supposed to work, and I will probably need some help (at least some good tutorial about MSI technology, what can be and what can not be done). I will appreciate comments and suggestions about the eggbuild design and implementation. Thanks Manlio -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkzRxNwACgkQscQJ24LbaUQimACfRhi6kJUbPR8RkOz16Zcjni8T AA8AmQGqdakXHSuZTMc1oKbOaGPJKq2p =Pwqc -----END PGP SIGNATURE-----

2 7

An observation on how system packagers and developers can be friends
by Jim Fulton 05 Nov '10

05 Nov '10

Periodically, in various venues, we discuss the challenges of deploying applications with or in spite of system packaging of Python and system packaging philosophies. (Note that I'm mainly talking g about deploying applications, as opposed to individual Python packages.) In my experience, the conversation usually unfolds with developers (like me:) snarkely saying how annoyed we are and systems packagers (and administrators) explaining all of the rules they have to follow and that we should follow too. In practice, I think the result is usually that developers make an end-run around system packaging system, either building in production, or by building system packages that bundle dependencies to get needed control. The result is that at least some of the system packagers goals are subverted. In my experience, both sides have legitimate goals, but the problem is rarely, if ever, approached from the point of view of recognizing both sets of goals coming up with a (probably new) solution that addresses both sets of goals. (Note that "doing things the way I've always done them" is *not* a valid goal. :) I believe that solutions that address both sets of goals are possible and even practical, but it has to start with a consideration of the underlying goals. Jim -- Jim Fulton

9 11

Re: [Distutils] package data not installed from python .egg file
by P.J. Eby 05 Nov '10

05 Nov '10

At 09:32 AM 11/3/2010 +0100, Roban Hultman Kramer wrote: >Can anyone suggest what I need to do to get the package_data files to >be installed when easy_install unzips the egg file? The issue is the '..' in your data file names; currently setuptools.archive_util refuses to extract files with '..' in their path. I'm going to go ahead and fix this, but even after I do, please note that it will continue to be a problem for versions of easy_install that are out there "in the wild".

2 1

Security issue with Distutils register is still actual
by anatoly techtonik 03 Nov '10

03 Nov '10

Hello, Does anybody care that PyPI password are stored in a well-known location in cleartext and developers are forced to store them when they submit packages for review? http://bugs.python.org/issue9995 -- anatoly t.

3 7

package data not installed from python .egg file
by Roban Hultman Kramer 03 Nov '10

03 Nov '10

I'm trying to include some data files in a python package using the setuptools package_data option. I'm then accessing the files with pkg_resources. This works perfectly when the python .egg file is installed as-is (i.e. still zipped). But when the egg file is unzipped during installation, the data files are not installed. In other words, if I run: python setup.py bdist_egg cd dist sudo easy_install -z EnrichPy-0.1.001-py2.6.egg then the egg file is installed (with the data safely zipped inside) and everything works. On the other hand, if I run sudo easy_install -Z EnrichPy-0.1.001-py2.6.egg then the data files are not installed. I have a directory called EnrichPy-0.1.001-py2.6.egg/enrichpy/ under dist-packages, but it contains only my source files, not my data files. Can anyone suggest what I need to do to get the package_data files to be installed when easy_install unzips the egg file? Notes: The package is available at http://github.com/roban/EnrichPy I can test it by running: import enrichpy.yields enrichpy.yields.Data_vdHG().data If that exits without errors, then pkg_resources is finding the installed data. I asked this question on stackoverflow without response: http://stackoverflow.com/questions/4043315/package-data-not-installed-from-… -- Roban Hultman Kramer Zwicky Fellow Institute for Astronomy ETH Zürich (Swiss Federal Institute of Technology)

1 0