Mailman 3 March 2008 - Distutils-SIG

virtualenv not respecting --no-site-packages for ZODB3?
by Noah Gift 16 Mar '08

16 Mar '08

I am getting the following behavior when using virtualenv to easy_install ZODB3. [ngift@Macintosh-7][H:10256][J:0]# virtualenv --no-site-packages zodbENV New python executable in zodbENV/bin/python Installing setuptools..........................done. [ngift@Macintosh-7][H:10257][J:0]# zodbENV/bin/easy_install ZODB3 Searching for ZODB3 Best match: ZODB3 3.8.0 Processing ZODB3-3.8.0-py2.5-macosx-10.5-i386.egg Adding ZODB3 3.8.0 to easy-install.pth file Installing mkzeoinst script to /Users/ngift/Documents/writing/IBM/ZODB/ zodbENV/bin Installing fstail script to /Users/ngift/Documents/writing/IBM/ZODB/ zodbENV/bin Installing zeopack script to /Users/ngift/Documents/writing/IBM/ZODB/ zodbENV/bin Installing runzeo script to /Users/ngift/Documents/writing/IBM/ZODB/ zodbENV/bin Installing zeopasswd script to /Users/ngift/Documents/writing/IBM/ZODB/ zodbENV/bin Installing zeoctl script to /Users/ngift/Documents/writing/IBM/ZODB/ zodbENV/bin Installing fsdump script to /Users/ngift/Documents/writing/IBM/ZODB/ zodbENV/bin Installing fsrefs script to /Users/ngift/Documents/writing/IBM/ZODB/ zodbENV/bin Installing repozo script to /Users/ngift/Documents/writing/IBM/ZODB/ zodbENV/bin Installing fsoids script to /Users/ngift/Documents/writing/IBM/ZODB/ zodbENV/bin Using /Library/Python/2.5/site-packages/ZODB3-3.8.0-py2.5-macosx-10.5- i386.egg Processing dependencies for ZODB3 Searching for zope.interface Reading http://pypi.python.org/simple/zope.interface/ Reading http://zope.org/Wikis/Interfaces/FrontPage Best match: zope.interface 3.4.1 Downloading http://pypi.python.org/packages/source/z/zope.interface/zope.interface-3.4.… =b085f4a774adab688e037ad32fbbf08e Processing zope.interface-3.4.1.tar.gz Running zope.interface-3.4.1/setup.py -q bdist_egg --dist-dir /var/ folders/LZ/LZFo5h8JEW4Jzr+ydkXfI++++TI/-Tmp-/easy_install-2eJgo2/ zope.interface-3.4.1/egg-dist-tmp-qzXWo6 Adding zope.interface 3.4.1 to easy-install.pth file Installed /Users/ngift/Documents/writing/IBM/ZODB/zodbENV/lib/ python2.5/site-packages/zope.interface-3.4.1-py2.5-macosx-10.5-i386.egg Finished processing dependencies for ZODB3

1 0

*ugh* - failure to easy_install numpy
by skip＠pobox.com 16 Mar '08

16 Mar '08

I have a new-ish MacBook Pro. When I installed it I used Apple's migration assitant to transfer content from my PowerBook. That left me with lots of Mach-O PPC shared object files. I've been sort of working my way through replacing things. Today I tried reinstalling numpy using easy_install (had been 1.0.1 in Mach-O PPC format, should wind up with 1.0.4 in Mach-O Intel format). I got this rather ugly output: % easy_install numpy /Users/skip/local/lib/python2.6/site-packages/setuptools-0.6c7-py2.6.egg/setuptools/package_index.py:7: DeprecationWarning: the md5 module is deprecated; use hashlib instead from md5 import md5 Searching for numpy Reading http://pypi.python.org/simple/numpy/ Reading http://numeric.scipy.org Reading http://sourceforge.net/project/showfiles.php?group_id=1369&package_id=175103 Reading http://numpy.scipy.org Best match: numpy 1.0.4 Downloading http://downloads.sourceforge.net/numpy/numpy-1.0.4.tar.gz?modtime=119453667… Processing numpy-1.0.4.tar.gz Running numpy-1.0.4/setup.py -q bdist_egg --dist-dir /var/folders/5q/5qTPn6xq2RaWqk+1Ytw3-U+++TI/-Tmp-/easy_install-dLgdmR/numpy-1.0.4/egg-dist-tmp-X0k4SP Running from numpy source directory. non-existing path in '/private/var/folders/5q/5qTPn6xq2RaWqk+1Ytw3-U+++TI/-Tmp-/easy_install-dLgdmR/numpy-1.0.4/numpy/distutils': 'site.cfg' /var/folders/5q/5qTPn6xq2RaWqk+1Ytw3-U+++TI/-Tmp-/easy_install-dLgdmR/numpy-1.0.4/numpy/distutils/misc_util.py:1278: DeprecationWarning: os.popen4 is deprecated. Use the subprocess module. sin, sout = os.popen4('svnversion') Traceback (most recent call last): File "/Users/skip/local/bin/easy_install", line 8, in <module> load_entry_point('setuptools==0.6c7', 'console_scripts', 'easy_install')() File "/Users/skip/local/lib/python2.6/site-packages/setuptools-0.6c7-py2.6.egg/setuptools/command/easy_install.py", line 1670, in main File "/Users/skip/local/lib/python2.6/site-packages/setuptools-0.6c7-py2.6.egg/setuptools/command/easy_install.py", line 1659, in with_ei_usage File "/Users/skip/local/lib/python2.6/site-packages/setuptools-0.6c7-py2.6.egg/setuptools/command/easy_install.py", line 1674, in <lambda> File "/Users/skip/local/lib/python2.6/distutils/core.py", line 151, in setup dist.run_commands() File "/Users/skip/local/lib/python2.6/distutils/dist.py", line 974, in run_commands self.run_command(cmd) File "/Users/skip/local/lib/python2.6/distutils/dist.py", line 994, in run_command cmd_obj.run() File "/Users/skip/local/lib/python2.6/site-packages/setuptools-0.6c7-py2.6.egg/setuptools/command/easy_install.py", line 211, in run File "/Users/skip/local/lib/python2.6/site-packages/setuptools-0.6c7-py2.6.egg/setuptools/command/easy_install.py", line 446, in easy_install File "/Users/skip/local/lib/python2.6/site-packages/setuptools-0.6c7-py2.6.egg/setuptools/command/easy_install.py", line 471, in install_item File "/Users/skip/local/lib/python2.6/site-packages/setuptools-0.6c7-py2.6.egg/setuptools/command/easy_install.py", line 655, in install_eggs File "/Users/skip/local/lib/python2.6/site-packages/setuptools-0.6c7-py2.6.egg/setuptools/command/easy_install.py", line 930, in build_and_install File "/Users/skip/local/lib/python2.6/site-packages/setuptools-0.6c7-py2.6.egg/setuptools/command/easy_install.py", line 919, in run_setup File "/Users/skip/local/lib/python2.6/site-packages/setuptools-0.6c7-py2.6.egg/setuptools/sandbox.py", line 27, in run_setup File "/Users/skip/local/lib/python2.6/site-packages/setuptools-0.6c7-py2.6.egg/setuptools/sandbox.py", line 63, in run File "/Users/skip/local/lib/python2.6/site-packages/setuptools-0.6c7-py2.6.egg/setuptools/sandbox.py", line 29, in <lambda> File "setup.py", line 89, in <module> File "setup.py", line 82, in setup_package File "/var/folders/5q/5qTPn6xq2RaWqk+1Ytw3-U+++TI/-Tmp-/easy_install-dLgdmR/numpy-1.0.4/numpy/distutils/core.py", line 145, in setup File "setup.py", line 49, in configuration File "/var/folders/5q/5qTPn6xq2RaWqk+1Ytw3-U+++TI/-Tmp-/easy_install-dLgdmR/numpy-1.0.4/numpy/distutils/misc_util.py", line 834, in add_subpackage File "/var/folders/5q/5qTPn6xq2RaWqk+1Ytw3-U+++TI/-Tmp-/easy_install-dLgdmR/numpy-1.0.4/numpy/distutils/misc_util.py", line 817, in get_subpackage File "/var/folders/5q/5qTPn6xq2RaWqk+1Ytw3-U+++TI/-Tmp-/easy_install-dLgdmR/numpy-1.0.4/numpy/distutils/misc_util.py", line 764, in _get_configuration_from_setup_py File "numpy/setup.py", line 9, in configuration File "/var/folders/5q/5qTPn6xq2RaWqk+1Ytw3-U+++TI/-Tmp-/easy_install-dLgdmR/numpy-1.0.4/numpy/distutils/misc_util.py", line 834, in add_subpackage File "/var/folders/5q/5qTPn6xq2RaWqk+1Ytw3-U+++TI/-Tmp-/easy_install-dLgdmR/numpy-1.0.4/numpy/distutils/misc_util.py", line 817, in get_subpackage File "/var/folders/5q/5qTPn6xq2RaWqk+1Ytw3-U+++TI/-Tmp-/easy_install-dLgdmR/numpy-1.0.4/numpy/distutils/misc_util.py", line 764, in _get_configuration_from_setup_py File "/private/var/folders/5q/5qTPn6xq2RaWqk+1Ytw3-U+++TI/-Tmp-/easy_install-dLgdmR/numpy-1.0.4/numpy/core/setup.py", line 246, in configuration File "/var/folders/5q/5qTPn6xq2RaWqk+1Ytw3-U+++TI/-Tmp-/easy_install-dLgdmR/numpy-1.0.4/numpy/distutils/system_info.py", line 267, in get_info File "/var/folders/5q/5qTPn6xq2RaWqk+1Ytw3-U+++TI/-Tmp-/easy_install-dLgdmR/numpy-1.0.4/numpy/distutils/system_info.py", line 366, in __init__ File "/var/folders/5q/5qTPn6xq2RaWqk+1Ytw3-U+++TI/-Tmp-/easy_install-dLgdmR/numpy-1.0.4/numpy/distutils/system_info.py", line 374, in parse_config_files File "/Users/skip/local/lib/python2.6/ConfigParser.py", line 242, in add_section raise ValueError, 'Invalid section name: %s' % section ValueError: Invalid section name: DEFAULT Any idea what the problem might be? I'm using easy_install 0.6c7 with Python 2.6 (Subversion checkout). I don't know if 0.6c7 is the most recent version or not. Thanks, -- Skip Montanaro - skip(a)pobox.com - http://www.webfast.com/~skip/

3 3

moving a development egg over to a production server not using buildout...
by michael nt milne 13 Mar '08

13 Mar '08

Hi Is there some special command that is required for packing up an egg which has been in development and is sitting in a buildout /src directory, over to a live server. This server isn't using a buildout config so it will go straight into site-packages. Does the egg need to be zipped up before it can be easy_installed? I've had a look at this page http://peak.telecommunity.com/DevCenter/EasyInstall#command-line-options What I am getting is a single .egg file and no folder structure for the egg within site-packages. Thanks -- michael

1 0

offline mode for Windows buildout -o or -No doesn't work...any alternatives?
by Michael NT Milne 11 Mar '08

11 Mar '08

Been told to try this post from Plone users on this list.... This is infuriating. Each time we install a new egg we have to run buildout in online mode as buildout -o or buildout -No just produces an invalid command error. buildout –c c:\Plone\'yoursitename'\buildout.cfg The above works but it re-installs new eggs etc alongside the old eggs and the site breaks as below. When re-running buildout, Zope uses the eggs with the higher numbers. Do you need to change anything to make this work? Also has anyone got Windows buildouts running in offline mode? It seems the only way to fix this is to delete the new eggs etc that have been fetched. 2008-03-10T16:45:09 ERROR Application Couldn't install Five Traceback (most recent call last): File "D:\Plone3\Zope\lib\python\OFS\Application.py", line 786, in install_product initmethod(context) File "D:\Plone3\Zope\lib\python\Products\Five\__init__.py", line 28, in initialize zcml.load_site() File "D:\Plone3\Zope\lib\python\Products\Five\zcml.py", line 53, in load_site _context = xmlconfig.file(file) File "D:\Plone3\Zope\lib\python\zope\configuration\xmlconfig.py", line 579, in file include(context, name, package) File "D:\Plone3\Zope\lib\python\zope\configuration\xmlconfig.py", line 515, in include processxmlfile(f, context) File "D:\Plone3\Zope\lib\python\zope\configuration\xmlconfig.py", line 370, in processxmlfile parser.parse(src) File "D:\Plone3\Python\Lib\site-packages\_xmlplus\sax\expatreader.py", line 109, in parse xmlreader.IncrementalParser.parse(self, source) File "D:\Plone3\Python\Lib\site-packages\_xmlplus\sax\xmlreader.py", line 123, in parse self.feed(buffer) File "D:\Plone3\Python\Lib\site-packages\_xmlplus\sax\expatreader.py", line 216, in feed self._parser.Parse(data, isFinal) File "D:\Plone3\Python\Lib\site-packages\_xmlplus\sax\expatreader.py", line 364, in end_element_ns self._cont_handler.endElementNS(pair, None) File "D:\Plone3\Zope\lib\python\zope\configuration\xmlconfig.py", line 349, in endElementNS self.context.end() File "D:\Plone3\Zope\lib\python\zope\configuration\config.py", line 544, in end self.stack.pop().finish() File "D:\Plone3\Zope\lib\python\zope\configuration\config.py", line 692, in finish actions = self.handler(context, **args) File "D:\Plone3\Zope\lib\python\Products\Five\fiveconfigure.py", line 78, in loadProducts handleBrokenProduct(product) File "D:\Plone3\Zope\lib\python\Products\Five\fiveconfigure.py", line 76, in loadProducts xmlconfig.include(_context, zcml, package=product) File "D:\Plone3\Zope\lib\python\zope\configuration\xmlconfig.py", line 515, in include processxmlfile(f, context) File "D:\Plone3\Zope\lib\python\zope\configuration\xmlconfig.py", line 370, in processxmlfile parser.parse(src) File "D:\Plone3\Python\Lib\site-packages\_xmlplus\sax\expatreader.py", line 109, in parse xmlreader.IncrementalParser.parse(self, source) File "D:\Plone3\Python\Lib\site-packages\_xmlplus\sax\xmlreader.py", line 123, in parse self.feed(buffer) File "D:\Plone3\Python\Lib\site-packages\_xmlplus\sax\expatreader.py", line 216, in feed self._parser.Parse(data, isFinal) File "D:\Plone3\Python\Lib\site-packages\_xmlplus\sax\expatreader.py", line 364, in end_element_ns self._cont_handler.endElementNS(pair, None) File "D:\Plone3\Zope\lib\python\zope\configuration\xmlconfig.py", line 349, in endElementNS self.context.end() File "D:\Plone3\Zope\lib\python\zope\configuration\config.py", line 544, in end self.stack.pop().finish() File "D:\Plone3\Zope\lib\python\zope\configuration\config.py", line 692, in finish actions = self.handler(context, **args) File "D:\Plone3\Zope\lib\python\zope\configuration\xmlconfig.py", line 515, in include processxmlfile(f, context) File "D:\Plone3\Zope\lib\python\zope\configuration\xmlconfig.py", line 370, in processxmlfile parser.parse(src) File "D:\Plone3\Python\Lib\site-packages\_xmlplus\sax\expatreader.py", line 109, in parse xmlreader.IncrementalParser.parse(self, source) File "D:\Plone3\Python\Lib\site-packages\_xmlplus\sax\xmlreader.py", line 123, in parse self.feed(buffer) File "D:\Plone3\Python\Lib\site-packages\_xmlplus\sax\expatreader.py", line 216, in feed self._parser.Parse(data, isFinal) File "D:\Plone3\Python\Lib\site-packages\_xmlplus\sax\expatreader.py", line 364, in end_element_ns self._cont_handler.endElementNS(pair, None) File "D:\Plone3\Zope\lib\python\zope\configuration\xmlconfig.py", line 349, in endElementNS self.context.end() File "D:\Plone3\Zope\lib\python\zope\configuration\config.py", line 544, in end self.stack.pop().finish() File "D:\Plone3\Zope\lib\python\zope\configuration\config.py", line 692, in finish actions = self.handler(context, **args) File "D:\Plone3\Zope\lib\python\zope\configuration\xmlconfig.py", line 515, in include processxmlfile(f, context) File "D:\Plone3\Zope\lib\python\zope\configuration\xmlconfig.py", line 370, in processxmlfile parser.parse(src) File "D:\Plone3\Python\Lib\site-packages\_xmlplus\sax\expatreader.py", line 109, in parse xmlreader.IncrementalParser.parse(self, source) File "D:\Plone3\Python\Lib\site-packages\_xmlplus\sax\xmlreader.py", line 123, in parse self.feed(buffer) File "D:\Plone3\Python\Lib\site-packages\_xmlplus\sax\expatreader.py", line 216, in feed self._parser.Parse(data, isFinal) File "D:\Plone3\Python\Lib\site-packages\_xmlplus\sax\expatreader.py", line 353, in start_element_ns AttributesNSImpl(newattrs, qnames)) File "D:\Plone3\Zope\lib\python\zope\configuration\xmlconfig.py", line 222, in startElementNS self.context.begin(name, data, info) File "D:\Plone3\Zope\lib\python\zope\configuration\config.py", line 541, in begin self.stack.append(self.stack[-1].contained(__name, __data, __info)) File "D:\Plone3\Zope\lib\python\zope\configuration\config.py", line 842, in contained return RootStackItem.contained(self, name, data, info) File "D:\Plone3\Zope\lib\python\zope\configuration\config.py", line 710, in contained factory = self.context.factory(self.context, name) File "D:\Plone3\Zope\lib\python\zope\configuration\config.py", line 487, in factory raise ConfigurationError("Unknown directive", ns, n) ZopeXMLConfigurationError: File "d:\Plone3\Insite2\parts\instance\etc\site.zcml", line 15.2-15.23 ZopeXMLConfigurationError: File "d:\Plone3\Data\Products\CMFPlone\configure.zcml", line 8.2-8.46 ZopeXMLConfigurationError: File "d:\plone3\insite2\eggs\plone.app.contentrules-1.1.0a1- py2.4.egg\plone\app\contentrules\configure.zcml", line 22.4-22.39 ZopeXMLConfigurationError: File "d:\plone3\insite2\eggs\plone.app.contentrules-1.1.0a1- py2.4.egg\plone\app\contentrules\exportimport\configure.zcml", line 16.4 ConfigurationError: ('Unknown directive', u'http://namespaces.zope.org/genericsetup', u'importStep')

5 15

bdist_wininst and Vista User Account Control (UAC)
by Mark Hammond 10 Mar '08

10 Mar '08

The pywin32 extensions require (well, prefer) administrative access during installation - certain files are copied to the System32 directory and the registry at HKEY_LOCAL_MACHINE is written to. Also, if I understand correctly, if Python happened to be installed into "\Program Files", admin access would be required to create any files in that directory tree - I'm not sure what permissions the \PythonXX directory are created with, but its not unreasable to assume that some shops might choose to secure that directory similarly to "\Program Files". The simplest way to achieve this for bdist_wininst installations is to include some magic in a "manifest". I've confirmed that once this magic is added, programs created by bdist_wininst get the little "shield" icon overlay and prompt for elevation before starting the executable. A problem here is that not all installations will require admin access - eg, a user who installed Python just for themselves will not need elevation to install an extension. A solution here would be for the installer to *not* be marked as requiring elevation, then sniffing the registry to make an educated guess (eg, HKLM\Software\Python\PythonCore\2.5 existing could indicate admin access is required). If it finds elevation is required, it would spawn another copy of itself with elevation requested, and terminate. This will have a side-effect of meaning the installer never gets the "shield" overlay, meaning the user will not be expecting to be prompted - but that is something we can live with. However, there is a complication here. Any "pure python" packages are not tied to a particular Python version, so the user can choose what installed Python version to use. Hence, in the general case, we can only determine if admin is required after the UI has opened and the user has selected the Python version. Arranging for the new "elevated" child process at this point will be (a) ugly, as the UI will vanish before the child process displays its GUI and (b) would require additional command-line processing logic - ie, passing the target directory to the child process. If we could make the determination *before* the GUI opens, it would appear seamless and would not require special command-line handling (the child process just does everything) So I see a few alternatives, but none are very desirable: * Only make this "admin required" check if a specific version of Python is necessary (ie, the package contains extension modules). This would leave pure-python packages out in the cold. * Live with the ugly UI that would result in performing that check after the Python version has been selected, and add the command-line processing necessary to make this work. * Ignore the issue and try to educate people that they must explicitly use "Run as Administrator" for such packages on Vista. I'm wondering if anyone has any opinions or thoughts on how we should handle this? Cheers, Mark

4 11

Re: [Distutils] [Catalog-sig] requested Trove Classifier: "Framework :: Setuptools Plugin"
by zooko 08 Mar '08

08 Mar '08

On Mar 8, 2008, at 7:57 PM, Richard Jones wrote: > OK, I've added "Framework :: Setuptools Plugin" Hooray! I've added the first three setuptools plugins to be marked with that classifier. This search shows all packages on pypi which have the "Framework :: Setuptools Plugin" classifier: http://pypi.python.org/pypi?:action=browse&c=524 Regards, Zooko

1 0

Encoding of metadata?
by Andreas Jung 08 Mar '08

08 Mar '08

Hi, are there any recommendations or constraints for the encoding of package metadata - both for PyPI and the setuptools internals? Although most of us write their metadata in English, we do have author names with accented characters...it's unclear if iso-8859-15 or utf-8 is preferred in this case (or even unicode strings)...what's the recommendation for the non-ascii world? Andreas -- ZOPYX Ltd. & Co. KG - Charlottenstr. 37/1 - 72070 Tübingen - Germany Web: www.zopyx.com - Email: info(a)zopyx.com - Phone +49 - 7071 - 793376 Registergericht: Amtsgericht Stuttgart, Handelsregister A 381535 Geschäftsführer/Gesellschafter: ZOPYX Limited, Birmingham, UK ------------------------------------------------------------------------ E-Publishing, Python, Zope & Plone development, Consulting

3 3

Re: [Distutils] Shared libs with setuptools/distutils ?
by Phillip J. Eby 07 Mar '08

07 Mar '08

At 06:11 PM 3/7/2008 -0800, Andi Vajda wrote: >If I want to support multiple Python extension modules built with >JCC to run in the same Python process and hence share the same Java >VM, there is some code between these modules that needs to be shared. > >Currently, the JCC runtime code (not much, really) is compiled into >each JCC-built extension module. There is one C++ class, JCCEnv, >that really needs to be shared among all JCC-built modules. Building >that class into a shared library (instead of a python module >library) could be to be the way to go. Then every such module would >be linked against this shared library. > >I gave this a quick manual try on Mac and it seems to work. > >But do distutils or setuptools have built-in ways of building a >regular shared library (in particular, on Mac OS X, a .dylib, not a >bundle) or is there some hacking needed there still ? (google shows >that there have been nibbles of interest over the past years about >this but it's unclear whether this was done or not). It would make >the JCC build considerably more complicated if I had to add >hand-crafted code for each and every platform/compiler that is >supported by JCC (that list is growing). Having a distutils or >setuptools way of building a regular shared library would be very >helpful here. Has support for that that been added yet ? Not really, but there is some experimental code in the setuptools trunk, IIRC. If you look at the 'tests/test_shlib' subdirectory there is some sample code for building a shared library. I don't know if it works right on OS X... and there were some hairy things involved in doing it on Linux. Patches welcome. :) (Chances are good, though, that you'll be better off using the import + API struct approach to sharing stuff. IIRC, there are still a lot of hoops to jump through to get shared libs working on OS X and Linux.)

2 1

[zc.buildout] find-links does not deal with two-level hierarchy
by Andreas Jung 07 Mar '08

07 Mar '08

Hi, we have a local fileserver with a two-level hierarchy for egg -something like: haufe.eggserver +--- haufe.eggserver-0.1.0.egg +--- haufe.recipe.svnsetup +--- .... easy_install -i http://our-server/egg haufe.recipe.svnsetup works fine with this two-level hierarchy. Using the URL within the find-links option of my buildout.cfg does not work (Error: Could not find a distribution...) for a part with recipe=haufe.recipe.svnsetup. Bug or feature? Andreas

4 4

Tahoe
by Raphael Ritz 07 Mar '08

07 Mar '08

http://allmydata.org/trac/tahoe something for the software center? Raphael

1 1