Mailman 3 December 2010 - Distutils-SIG

ImportError running 'test' on namespace package - other package in namespace not found
by Jason R. Coombs April 17, 2020

April 17, 2020

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 April 29, 2018

April 29, 2018

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 April 29, 2018

April 29, 2018

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 April 29, 2018

April 29, 2018

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 April 29, 2018

April 29, 2018

-----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 April 29, 2018

April 29, 2018

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 April 29, 2018

April 29, 2018

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 April 29, 2018

April 29, 2018

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 April 29, 2018

April 29, 2018

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 April 29, 2018

April 29, 2018

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 April 29, 2018

April 29, 2018

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 April 29, 2018

April 29, 2018

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 April 29, 2018

April 29, 2018

3 2

[buildout] branches languishing? (site-packages and distutils scripts)
by Chris Withers April 2, 2012

April 2, 2012

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 June 9, 2011

June 9, 2011

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 April 22, 2011

April 22, 2011

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 Feb. 23, 2011

Feb. 23, 2011

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 Feb. 19, 2011

Feb. 19, 2011

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

Distribute comments
by K. Richard Pixley Jan. 4, 2011

Jan. 4, 2011

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

PEP 345: real-world examples of "virtual" projects (Provides-Release)
by Sridhar Ratnakumar Dec. 24, 2010

Dec. 24, 2010

From https://bitbucket.org/ametaireau/python-peps/src/tip/pep-0345.txt """ Provides-Release (multiple use) ::::::::::::::::::::::::::::::: [...] A release may also provide a "virtual" project name, which does not correspond to any separately-distributed project: such a name might be used to indicate an abstract capability which could be supplied by one of multiple projects. E.g., multiple projects might supply RDBMS bindings for use by a given ORM: each project might declare that it provides ``ORM-bindings``, allowing other projects to depend only on having at most one of them installed. """ 1. I find this to be a strange example. If only one provided project (ORM-bindings) can be installed at any time, what if anyone wants to install more than one DB backends for ORM? 2. What is the expected behavior of 'pip install ORM-bindings'[1]? To pick one of the many projects "providing" ORM-bindings? 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? 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; similarly, "psycopg2" can be provided by psycopg2-pg8.4 and psycopg2-pg9.0. Or, "modwsgi" can be provided by modwsgi-apache2.2, modwsgi-apache2.4. How would PEP 345's "Provides-Release" help, if at all, in describing this scenario? -srid [1] Or substitute `pip` with any package installer (easy_install, distutils2.install, pypm, enstaller).

3 3

The new MSI given by Python 2.7
by cool-RR Dec. 24, 2010

Dec. 24, 2010

I'm making a release of my project today, and I noticed that the MSI created by Python 2.7 when doing `bdist_msi` does not seem to be attached to a specific Python version. Is it safe to supply it for users of Python 2.5-2.7? (My package is pure-Python.) When uploading to PyPI, I'm forced to choose a single Python version for the MSI. What do I do? I don't want people to be mislead to think that it's an MSI only for 2.6 when it works for 2.5-2.7. I tried uploading the same file for all three versions, but PyPI didn't allow this, telling me I already uploaded that file. Please help, I want to make a release today. Thanks, Ram.

3 4

Re: [Distutils] [issue119] setuptools-0.6c11.win32-py2.5 python path recognition problem
by P.J. Eby Dec. 23, 2010

Dec. 23, 2010

At 05:39 AM 12/23/2010 +0000, hm wrote: >I have downloaded setuptools-0.6c11.win32-py2.5.exe and tried to >install it on Windows 7 (64 bit). I have an existing Python >installation. The setuptool recognizes the path, however, puts a >quote around the path. The problem is that it also carries the >quotes around the Python path in the installation directory and >makes a path like: > >"C:\Python25\"\Lib\site-packages\ > >This is an invalid path and in the next step the installer complains >that cannot install the files in the provided path. The setuptool >also does not allow editing this path. Any help is appreciated, asap. This sounds like a problem with the distutils installer for Windows. Have you tried installing any other Python .exe's from PyPI, and do they have the same problem?

1 0

[issue119] setuptools-0.6c11.win32-py2.5 python path recognition problem
by hm Dec. 23, 2010

Dec. 23, 2010

New submission from hm <hmotahary(a)yahoo.com>: I have downloaded setuptools-0.6c11.win32-py2.5.exe and tried to install it on Windows 7 (64 bit). I have an existing Python installation. The setuptool recognizes the path, however, puts a quote around the path. The problem is that it also carries the quotes around the Python path in the installation directory and makes a path like: "C:\Python25\"\Lib\site-packages\ This is an invalid path and in the next step the installer complains that cannot install the files in the provided path. The setuptool also does not allow editing this path. Any help is appreciated, asap. Thank Hamid ---------- messages: 569 nosy: hm priority: bug status: unread title: setuptools-0.6c11.win32-py2.5 python path recognition problem _______________________________________________ Setuptools tracker <setuptools(a)bugs.python.org> <http://bugs.python.org/setuptools/issue119> _______________________________________________

1 0

Buildout or distribute raise unnecessary version conflict?
by Alan Franzoni Dec. 20, 2010

Dec. 20, 2010

Hello, I've got a strange issue with version resolution when using zc.buildout; I don't know if it's zc.buildout specific or it's caused by something which is done by distribute. The example code can be fetched from there: hg clone https://Alan@bitbucket.org/Alan/buildoutversionissue End of output result: Installing test. While: Installing test. Error: There is a version conflict. We already have: zope.testrunner 4.0.0 but asd 0.1.0 requires 'zope.testrunner==4.0.0b1'. If you check within the downloaded eggs, you'll see there's no egg requiring zope.testrunner 4.0.0; there's just zc.recipe.testrunner requiring "zope.testrunner", without any version. if egg A requires "foolib" while egg B requires "foolib==1.0.0", and the latest available version of foolib is "1.0.1", then a version conflict error will arise; it's just as if a "naked" egg dependency is pinned to the latest available version of a package. Is that an intended behaviour? I don't seem to find any evidence of that in distribute or distutils doc. Although specifying a dependency without a version shouldn't be a good practice, it seems quite common - mostly because many people have got full control of the pypi section on their own repo and they can decide what's offered there, so they just specify "mydependency" on their other projects. I think it's quite a wide assumption, by the way. Also, this is not the usualy way dependencies are resolved in most package managers. When using yum (and apt should be quite similar), something like that happens: Scenario: two versions of "mydep" are available: mydep 1.0.0 and 1.0.1 "foo" depends just on mydep "bar" depends on mydep 1.0.0 If I just want to install "foo", I'll get foo and mydep 1.0.1 on my system. But if I try installing both, I'll get foo, bar and mydep 1.0.0, because that will be resolved as the best way to handle all dependencies. Any comment? -- Alan Franzoni -- contact me at public(a)[mysurname].eu

3 8

'python setup.py test' in develop mode?
by Barry Warsaw Dec. 18, 2010

Dec. 18, 2010

Something bugs me about virtualenv, distribute, development, and testing. I figure I'm probably doing something wrong and that y'all will be able to set me straight. I'm working on a new tool called pkgme[1]. It uses distribute and recommends using virtualenv for development. After activating the virtualenv you can do 'python setup.py develop' and do convenient in-place editing so that your changes to the source show up immediately in the running environment. So far so good. However, when I want to run the test suite, it does the equivalent of a 'python setup.py build' and then runs the tests out of the build/lib.{platform}-{version} directory. This actually screws with our tests because (at least currently) the tests are looking for shell scripts and other programs that live in our tree, but are not part of the Python packaging, so don't get built or installed by setup.py. When we do filesystem introspection to try to find the scripts to exec them, it will work when running in develop mode, but fail in the tests, since __file__ points into build/lib.* instead of the source tree. So I'm wondering if other folks have hit similar problems and what best practices can be recommended to deal with this problem. I can think of various hacks around the problem, but don't want to reinvent the wheel. Or do you think that 'python setup.py test' should use the in-place tree and this is Just A Bug? Cheers, -Barry [1] https://launchpad.net/pkgme

4 6

demo and setup.py
by Alessandro Dentella Dec. 18, 2010

Dec. 18, 2010

Hi, i'm new to this list. I hope this question is pertinent to the list, if not please address me to a more appropriate one. I'd like to understand what is the preferred way to cope with demo examples/directory while packaging. I have a classic structure sqlkit-N.n/ sqlkit/ setup.py MANIFEST.in demo/ My goal would be to have a setup so that 'python setup.py sdist' would package also the demo, so that 'python setup.py sdist upload' could be all I need to do to publish it. Is this a reasonable goal? I ask this as I wouldn't know where to place the demo in the target installation. Under Linux that I know pretty well a demo would be under /usr/(local/)/share/doc... but where sould it be placed under Windows? Is this simething that should be taken care of by setuptools? Searching in the docs I never found the 'demo' word and google was not very usefull too. Any hint is appreciated. thanks a lot sandro -- Sandro Dentella *:-) http://www.reteisi.org Soluzioni libere per le scuole http://sqlkit.argolinux.org SQLkit home page - PyGTK/python/sqlalchemy

2 1

stdeb development?
by Sean Ochoa Dec. 16, 2010

Dec. 16, 2010

Hello all. I'm wondering if there is still any effort behind the stdeb package development. I find it super handy for what I do at work, and I'm wondering if there's going to be canonical support and/or further package development done in this area. - Sean

3 2

Obtuse warning from pkg_resources when egg and non-egg distributions clash
by Arve Knudsen Dec. 15, 2010

Dec. 15, 2010

Hello I've just been able to properly identify why pkg_resources at times issues an obtuse (to me at least) warning along these lines: "Module <module> was already imported from <filename>, but <egg> is being added to sys.path". It turns out that really that a non-egg distribution is on the module search path before a corresponding egg distribution. If you run bin/test.py in the attached case, you should see a demonstration of the issue. Right now, it bit me when testing under a continuous integration slave on a machine where the tested project is also installed as an egg. I couldn't for the life of me understand why this warning was being issued, when I couldn't see it on my development machine. Not before painstakingly debugging pkg_resources, did it dawn on me that pkg_resources only complained on the test machine since there was no egg metadata in the source tree (whereas in my development source tree there is). Until debugging pkg_resources I actually didn't know that a directory (i.e., with Python packages) is considered an egg if it has a .egg-info file (with egg metadata) in it. I just hadn't had the motivation yet to learn the egg technology that well. Considering that pkg_resources' rationale for issuing this warning is so difficult to derive from the message, may I suggest please that we modify the message somewhat for added clarity? If it were more explicit, it should be much easier to rectify the warning's cause. My suggestion is a message on this form: "'<egg>' is being added to sys.path, but contained module '<module>' was already imported from '<filename>'. Could this be a non-egg distribution?". From such a warning, it should be possible to derive that the module may have been imported from what is not considered by pkg_resources an egg distribution (such as a clean source tree). Thanks, Arve

1 0

Newbie - Buildout bootstrap error pkg_resources.DistributionNotFound: zc.buildout==1.5.2
by Cops Club Dec. 15, 2010

Dec. 15, 2010

I'm a newbie to Python, so please be patient with me.... 1) On Ubunto 10.10 I used sudo to install python-setuptools then used easy_install to install zc.buildout. 2) I then logged on as a different user (who is not able to sudo) to create my first buildout project. plonesvc@ubuntu:~$ mkdir exercise1 plonesvc@ubuntu:~$ cd exercise1/ plonesvc@ubuntu:~/exercise1$ buildout init Creating '/home/plonesvc/exercise1/buildout.cfg'. Creating directory '/home/plonesvc/exercise1/bin'. Creating directory '/home/plonesvc/exercise1/parts'. Creating directory '/home/plonesvc/exercise1/eggs'. Creating directory '/home/plonesvc/exercise1/develop-eggs'. Generated script '/home/plonesvc/exercise1/bin/buildout'. 3) I downloaded the bootstrap.py from svn plonesvc@ubuntu:~$ wget \ http://svn.zope.org/*checkout*/zc.buildout/trunk/bootstrap/bootstrap.py 4)And tried to run the bootstrap - which failed: plonesvc@ubuntu:~/exercise1$ python bootstrap.py Downloading http://pypi.python.org/packages/2.6/s/setuptools/setuptools-0.6c11-py2.6.egg Traceback (most recent call last): File "bootstrap.py", line 256, in <module> ws.require(requirement) File "/tmp/tmpCfYQ3c/setuptools-0.6c11-py2.6.egg/pkg_resources.py", line 666, in require File "/tmp/tmpCfYQ3c/setuptools-0.6c11-py2.6.egg/pkg_resources.py", line 565, in resolve pkg_resources.DistributionNotFound: zc.buildout==1.5.2 5) I've tried searching for the error via google without success. 6) I have subsequently installed virtual env and setup a new buildout project and run the bootstrap.py successfully. Which, is great but I want to know why I wasn't able to do this without virtual env? I was wondering if someone could explain why step 4 above failed. What was the reason for this? Simon

2 1

Re: [Distutils] How to best install pkg_resources?
by Laura Creighton Dec. 15, 2010

Dec. 15, 2010

Arve: You may find that Bento already does what you want. http://cournape.github.com/Bento/ Laura Creighton

2 1

Re: [Distutils] namespace packages ok to contain code?
by P.J. Eby Dec. 15, 2010

Dec. 15, 2010

At 05:11 PM 12/13/2010 -0600, Brad Allen wrote: >Where I work we're considering a change to moving a group of packages >to using namespaces. We want the namespace paths to reflect a >dependency hierarchy, Note that you don't *need* to use namespace paths to reflect dependencies; the main purpose of namespace packages is to allow you to separately distribute parts of a larger package, and to avoid naming conflicts with code produced by other organizations. (In other words, it's a rare use case that really needs even *two* levels of namespace package; the common use is simply to make one parent namespace package for your organization. In general, the "flat is better than nested" rule of Python still applies. ;-) ) >Some have warned this is not usually done, but no specific problems >with this approach have been identified. Any guidance on this would be >appreciated. As Martin said, don't put code in the __init__.py of a namespace package. (And parent packages of namespace packages count as namespace packages.)

2 1

Re: [Distutils] How to best install pkg_resources?
by P.J. Eby Dec. 14, 2010

Dec. 14, 2010

At 07:30 PM 12/14/2010 +0100, Arve Knudsen wrote: >On Tue, Dec 14, 2010 at 7:22 PM, P.J. Eby ><<mailto:pje@telecommunity.com>pje(a)telecommunity.com> wrote: >At 06:30 PM 12/14/2010 +0100, Arve Knudsen wrote: >Argh :( Can you describe some other way of customizing the install >command that works better with setuptools? > > >That depends on what you're trying to do; but probably it will >involve subclassing the install command rather than simply invoking it. > >What are you trying to customize, anyway? There really aren't many >user-serviceable parts inside; you'd probably be better off >customizing subcommands (like install_lib or some of the build_* commands). > > >I don't have the project in front of me right now, but what I needed >to do was to install something non-Python. That is, if the package >gets installed under <prefix>/lib, the extra data gets installed >under <prefix>/data. The data is part of the project, but not part >of the Python package(s). That's not going to work except in the old-style installation mode. With a setuptools or distribute project, your only places to store data are inside the package or in the metadata (e.g. a subdirectory inside .egg-info).

2 1

Re: [Distutils] How to best install pkg_resources?
by P.J. Eby Dec. 14, 2010

Dec. 14, 2010

At 06:30 PM 12/14/2010 +0100, Arve Knudsen wrote: >Argh :( Can you describe some other way of customizing the install >command that works better with setuptools? That depends on what you're trying to do; but probably it will involve subclassing the install command rather than simply invoking it. What are you trying to customize, anyway? There really aren't many user-serviceable parts inside; you'd probably be better off customizing subcommands (like install_lib or some of the build_* commands).

2 1

egg-links are added to end of sys.path?
by Devin Bayer Dec. 14, 2010

Dec. 14, 2010

Hello. I have been struggling a bit with using buildout for developing eggs and would appreciate some advice. "." is added to the end of sys.path, so the older version of the package (installed in eggs/) is used instead. If I add the following code, it works. But I feel like I'm missing something and this should not be needed: ====================== [python] initialization = import sys sys.path.insert(0, '.') ====================== Any ideas? Thanks, Devin === my buildout.cfg === [buildout] parts = python develop = . [python] recipe = z3c.recipe.scripts eggs = myegg ======================

1 0

Re: [Distutils] How to best install pkg_resources?
by P.J. Eby Dec. 14, 2010

Dec. 14, 2010

At 03:33 PM 12/14/2010 +0100, Arve Knudsen wrote: >I found out how to solve it; I need to call >setuptools.command.install.install.do_egg_install, since >setuptools.command.install.install.run will emulate the standard >distutils behaviour unless it's run directly from setup.py :( This >behaviour was hardly obvious I have to say :( Worse news: unless you emulate that same behavior in *your* install class, you will break bdist_rpm, bdist_wininst, bdist_dumb, etc. In other words, all that non-obvious behavior is there for backward compatibility with other distutils commands that invoke "install" as a subcommand. If you test your now-"fixed" setup.py with them, you will find that your project does terribly broken things. (i.e., try "bdist_rpm" or "bdist_wininst" on a simple setup and your more complex project, and compare the results.)

2 1

Re: [Distutils] How to best install pkg_resources?
by P.J. Eby Dec. 14, 2010

Dec. 14, 2010

At 01:42 PM 12/14/2010 +0100, Arve Knudsen wrote: >Hi > >Using Distribute in my setup.py, how do I best ensure that >pkg_resources gets installed along with my package? I've tried >'install_requires=["setuptools>=0.6"]' as an argument to setup(), >but setuptools didn't get installed. I don't know about Distribute, but it should definitely get installed if you're using setuptools. Under what installation scenario(s) did setuptools *not* get installed?

2 4

How to best install pkg_resources?
by Arve Knudsen Dec. 14, 2010

Dec. 14, 2010

Hi Using Distribute in my setup.py, how do I best ensure that pkg_resources gets installed along with my package? I've tried 'install_requires=["setuptools>=0.6"]' as an argument to setup(), but setuptools didn't get installed. Thanks, Arve

1 0

Re: [Distutils] custom site_dirs location. Solved
by adso 0000 Dec. 14, 2010

Dec. 14, 2010

Yeah. It was that. In this mail this become clear (http://www.mail-archive.com/distutils-sig@python.org/msg00439.html ) it seems the semi-colons are needed in .pth files, and i was using indentation as in python files. Thank you. --adso On Tue, Dec 14, 2010 at 2:23 AM, P.J. Eby <pje(a)telecommunity.com> wrote: > At 01:54 AM 12/14/2010 +0100, adso 0000 wrote: >> >> Hi, >> i am doing something wrong probably, but when i try to get a custom >> site-packages location in Debian, i need to set the contents of >> altinstall.pth just several line with the absolute paths. >> >> If i use the usual python code with site.addsitedir(....) in > > Are you using "import site; site.addsitedir(...)", or just > "site.addsitedir(...)"? > >

1 0

Re: [Distutils] custom site_dirs location
by P.J. Eby Dec. 14, 2010

Dec. 14, 2010

At 01:54 AM 12/14/2010 +0100, adso 0000 wrote: >Hi, >i am doing something wrong probably, but when i try to get a custom >site-packages location in Debian, i need to set the contents of >altinstall.pth just several line with the absolute paths. > >If i use the usual python code with site.addsitedir(....) in Are you using "import site; site.addsitedir(...)", or just "site.addsitedir(...)"?

1 0

custom site_dirs location
by adso 0000 Dec. 14, 2010

Dec. 14, 2010

Hi, i am doing something wrong probably, but when i try to get a custom site-packages location in Debian, i need to set the contents of altinstall.pth just several line with the absolute paths. If i use the usual python code with site.addsitedir(....) in altinstall.pth the directories are not added to sys.path. In sitecustomize.py, by other hand, the code works just fine. btw, i've not found any other manner to set a list for site-dirs in distutils.cfg than this: site_dirs = /path/to/dir1,/path/to/dir2 . Any space, tab or quote makes it fail for me :-S Any clue ? Thank you. --adso this works for me, though --- /home/user/opt/lib/python2.6/site-packages/altinstall.pth -- /home/user/opt/lib/python2.6/site-packages-testing3 /home/user/opt/lib/python2.6/site-packages-testing2 --- /home/user/opt/lib/python2.6/distutils/distutils.cfg --- [easy_install] site_dirs =/home/user/opt/lib/python2.6/site-packages-testing2,/home/user/opt/lib/python2.6/site-packages-testing3

1 0

namespace packages ok to contain code?
by Brad Allen Dec. 14, 2010

Dec. 14, 2010

Where I work we're considering a change to moving a group of packages to using namespaces. We want the namespace paths to reflect a dependency hierarchy, and the current plan requires putting some source code into actual module distributions at the level of some of the namespace packages. Example: toplevel.midlevel toplevel.midlevel.a toplevel.midlevel.b Each of these three is a separate module distribution We want to put core library code in the midlevel. Some have warned this is not usually done, but no specific problems with this approach have been identified. Any guidance on this would be appreciated. Thanks!

2 2

zc.buildout fails to use system-installed dep?
by Alan Franzoni Dec. 13, 2010

Dec. 13, 2010

Hello, there's a problem with zc.buildout that I can reproduce very easily on Ubuntu 10.10 (64 bit) it seems that zc.buildout does not download the dependency from pypi if the very same version is already available in the host system, but then for some reason does not add it to sys.path and/or is unable to use it for some reason; zope.testrunner hence fails on importing zope.interface python-zope.interface is installed at version 3.6.1, and zope.testrunner seems to use that very same dependency. Any workaround? I'll open an issue on launchpad in the weekend. Do this in order to reproduce the problem: # start cd /tmp mkdir -p MyProj/myproj cd MyProj cat <<EOM > buildout.cfg [buildout] parts = test develop = myproj [test] recipe = zc.recipe.testrunner eggs = myproj EOM cat <<EOM > myproj/setup.py from setuptools import setup setup( name="myproj", version="1.0.0", description="myproj" ) EOM wget http://svn.zope.org/*checkout*/zc.buildout/trunk/bootstrap/bootstrap.py python bootstrap.py --distribute && bin/buildout -vvv bin/test #end output from buildout run: alan@afra:/tmp/MyProj$ python bootstrap.py --distribute && bin/buildout Downloading http://pypi.python.org/packages/source/d/distribute/distribute-0.6.14.tar.gz Extracting in /tmp/tmpUAAumj Now working in /tmp/tmpUAAumj/distribute-0.6.14 Building a Distribute egg in /tmp/tmphpzBsD /tmp/tmphpzBsD/distribute-0.6.14-py2.6.egg install_dir /tmp/tmphpzBsD Creating directory '/tmp/MyProj/bin'. Creating directory '/tmp/MyProj/parts'. Creating directory '/tmp/MyProj/eggs'. Creating directory '/tmp/MyProj/develop-eggs'. Generated script '/tmp/MyProj/bin/buildout'. Upgraded: distribute version 0.6.14; restarting. Develop: '/tmp/MyProj/myproj' install_dir /tmp/MyProj/develop-eggs/tmpoKKOZAbuild Getting distribution for 'zc.recipe.testrunner'. install_dir /tmp/MyProj/eggs/tmpQvIfIg zip_safe flag not set; analyzing archive contents... Got zc.recipe.testrunner 1.4.0. Getting distribution for 'z3c.recipe.scripts>=1.0.0'. install_dir /tmp/MyProj/eggs/tmpQPz2RH Got z3c.recipe.scripts 1.0.1. Getting distribution for 'zope.testrunner'. install_dir /tmp/MyProj/eggs/tmpGvi6JB package init file 'src/zope/testrunner/testrunner-ex/__init__.py' not found (or not a regular file) Creating missing __init__.py for zope.testrunner.testrunner-ex Got zope.testrunner 4.0.0. Getting distribution for 'zc.recipe.egg>=1.3.0'. install_dir /tmp/MyProj/eggs/tmp_pJ4gb Got zc.recipe.egg 1.3.2. Getting distribution for 'zope.exceptions'. install_dir /tmp/MyProj/eggs/tmpxRSjc1 Got zope.exceptions 3.6.1. Installing test. Generated script '/tmp/MyProj/bin/test'. alan@afra:/tmp/MyProj$ bin/test Traceback (most recent call last): File "bin/test", line 20, in <module> import zope.testrunner File "/tmp/MyProj/eggs/zope.testrunner-4.0.0-py2.6.egg/zope/testrunner/__init__.py", line 21, in <module> import zope.testrunner.interfaces File "/tmp/MyProj/eggs/zope.testrunner-4.0.0-py2.6.egg/zope/testrunner/interfaces.py", line 21, in <module> import zope.interface ImportError: No module named interface -- Alan Franzoni -- contact me at public(a)[mysurname].eu

7 23

Distribute name for the setup() options.
by Lennart Regebro Dec. 13, 2010

Dec. 13, 2010

A quick look through the Distribute docs shows that we call the settings we give to setup py various things. Both "options" and "arguments" and "parameters" (that last is my fault). We should probably decide on one thing, and go through the docs to make sure it's consistent. I prefer "option", although strictly speaking they *are* keyword arguments. Opinions? //Lennart

1 0

setuptools: zip_safe as command line option ?
by Martin Raspaud Dec. 8, 2010

Dec. 8, 2010

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, Is it possible to tell setuptools to not zip the egg when installing ? I can't seem to find any option regarding this in the command line help... Thanks, Martin -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Remi - http://enigmail.mozdev.org/ iQEcBAEBAgAGBQJM/0c/AAoJEBdvyODiyJI4EXAH/2EVqqAFIBqmiZLMPyQ6Ibd1 CBLZlT12lm9oQ3+HvGIpow+UlWJCC+IRq/MsbUrrlLk1lSQ1lHt+gnjtiinixi5s XfH81ykaEhD0biWKVPHamU6LKjzkUl9UVIji3kUcznkl5clhXXuim7sCYfHYUVrH PyhJgWygK4r7c3bmrpd8VRDPmpRDLb2kFokhNQ+oe3JiX6UGWzVSLG2ohzy7CeDj AIWdadYc6i5QIHXpra5i8TkX2XLRvtYV5Yb5P3znArjc61Gjd7RRQUm83nug9/xV ZMsvPE8KtQsbHXKQHQ9npan+YF2p4LJW/4t/7SZw3pY3UHroTFa6Tyb6tXoSjsE= =GxiC -----END PGP SIGNATURE-----

4 4

Re: [Distutils] Unable to install packages after specifying package version
by P.J. Eby Dec. 8, 2010

Dec. 8, 2010

At 04:04 PM 12/7/2010 +0530, devyan parmar wrote: >On Fri, Dec 3, 2010 at 10:14 PM, P.J. Eby ><<mailto:pje@telecommunity.com>pje(a)telecommunity.com> wrote: >At 04:25 PM 12/3/2010 +0530, devyan parmar wrote: >Hello, > >i am trying to install package from my packageserver using PIP. > >for example: >m trying >/bin/pip install >--extra-index-url=<<http://mypkgserver/dev>http://mypkgserver/dev>http://mypkgserver/dev >package_name==2.4.12b > > >"2.4.12b" is the version of my package but in package server it is >going as "2.4.12b_1" extra part in version is nothing but a build >number which getting generated from hudson JOB. >is setuptool avoids extra build number which goes with my pcakage version ?? > > > No. That's why it's not being found. Ask for > "package_name==2.4.12b-1" instead. > > >Is there any way to avoid the extra hudson build number which is >coming with my package version ?? Er, don't put it in there? > coz i need that build number to check which package build test got > failed...and issue is in package/setup.py i am specifying only > versions of dependent package. Don't use '==', then, use '>='. >and pip install is looking for only those particular version package >in package server, but finds hudson build number attached with >package version which is mismatching with setup.py install requires . > >can you help me how version is getting identified from the package >by setuptools.?? > >Thanks Regards >devyan parmar

1 0

msi installer for 64-bit Windows?
by John Machin Dec. 7, 2010

Dec. 7, 2010

Hello, I'm trying to figure out how to produce a Windows installer for pure-Python packages such that it will "just run" on a 64-bit Windows platform. I'm running a 32-bit Windows (Windows 7 Pro), and the msi produced by python setup.py bdist_msi works just fine on Win 7 Pro. I don't have a win64 platform to test on. The distutils docs for Python 2.7.1 say: ""In most cases, the bdist_msi installer is a better choice than the bdist_wininst installer, because it provides better support for Win64 platforms, allows administrators to perform non-interactive installations, and allows installation through group policies.""" but give no more detail. Running python setup.py bdist_msi --help produces only one item of interest: Options for 'bdist_msi' command: --plat-name (-p) platform name to embed in generated filenames (default: win32) Does the win32 version work on win64? Is the purpose of changing the name solely in order that win64 users are not deterred from using it because the name includes "win32"? Cheers, John

2 1

Re: [Distutils] Unable to install packages after specifying package version
by P.J. Eby Dec. 7, 2010

Dec. 7, 2010

At 04:25 PM 12/3/2010 +0530, devyan parmar wrote: >Hello, > >i am trying to install package from my packageserver using PIP. > >for example: >m trying >/bin/pip install >--extra-index-url=<http://mypkgserver/dev>http://mypkgserver/dev >package_name==2.4.12b > >"2.4.12b" is the version of my package but in package server it is >going as "2.4.12b_1" extra part in version is nothing but a build >number which getting generated from hudson JOB. >is setuptool avoids extra build number which goes with my pcakage version ?? No. That's why it's not being found. Ask for "package_name==2.4.12b-1" instead.

2 1

easy_install from source?
by skip＠pobox.com Dec. 4, 2010

Dec. 4, 2010

I installed the 0.39 version of python-sybase using easy_install -m. That worked fine, but that version is extremely old. Is there a way to use easy_install with the a checkout from the project's version control system? I see this in the help output: --local-snapshots-ok (-l) allow building eggs from local checkouts but how do I specify the location of the local checkout? Thanks, -- Skip Montanaro - skip(a)pobox.com - http://www.smontanaro.net/

2 1

Re: [Distutils] specifying dependencies to latest major/minor
by P.J. Eby Dec. 3, 2010

Dec. 3, 2010

At 03:14 PM 12/3/2010 +0100, Alan Franzoni wrote: >Hello, >I've got some issues with dependency specification; this seems to >apply both to setuptools and distribute. > >Let's suppose I want to have a dependency on a certain library >major.minor , because I want to depend on a certain API - which is >supposed to be stable for that lib unless at least the minor changes - >but I want to pick in any bugfix release they might end up with. > >I'd like to do something like "pick up the latest 1.1 release of mylib" > >The only way to do it seems to be this: > >install_requires = [ "mylib>=1.1, <1.1.999" ] > >if I use just == 1.1 , it picks 1.1.0 . If I use >= 1.1 and <1.2.0, it >will pick beta releases for 1.2 as well. Use ">=1.1,<1.2dev".

1 0

specifying dependencies to latest major/minor
by Alan Franzoni Dec. 3, 2010

Dec. 3, 2010

Hello, I've got some issues with dependency specification; this seems to apply both to setuptools and distribute. Let's suppose I want to have a dependency on a certain library major.minor , because I want to depend on a certain API - which is supposed to be stable for that lib unless at least the minor changes - but I want to pick in any bugfix release they might end up with. I'd like to do something like "pick up the latest 1.1 release of mylib" The only way to do it seems to be this: install_requires = [ "mylib>=1.1, <1.1.999" ] if I use just == 1.1 , it picks 1.1.0 . If I use >= 1.1 and <1.2.0, it will pick beta releases for 1.2 as well. That's quite clumsy, since it's something I do often and it's quite a common practice (I suppose); isn't there any regex/wildcald character support? Would any patch about that be accepted? -- Alan Franzoni -- contact me at public(a)[mysurname].eu

1 0

Unable to install packages after specifying package version
by devyan parmar Dec. 3, 2010

Dec. 3, 2010

Hello, i am trying to install package from my packageserver using PIP. for example: m trying /bin/pip install --extra-index-url=http://mypkgserver/devpackage_name==2.4.12b "2.4.12b" is the version of my package but in package server it is going as "2.4.12b_1" extra part in version is nothing but a build number which getting generated from hudson JOB. is setuptool avoids extra build number which goes with my pcakage version ?? coz if i try to install package it's gives me message "No distributions at all found ". is there anything wrong am doing in package version.?? Thanks Regards Devyan Parmar

2 1

Problem with "custom" version nosetests
by Gora Khargosh Dec. 2, 2010

Dec. 2, 2010

Greetings, I'm trying to get nosetests to run doctests within my source tree, but I get this instead. $ nosetests --with-doctest Usage: This is a custom version of the zc.buildout nosetests script. It is intended to meet a temporary need if you encounter problems with the zc.buildout 1.5 release. nosetests: error: no such option: --with-doctest Can someone tell me why nose would be "replaced" with a custom version and how do I get nosetests to run properly by removing this custom version? Thank you. =) Cheers. -- Gora Khargosh — गोरा ख़रग़ोश

1 1