Mailman 3 July 2007 - Distutils-SIG

cross-compiling using distutils
by Mark Hammond 18 Jul '07

18 Jul '07

Hi all, I'm making good progress on using bdist_msi to package up x64 versions of the pywin32 extensions. On the way I've struck a number of issues. In an effort to try and keey the discussions focussed, I'll create new threads for each of them, and the first cab off the rank is cross-compilation. IIUC, the only way to build Python or Python extensions using VS2003 is to cross-compile from a 32bit platform. Although this requirement is only short term, in the longer term we should support cross-compilation to prevent a Windows developer needing access to all architectures just to create a build. Here are the problems I had: * The dev box needs access to both a 32bit and a 64bit version of Python - the 32bit one to execute Python itself, and the 64bit one to link against. * PYTHONHOME had to be set to the x64 version of Python when running the build, otherwise the link would fail as it tries to use the 32bit python.lib * '/MACHINE:AMD64' or '/MACHINE:Itanium' manually needs to be added to the link commandline. * '/D_M_X64' had to be passed to the compiler (which seems unusual, but I didn't dig too deep into this) One way to approach this might be to add a "global" option to distutils. It might be possible to call it --python_bin_dir, which would point at the libraries for the target system (and we could attempt to sniff the architecture from them). It would need to be a 'global' option as many commands may need to know the target (eg, bdist_msi would also need to know) and distutils.util.get_platform() would need to change to reflect the target platform, not the platform being used to perform the build. msvccompiler.get_build_architecture() could also change to take advantage of this and grow support for /MACHINE etc. Does anyone have any thoughts on this? I'm happy to come up with a patch, but I'm looking for direction (or even just encouragement <wink>) Thanks, Mark

1 0

unattended install
by vadim suvorov 17 Jul '07

17 Jul '07

I have a customer who has many (Windows) computers on which Python and related packages must be installed/updated on regular bases. One of their concerns is wininst based packages, which do not allow unattended installation. Newer and greater MSI helps, but there are legacy packages. Can you give me opinion: 1) Why pywin32 (Mark Hammond) is continued to be distributed in wininst form? 2) If one prepares MSI package, are there foreseeable snags to distribute it in 2.4 environment? 3) I offered to consider development of wininst to msi (ready package) converter. Is it stupid suggestion, or is it feasable (and easier than silencing of wininst)? Would there be interest for such converter (my customer is willing to contribute to Python project)? Thank you!

2 4

[easy_install] won't upgrade egg from 1.0.9 -> 1.0.10
by Andreas Jung 17 Jul '07

17 Jul '07

I uploaded z3c.sqlalchemy 1.0.10 to Cheeseshop. easy_install -U z3c.sqlalchemy won't upgrade an installed 1.0.9 egg to the new version unless I pass the current version as "z3c.sqlalchemy==1.0.10". Bug or feature? Andreas

2 1

Newbie questions about setuptools
by Edward Ream 16 Jul '07

16 Jul '07

I have some questions and comments about setuptools and easy_install. What I like best about setuptools is that setup eliminates the need to maintain manifest.in and MANIFEST files. Assuming that everything in the cvs tree is part of the distribution is a clever idea, and it works for me. This is reason enough for me to want to use setuptools. However, I have the following problems with setuptools. These are serious enough so that for now I just use setuptools to create .zip files. 1. On both XP and Ubuntu, running python setup.py bdist_egg gives a .egg file with a suffix of py2.5.egg, even though the version arg to setup is '4.4.3preview9' I was expecting a suffix of all.egg, because platforms = ['all',] Can anyone explain what is going on? Here is the complete call to setup: setuptools.setup ( name='leo', version='4.4.3preview9', author='Edward K. Ream', author_email='edreamleo(a)charter.net', url='http://webpages.charter.net/edreamleo/front.html', download_url='http://downloads.sourceforge.net/leo/leo-4.4.3preview9.egg', packages = setuptools.find_packages(), include_package_data = True, exclude_package_data = { '': ['*.pyc','*.pyo']}, zip_safe=False, install_requires=[], description = 'Leo: Literate Editor with Outlines', license='Python', platforms=['all',], long_description = long_description, keywords = 'outline, outliner, ide, editor, literate programming', ) 2. The resulting egg file is much larger than the .zip file created by 'python setup.py sdist' in spite of exclude_package_data = { '': ['*.pyc','*.pyo']}, Is there any way to exclude .pyc and .pyo files? 3. 'python setup.py register' works fine, but 'python setup.py upload' fails with an 'invalid request' returned from the server. Maybe because the egg is over 8Meg? 4. 'easy_install leo' is supposed to use the download_url link arg. This is a great idea. Alas, for me it is spoiled by the setuptools pre/post release naming convention. The problem is that this convention is applied to all the links on the download_url page. Because I can't upload to the Python Cheese Shop, I used Leo's SourceForge download page for the main Leo project. The setup.py script is supposed to find the latest release on the page, but setup.py thinks that the latest match is something like Leo-4.2.1.zip (!!) This in spite of the fact that Leo-4.4.3rc1.zip exists on the page. I can't change the filenames on Leo's SourceForge page, and I can't change setuptools's naming conventions. How is 'easy_install leo' going to find the proper version? 5. setuptools is advertised as an 0.x release. This post appeared over a year ago, http://bitworking.org/news/Please_stop_using_setuptools__at_least_exclusive… This post may be obsolete, but it troubles me. I suppose I wouldn't worry so much were it not for these other issues. Any help would be greatly appreciated. Thanks. Edward -------------------------------------------------------------------- Edward K. Ream email: edreamleo(a)charter.net Leo: http://webpages.charter.net/edreamleo/front.html --------------------------------------------------------------------

5 16

Empty directories in eggs
by Martin Aspeli 15 Jul '07

15 Jul '07

Hi, I tried to build an egg from this tag, using bdist_egg and sdist: http://svn.plone.org/svn/collective/ZopeSkel/tags/0.5/ However, the packaged egg lost several directories, such as: http://svn.plone.org/svn/collective/ZopeSkel/tags/0.5/zopeskel/templates/pl… These are empty, but under version control. To get them into the egg (I need it because it's part of a Paste Script template which expects the empty directories to be there), I had to add some mostly-empty (if slightly useful) README.txt files (on the 0.6 tag). Bug or feature? ;-) Martin -- Acquisition is a jealous mistress

1 0

Buildout error reporting - connection refused
by Martin Aspeli 15 Jul '07

15 Jul '07

Hi Jim & co, I just ran a buildout and got this error. It went away again (I guess it was a server going down), but it annoyed me that I couldn't work out *which* URL it was trying to connect to that got refused. Could buildout produce a bit more information in this case? Also - I had a find-link at this point that I know was down. It is not the link for python-openid, so it shouldn't matter, it's only a backup mirror (which atm is even empty). But would setuptools/buildout bomb out regardless, if one of the find-links was down? Thanks, Martin $ ./bin/buildout -vv Installing 'zc.buildout', 'setuptools'. We have the best distribution that satisfies 'zc.buildout'. Picked: zc.buildout = 1.0.0b28 We have the best distribution that satisfies 'setuptools'. Picked: setuptools = 0.6c6 Installing 'plone.recipe.plone'. We have the best distribution that satisfies 'plone.recipe.plone'. Adding find link 'http://download.zope.org/distribution/' from plone.recipe.plone 3.0rc1 Picked: plone.recipe.plone = 3.0rc1 Getting required 'plone.recipe.distros' required by plone.recipe.plone 3.0rc1. We have the best distribution that satisfies 'plone.recipe.distros'. Picked: plone.recipe.distros = 0.2 Getting required 'zc.recipe.egg' required by plone.recipe.plone 3.0rc1. We have the best distribution that satisfies 'zc.recipe.egg'. Picked: zc.recipe.egg = 1.0.0b6 Installing 'plone.recipe.zope2install'. We have the best distribution that satisfies 'plone.recipe.zope2install'. Adding find link 'http://download.zope.org/distribution/' from plone.recipe.zope2install 0.1 Picked: plone.recipe.zope2install = 0.1 Installing 'plone.recipe.zope2instance'. We have the best distribution that satisfies 'plone.recipe.zope2instance'. Adding find link 'http://download.zope.org/distribution/' from plone.recipe.zope2instance 0.6.1 Picked: plone.recipe.zope2instance = 0.6.1 Configuration data: [zope2] executable = /opt/local/Library/Frameworks/Python.framework/Versions/2.4/bin/python location = /Users/optilude/tmp/eggs/zopeskel/rc1/parts/zope2 recipe = plone.recipe.zope2install url = http://www.zope.org/Products/Zope/2.10.4/Zope-2.10.4-final.tgz [buildout] bin-directory = /Users/optilude/tmp/eggs/zopeskel/rc1/bin develop = develop-eggs-directory = /Users/optilude/tmp/eggs/zopeskel/rc1/develop-eggs directory = /Users/optilude/tmp/eggs/zopeskel/rc1 download-directory = /Users/optilude/tmp/eggs/zopeskel/rc1/downloads eggs = eggs-directory = /Users/optilude/.buildout/eggs executable = /opt/local/Library/Frameworks/Python.framework/Versions/2.4/bin/python find-links = installed = /Users/optilude/tmp/eggs/zopeskel/rc1/.installed.cfg log-format = log-level = INFO newest = true offline = false parts = %(__buildout_space_n__)splone zope2 productdistros instance zopepy parts-directory = /Users/optilude/tmp/eggs/zopeskel/rc1/parts python = buildout verbosity = 20 [productdistros] location = /Users/optilude/tmp/eggs/zopeskel/rc1/parts/productdistros nested-packages = prefix = /Users/optilude/tmp/eggs/zopeskel/rc1/parts/productdistros recipe = plone.recipe.distros urls = version-suffix-packages = [instance] _b = /Users/optilude/tmp/eggs/zopeskel/rc1/bin _d = /Users/optilude/tmp/eggs/zopeskel/rc1/develop-eggs _e = /Users/optilude/.buildout/eggs bin-directory = /Users/optilude/tmp/eggs/zopeskel/rc1/bin debug-mode = on develop-eggs-directory = /Users/optilude/tmp/eggs/zopeskel/rc1/develop-eggs eggs = %(__buildout_space_n__)s%(__buildout_space_n__)sarchetypes.kss==1.2-rc1.1 kss.core==1.2-rc1.1 plone.app.content==1.0rc1 plone.app.contentmenu==1.0rc1 plone.app.contentrules==1.0rc1 plone.app.controlpanel==1.0rc1 plone.app.customerize==1.0rc1 plone.app.form==1.0rc1 plone.app.i18n==1.0rc1 plone.app.iterate==1.0rc1 plone.app.kss==1.2-rc1.1 plone.app.layout==1.0rc1 plone.app.linkintegrity==1.0rc1.1 plone.app.openid==1.0rc1 plone.app.portlets==1.0rc1 plone.app.redirector==1.0rc1 plone.app.viewletmanager==1.0rc1 plone.app.vocabularies==1.0rc1 plone.app.workflow==1.0rc1 plone.contentrules==1.0rc1 plone.fieldsets==1.0rc1 plone.i18n==1.0rc1 plone.intelligenttext==1.0rc1 plone.locking==1.0rc1 plone.memoize==1.0rc1 plone.openid==1.0rc1 plone.portlets==1.0rc1 plone.session==1.0rc1 plone.theme==1.0rc1 wicked==1.1.3 five.customerize==0.1.3 five.localsitemanager==0.2 eggs-directory = /Users/optilude/.buildout/eggs executable = /opt/local/Library/Frameworks/Python.framework/Versions/2.4/bin/python http-address = 8080 location = /Users/optilude/tmp/eggs/zopeskel/rc1/parts/instance products = %(__buildout_space_n__)s/Users/optilude/tmp/eggs/zopeskel/rc1/products /Users/optilude/tmp/eggs/zopeskel/rc1/parts/productdistros /Users/optilude/tmp/eggs/zopeskel/rc1/parts/plone recipe = plone.recipe.zope2instance scripts = user = admin:admin verbose-security = on zcml = zope2-location = /Users/optilude/tmp/eggs/zopeskel/rc1/parts/zope2 [zopepy] _b = /Users/optilude/tmp/eggs/zopeskel/rc1/bin _d = /Users/optilude/tmp/eggs/zopeskel/rc1/develop-eggs _e = /Users/optilude/.buildout/eggs bin-directory = /Users/optilude/tmp/eggs/zopeskel/rc1/bin develop-eggs-directory = /Users/optilude/tmp/eggs/zopeskel/rc1/develop-eggs eggs = %(__buildout_space_n__)s%(__buildout_space_n__)sarchetypes.kss==1.2-rc1.1 kss.core==1.2-rc1.1 plone.app.content==1.0rc1 plone.app.contentmenu==1.0rc1 plone.app.contentrules==1.0rc1 plone.app.controlpanel==1.0rc1 plone.app.customerize==1.0rc1 plone.app.form==1.0rc1 plone.app.i18n==1.0rc1 plone.app.iterate==1.0rc1 plone.app.kss==1.2-rc1.1 plone.app.layout==1.0rc1 plone.app.linkintegrity==1.0rc1.1 plone.app.openid==1.0rc1 plone.app.portlets==1.0rc1 plone.app.redirector==1.0rc1 plone.app.viewletmanager==1.0rc1 plone.app.vocabularies==1.0rc1 plone.app.workflow==1.0rc1 plone.contentrules==1.0rc1 plone.fieldsets==1.0rc1 plone.i18n==1.0rc1 plone.intelligenttext==1.0rc1 plone.locking==1.0rc1 plone.memoize==1.0rc1 plone.openid==1.0rc1 plone.portlets==1.0rc1 plone.session==1.0rc1 plone.theme==1.0rc1 wicked==1.1.3 five.customerize==0.1.3 five.localsitemanager==0.2 eggs-directory = /Users/optilude/.buildout/eggs executable = /opt/local/Library/Frameworks/Python.framework/Versions/2.4/bin/python extra-paths = /Users/optilude/tmp/eggs/zopeskel/rc1/parts/zope2/lib/python interpreter = zopepy recipe = zc.recipe.egg scripts = zopepy [plone] _b = /Users/optilude/tmp/eggs/zopeskel/rc1/bin _d = /Users/optilude/tmp/eggs/zopeskel/rc1/develop-eggs _e = /Users/optilude/.buildout/eggs bin-directory = /Users/optilude/tmp/eggs/zopeskel/rc1/bin develop-eggs-directory = /Users/optilude/tmp/eggs/zopeskel/rc1/develop-eggs eggs = archetypes.kss==1.2-rc1.1 kss.core==1.2-rc1.1 plone.app.content==1.0rc1 plone.app.contentmenu==1.0rc1 plone.app.contentrules==1.0rc1 plone.app.controlpanel==1.0rc1 plone.app.customerize==1.0rc1 plone.app.form==1.0rc1 plone.app.i18n==1.0rc1 plone.app.iterate==1.0rc1 plone.app.kss==1.2-rc1.1 plone.app.layout==1.0rc1 plone.app.linkintegrity==1.0rc1.1 plone.app.openid==1.0rc1 plone.app.portlets==1.0rc1 plone.app.redirector==1.0rc1 plone.app.viewletmanager==1.0rc1 plone.app.vocabularies==1.0rc1 plone.app.workflow==1.0rc1 plone.contentrules==1.0rc1 plone.fieldsets==1.0rc1 plone.i18n==1.0rc1 plone.intelligenttext==1.0rc1 plone.locking==1.0rc1 plone.memoize==1.0rc1 plone.openid==1.0rc1 plone.portlets==1.0rc1 plone.session==1.0rc1 plone.theme==1.0rc1 wicked==1.1.3 five.customerize==0.1.3 five.localsitemanager==0.2 eggs-directory = /Users/optilude/.buildout/eggs executable = /opt/local/Library/Frameworks/Python.framework/Versions/2.4/bin/python find-links = http://dist.plone.org location = /Users/optilude/tmp/eggs/zopeskel/rc1/parts/plone nested-packages = CMF-2.1.0-beta2.tar.gz prefix = /Users/optilude/tmp/eggs/zopeskel/rc1/parts/plone products = /Users/optilude/tmp/eggs/zopeskel/rc1/parts/plone python-url = http://www.python.org/ftp/python/2.4.4/Python-2.4.4.tgz recipe = plone.recipe.plone urls = http://www.zope.org/Products/CMF/CMF-2.1.0-beta2/CMF-2.1.0-beta2.tar.gz http://plone.org/products/atcontenttypes/releases/1.2/atcontenttypes-1-2-0-… http://plone.org/products/atreferencebrowserwidget/releases/2.0/ATReference… http://plone.org/products/cmfdynamicviewfti/releases/3.0/CMFDynamicViewFTI-… http://plone.org/products/cmfformcontroller/releases/2.1/CMFFormController-… http://plone.org/products/cmfplacefulworkflow/releases/1.2.0-rc1/cmfplacefu… http://plone.googlecode.com/files/PloneBase-3.0-rc1.tar.gz http://plone.org/products/cmfquickinstallertool/releases/2.0.3/CMFQuickInst… http://plone.org/products/cmfdifftool/releases/0.3.4/cmfdifftool-0-3-4.tgz http://plone.org/products/cmftestcase/releases/0.9.6/CMFTestCase-0.9.6.tar.… http://plone.org/products/extendedpathindex/releases/2.4/ExtendedPathIndex-… http://plone.org/products/external-editor/releases/0.9.3/ExternalEditor-0.9… http://plone.org/products/groupuserfolder/releases/3.54.4/GroupUserFolder-3… http://plone.org/products/kupu/releases/1.4/kupu-1-4rc1.tgz http://plone.org/products/pts/releases/1.4.4/PlacelessTranslationService-1.… http://plone.org/products/plonetestcase/releases/0.9.6/PloneTestCase-0.9.6.… http://plone.org/products/plonetranslations/releases/3.0.3/PloneTranslation… http://plone.org/products/plonelanguagetool/releases/2.0/PloneLanguageTool-… http://plone.org/products/securemailhost/releases/1.1/SecureMailHost-1.1.ta… http://plone.org/products/resourceregistries/releases/1.4.0/resourceregistr… http://plone.org/products/statusmessages/releases/3.0/statusmessages-3.0rc1… http://plone.org/products/plonepas/releases/3.0/plonepas-3-0rc1-tar.gz http://www.zope.org/Products/PluggableAuthService/PluggableAuthService-1.5/… http://plone.org/products/passwordresettool/releases/1.0/PasswordResetTool-… http://www.zope.org/Products/PluginRegistry/PluginRegistry-1.1.2/PluginRegi… http://antiloop.plone.org/download/ZopeVersionControl-0.3.4.tar.gz http://plone.org/products/cmfeditions/releases/1.1/cmfeditions-1-1-rc1.tgz http://plone.org/products/nuplone/releases/0.8/NuPlone-0.8.tgz http://www.dieter.handshake.de/pyprojects/zope/AdvancedQuery.tgz http://plone.org/products/archetypes/releases/1.5/Archetypes-1.5.0-rc2.tar.… version-suffix-packages = PluggableAuthService-1.5.tar.gz PluginRegistry-1.1.2.tar.gz zope2-url = http://www.zope.org/Products/Zope/2.10.4/Zope-2.10.4-final.tgz Installing plone. Installing 'archetypes.kss==1.2-rc1.1', 'kss.core==1.2-rc1.1', 'plone.app.content==1.0rc1', 'plone.app.contentmenu==1.0rc1', 'plone.app.contentrules==1.0rc1', 'plone.app.controlpanel==1.0rc1', 'plone.app.customerize==1.0rc1', 'plone.app.form==1.0rc1', 'plone.app.i18n==1.0rc1', 'plone.app.iterate==1.0rc1', 'plone.app.kss==1.2-rc1.1', 'plone.app.layout==1.0rc1', 'plone.app.linkintegrity==1.0rc1.1', 'plone.app.openid==1.0rc1', 'plone.app.portlets==1.0rc1', 'plone.app.redirector==1.0rc1', 'plone.app.viewletmanager==1.0rc1', 'plone.app.vocabularies==1.0rc1', 'plone.app.workflow==1.0rc1', 'plone.contentrules==1.0rc1', 'plone.fieldsets==1.0rc1', 'plone.i18n==1.0rc1', 'plone.intelligenttext==1.0rc1', 'plone.locking==1.0rc1', 'plone.memoize==1.0rc1', 'plone.openid==1.0rc1', 'plone.portlets==1.0rc1', 'plone.session==1.0rc1', 'plone.theme==1.0rc1', 'wicked==1.1.3', 'five.customerize==0.1.3', 'five.localsitemanager==0.2'. We have the distribution that satisfies 'archetypes.kss==1.2-rc1.1'. We have the distribution that satisfies 'kss.core==1.2-rc1.1'. We have the distribution that satisfies 'plone.app.content==1.0rc1'. We have the distribution that satisfies 'plone.app.contentmenu==1.0rc1'. We have the distribution that satisfies 'plone.app.contentrules==1.0rc1'. We have the distribution that satisfies 'plone.app.controlpanel==1.0rc1'. We have the distribution that satisfies 'plone.app.customerize==1.0rc1'. We have the distribution that satisfies 'plone.app.form==1.0rc1'. We have the distribution that satisfies 'plone.app.i18n==1.0rc1'. We have the distribution that satisfies 'plone.app.iterate==1.0rc1'. We have the distribution that satisfies 'plone.app.kss==1.2-rc1.1'. We have the distribution that satisfies 'plone.app.layout==1.0rc1'. We have the distribution that satisfies 'plone.app.linkintegrity==1.0rc1.1'. We have the distribution that satisfies 'plone.app.openid==1.0rc1'. We have the distribution that satisfies 'plone.app.portlets==1.0rc1'. We have the distribution that satisfies 'plone.app.redirector==1.0rc1'. We have the distribution that satisfies 'plone.app.viewletmanager==1.0rc1'. We have the distribution that satisfies 'plone.app.vocabularies==1.0rc1'. We have the distribution that satisfies 'plone.app.workflow==1.0rc1'. We have the distribution that satisfies 'plone.contentrules==1.0rc1'. We have the distribution that satisfies 'plone.fieldsets==1.0rc1'. We have the distribution that satisfies 'plone.i18n==1.0rc1'. We have the distribution that satisfies 'plone.intelligenttext==1.0rc1'. We have the distribution that satisfies 'plone.locking==1.0rc1'. We have the distribution that satisfies 'plone.memoize==1.0rc1'. We have the distribution that satisfies 'plone.openid==1.0rc1'. We have the distribution that satisfies 'plone.portlets==1.0rc1'. We have the distribution that satisfies 'plone.session==1.0rc1'. We have the distribution that satisfies 'plone.theme==1.0rc1'. We have the distribution that satisfies 'wicked==1.1.3'. We have the distribution that satisfies 'five.customerize==0.1.3'. We have the distribution that satisfies 'five.localsitemanager==0.2'. Getting required 'setuptools' required by five.customerize 0.1.3. required by five.localsitemanager 0.2. required by plone.app.content 1.0rc1. required by plone.app.contentmenu 1.0rc1. required by plone.app.contentrules 1.0rc1. required by plone.app.controlpanel 1.0rc1. required by plone.app.customerize 1.0rc1. required by plone.app.form 1.0rc1. required by plone.app.i18n 1.0rc1. required by plone.app.iterate 1.0rc1. required by plone.app.layout 1.0rc1. required by plone.app.openid 1.0rc1. required by plone.app.portlets 1.0rc1. required by plone.app.redirector 1.0rc1. required by plone.app.viewletmanager 1.0rc1. required by plone.app.vocabularies 1.0rc1. required by plone.app.workflow 1.0rc1. required by plone.contentrules 1.0rc1. required by plone.fieldsets 1.0rc1. required by plone.i18n 1.0rc1. required by plone.intelligenttext 1.0rc1. required by plone.locking 1.0rc1. required by plone.memoize 1.0rc1. required by plone.openid 1.0rc1. required by plone.portlets 1.0rc1. required by plone.session 1.0rc1. required by plone.theme 1.0rc1. required by plone.app.linkintegrity 1.0rc1.1. required by wicked 1.1.3. required by archetypes.kss 1.2-rc1.1. required by kss.core 1.2-rc1.1. required by plone.app.kss 1.2-rc1.1. Download error: (61, 'Connection refused') -- Some packages may not be found! We have the best distribution that satisfies 'setuptools'. Picked: setuptools = 0.6c6 Getting required 'python-openid>=2.0.0,<2.0.999' required by plone.openid 1.0rc1. We have the best distribution that satisfies 'python-openid>=2.0.0,<2.0.999'. Picked: python-openid = 2.0.1 While: Installing plone. An internal error occured due to a bug in either zc.buildout or in a recipe being used: URLError: <urlopen error (61, 'Connection refused')> -- Acquisition is a jealous mistress

1 0

Cygwin build of PIL 1.1.6 hangs
by Steve Holden 14 Jul '07

14 Jul '07

Has anyone noticed or reported Cygwin problems? The ordinarily well-behaved PIL install hangs on Cygwin. I put debug prints inside spawn.py and it appears that the os.waitpid(pid, 0) inside spawn_posix is failing to return when the gcc task completes. Nothing on Google about this that I can find, and no response from either the PIL or Cygwin lists. This seems a pretty fundamental breakage to not get noticed. What have I done wrong? This is using Python 2.5.2 (same thing happens with 2.5.1) on Cygwin 1.5.24, using gcc 3.4.4-3. The task manager shows 100% CPU (with kernel usage hovering about 35%) and a python.exe process gobbling CPU like there's no tomorrow. If I CTRL/C the build I get an "interrupted" diagnostic but the python.exe (presumably the child) continues to gobble CPU until killed from the task manager. I haven't yet started debugging the child process, as I am hoping someone knows of a fix. regards Steve -- Steve Holden +1 571 484 6266 +1 800 494 3119 Holden Web LLC/Ltd http://www.holdenweb.com Skype: holdenweb http://del.icio.us/steve.holden --------------- Asciimercial ------------------ Get on the web: Blog, lens and tag the Internet Many services currently offer free registration ----------- Thank You for Reading -------------

1 0

In using bdist_rpm, how do I get documentation files to go where they belong?
by Stanley A. Klein 13 Jul '07

13 Jul '07

Now that I understand how to prepare the setup.cfg for Fedora, I have been able to generate some rpms for Python packages using bdist_rpm. However, using only find_packages() causes only the executable part to be packaged. I have made various attempts to get the documentation packaged without success. 1. The first issue is that I get a peculiar error that may be an incorrect setup.py/setup.cfg or may be a bug. The result of the attempt is an error in copying a file called "d" that I didn't declare and doesn't exist. I did declare a directory called "docs". 2. The second issue is that Fedora wants to put documentation files in /usr/share/doc/package_name_and_version and I can't figure out how to make that happen. This placement of documentation is specified under the Unix Filesystem Hierarchy Standard referenced under the Linux Standards Base. The same standard specifies configuration files going under /etc, and the same issue applies if there are any such files. Below is an example from an attempt to package MojoView (from the Python Cheeseshop) with a modified setup.py. I would appreciate any help. Thanks. Stan Klein ------------------------- MojoView packaging attempt ----------------- My setup.py is: from setuptools import setup, find_packages setup(name="MojoView", version="1.0", description="Simple framwork for building PyGTK database applications", author="Jamey Cribbs", author_email="jcribbs(a)twmi.rr.com", url="http://www.netpromi.com/mojoview.html", packages = find_packages(), data_files = [("docs", "docs/*"), ("examples", "examples/*"), ("gtk", "gtk/*"), ("readme.txt", "readme.txt")] ) The setup.cfg is: #setup.cfg to get proper rpms [install] optimize = 1 [bdist_rpm] doc_files = readme.txt docs/ gtk/ examples/ The output from the attempt is: [stan@localhost MojoView-1.0]$ python setup.py bdist_rpm running bdist_rpm running egg_info writing MojoView.egg-info/PKG-INFO writing top-level names to MojoView.egg-info/top_level.txt writing dependency_links to MojoView.egg-info/dependency_links.txt reading manifest file 'MojoView.egg-info/SOURCES.txt' writing manifest file 'MojoView.egg-info/SOURCES.txt' writing 'build/bdist.linux-i686/rpm/SPECS/MojoView.spec' running sdist warning: sdist: standard file not found: should have one of README, README.txt creating MojoView-1.0 creating MojoView-1.0/MojoView.egg-info creating MojoView-1.0/mojoview making hard links in MojoView-1.0... hard linking setup.cfg -> MojoView-1.0 hard linking setup.py -> MojoView-1.0 hard linking MojoView.egg-info/PKG-INFO -> MojoView-1.0/MojoView.egg-info hard linking MojoView.egg-info/SOURCES.txt -> MojoView-1.0/MojoView.egg-info hard linking MojoView.egg-info/dependency_links.txt -> MojoView-1.0/MojoView.egg-info hard linking MojoView.egg-info/top_level.txt -> MojoView-1.0/MojoView.egg-info hard linking mojoview/__init__.py -> MojoView-1.0/mojoview hard linking mojoview/aboutwin.py -> MojoView-1.0/mojoview hard linking mojoview/browse.py -> MojoView-1.0/mojoview hard linking mojoview/busycursor.py -> MojoView-1.0/mojoview hard linking mojoview/clist.py -> MojoView-1.0/mojoview hard linking mojoview/editdaterange.py -> MojoView-1.0/mojoview hard linking mojoview/editrec.py -> MojoView-1.0/mojoview hard linking mojoview/editwin.py -> MojoView-1.0/mojoview hard linking mojoview/errorwin.py -> MojoView-1.0/mojoview hard linking mojoview/guierror.py -> MojoView-1.0/mojoview hard linking mojoview/mainmenu.py -> MojoView-1.0/mojoview hard linking mojoview/mv.py -> MojoView-1.0/mojoview hard linking mojoview/notebookwin.py -> MojoView-1.0/mojoview hard linking mojoview/toolbar.py -> MojoView-1.0/mojoview copying setup.cfg -> MojoView-1.0 Writing MojoView-1.0/setup.cfg tar -cf dist/MojoView-1.0.tar MojoView-1.0 gzip -f9 dist/MojoView-1.0.tar removing 'MojoView-1.0' (and everything under it) copying dist/MojoView-1.0.tar.gz -> build/bdist.linux-i686/rpm/SOURCES building RPMs rpmbuild -ba --define _topdir /home/stan/exper/mojoview/MojoView-1.0/build/bdist.linux-i686/rpm --clean build/bdist.linux-i686/rpm/SPECS/MojoView.spec Executing(%prep): /bin/sh -e /var/tmp/rpm-tmp.61946 + umask 022 + cd /home/stan/exper/mojoview/MojoView-1.0/build/bdist.linux-i686/rpm/BUILD + LANG=C + export LANG + unset DISPLAY + cd /home/stan/exper/mojoview/MojoView-1.0/build/bdist.linux-i686/rpm/BUILD + rm -rf MojoView-1.0 + /bin/gzip -dc /home/stan/exper/mojoview/MojoView-1.0/build/bdist.linux-i686/rpm/SOURCES/MojoView-1.0.tar.gz + tar -xvvf - drwxrwxr-x stan/stan 0 2007-07-13 14:37 MojoView-1.0/ drwxrwxr-x stan/stan 0 2007-07-13 14:37 MojoView-1.0/MojoView.egg-info/ -rw-rw-r-- stan/stan 9 2007-07-13 14:37 MojoView-1.0/MojoView.egg-info/top_level.txt -rw-rw-r-- stan/stan 437 2007-07-13 14:37 MojoView-1.0/MojoView.egg-info/SOURCES.txt -rw-rw-r-- stan/stan 276 2007-07-13 14:37 MojoView-1.0/MojoView.egg-info/PKG-INFO -rw-rw-r-- stan/stan 1 2007-07-13 14:37 MojoView-1.0/MojoView.egg-info/dependency_links.txt -rw-rw-rw- stan/stan 519 2007-07-12 17:00 MojoView-1.0/setup.py drwxrwxr-x stan/stan 0 2007-07-13 14:37 MojoView-1.0/mojoview/ -rw-rw-rw- stan/stan 2034 2003-08-21 14:17 MojoView-1.0/mojoview/editdaterange.py -rw-rw-rw- stan/stan 23415 2003-09-02 16:51 MojoView-1.0/mojoview/browse.py -rw-rw-rw- stan/stan 2212 2003-09-02 16:38 MojoView-1.0/mojoview/notebookwin.py -rw-rw-rw- stan/stan 1477 2003-08-08 15:41 MojoView-1.0/mojoview/editwin.py-rw-rw-rw- stan/stan 593 2003-08-08 15:41 MojoView-1.0/mojoview/busycursor.py -rw-rw-rw- stan/stan 1829 2003-09-02 16:29 MojoView-1.0/mojoview/toolbar.py-rw-rw-rw- stan/stan 16470 2003-09-02 16:50 MojoView-1.0/mojoview/clist.py -rw-rw-rw- stan/stan 373 2003-08-08 15:42 MojoView-1.0/mojoview/errorwin.py -rw-rw-rw- stan/stan 26 2003-08-08 15:39 MojoView-1.0/mojoview/__init__.py -rw-rw-rw- stan/stan 520 2003-08-12 08:56 MojoView-1.0/mojoview/aboutwin.py -rw-rw-rw- stan/stan 3675 2003-09-02 16:39 MojoView-1.0/mojoview/mainmenu.py -rw-rw-rw- stan/stan 317 2003-08-28 14:31 MojoView-1.0/mojoview/mv.py -rw-rw-rw- stan/stan 1983 2003-09-03 13:18 MojoView-1.0/mojoview/guierror.py -rw-rw-rw- stan/stan 2849 2003-09-02 16:27 MojoView-1.0/mojoview/editrec.py-rw-rw-r-- stan/stan 143 2007-07-13 14:37 MojoView-1.0/setup.cfg -rw-rw-r-- stan/stan 276 2007-07-13 14:37 MojoView-1.0/PKG-INFO + STATUS=0 + '[' 0 -ne 0 ']' + cd MojoView-1.0 ++ /usr/bin/id -u + '[' 500 = 0 ']' ++ /usr/bin/id -u + '[' 500 = 0 ']' + /bin/chmod -Rf a+rX,u+w,g-w,o-w . + exit 0 Executing(%build): /bin/sh -e /var/tmp/rpm-tmp.61946 + umask 022 + cd /home/stan/exper/mojoview/MojoView-1.0/build/bdist.linux-i686/rpm/BUILD + cd MojoView-1.0 + LANG=C + export LANG + unset DISPLAY + python setup.py build running build running build_py creating build creating build/lib creating build/lib/mojoview copying mojoview/editdaterange.py -> build/lib/mojoview copying mojoview/browse.py -> build/lib/mojoview copying mojoview/notebookwin.py -> build/lib/mojoview copying mojoview/editwin.py -> build/lib/mojoview copying mojoview/busycursor.py -> build/lib/mojoview copying mojoview/toolbar.py -> build/lib/mojoview copying mojoview/clist.py -> build/lib/mojoview copying mojoview/errorwin.py -> build/lib/mojoview copying mojoview/__init__.py -> build/lib/mojoview copying mojoview/aboutwin.py -> build/lib/mojoview copying mojoview/mainmenu.py -> build/lib/mojoview copying mojoview/mv.py -> build/lib/mojoview copying mojoview/guierror.py -> build/lib/mojoview copying mojoview/editrec.py -> build/lib/mojoview + exit 0 Executing(%install): /bin/sh -e /var/tmp/rpm-tmp.75576 + umask 022 + cd /home/stan/exper/mojoview/MojoView-1.0/build/bdist.linux-i686/rpm/BUILD + cd MojoView-1.0 + LANG=C + export LANG + unset DISPLAY + python setup.py install --single-version-externally-managed --root=/var/tmp/MojoView-1.0-1-buildroot --record=INSTALLED_FILES running install running build running build_py running install_lib writing byte-compilation script '/tmp/tmp0s5onf.py' /usr/bin/python -O /tmp/tmp0s5onf.py removing /tmp/tmp0s5onf.py running install_data error: can't copy 'd': doesn't exist or not a regular file error: Bad exit status from /var/tmp/rpm-tmp.75576 (%install) RPM build errors: Bad exit status from /var/tmp/rpm-tmp.75576 (%install) error: command 'rpmbuild' failed with exit status 1

1 0

Case sensitivity of package names
by Jim Fulton 12 Jul '07

12 Jul '07

On Jul 12, 2007, at 2:43 PM, Phillip J. Eby wrote: > At 02:15 PM 7/12/2007 -0400, Jim Fulton wrote: >> I want to make sure I understand this. I would hope that searching >> would be case insensitive and otherwise flexible wrt names. > > PyPI's searching is indeed case insensitive, and is a substring/ > keyword search as well. > > >> Is there >> any reason we can't expect URLs and requirement specifications to be >> precisely spelled? That is, if someone names their package "sPaM", I >> see no reason why PyPI needs to support anything other than >> http:// www.python.org/pypi/sPaM as the one URL of the package. >> Someone >> should be able to use the search UI to search for "spam" and see a >> result that includes "sPaM". From then on, they should be able to >> type the name "sPaM". Or am I missing something? > > You're missing that the subject is about similarity of names. > A typo of say, 'SPam' shouldn't return me some package *other* > than the one I'm looking for. I No, I understand that part. I understand the desire to avoid conflicts that cause problems down the road. I would prefer to "disallow" this by rejecting new package names that are too similar to already-registered packages. > t'd be nice if the resulting page said something besides "Not > Found", too... like "there's no SPam, but here are a bunch of > packages whose name contains 'spam'". I think this would be fine in a human interface. > If it did that, setuptools would be able to find the right page > without hitting the main index, too. But redirection, as proposed > by Martin, also accomplishes the same thing. I really don't like this for setuptools. My preference is that setuptools should be required to ask for a package with precise spelling. > And again, all this helps human direct users of the index, too. I think it encourages humans to do bad things. Is someone misspells ZODB3 as zodb3 and is able to install it with easy_install, then they'll be tempted to use the name "zodb3" in their requirements specifications. That is a bad thing IMO. We're talking about technical users and I think it is reasonable to expect them to be precise in their specifications. I could live with case-insensitive package names if we (for some definition of we, possibly being Guido) decided we want them, but I'd prefer they be case sensitive. I'd still be in favor of avoiding confusing duplicates. If we stick with case-sentitive package names, then I'd prefer that the interaction of setuptools with the index be case sensitive. I wouldn't object to setuptools giving people help. So, for example, if I type "zodb3", I wouldn't object to setuptools letting the user know that maybe they should use ZODB3. Jim -- Jim Fulton mailto:jim@zope.com Python Powered! CTO (540) 361-1714 http://www.python.org Zope Corporation http://www.zope.com http://www.zope.org

3 4

Re: [Distutils] [Catalog-sig] start on static generation, and caching - apache config.
by Jim Fulton 11 Jul '07

11 Jul '07

On Jul 11, 2007, at 6:11 PM, Richard Jones wrote: > On Thu, 12 Jul 2007, Martin v. Löwis wrote: >>> The questions for us is, how much effort we are willing to make to >>> prevent people from shooting themselves in the foot. I can >>> understand >>> why Phillip would like the package index to prevent people from >>> choosing >>> problematic package names. >> >> That's not my understanding - the issue isn't with "problematic >> package >> names", but with conflicting package names. IOW, any single name is >> fine - it's a pair of names that would cause a problem (and only if >> you wanted to install both packages on the same system). > > A big issue that's not been raised is that *distutils* have no > package name > rules, but it's being proposed that PyPI does - thus a package > author will > potentially get an error when uploading their package, and also the > name that > appears in the index may be quite different to the name of their > package. Maybe distutils should have more package name rules than it does now. We (the Community) should be free to change things based on experience. We now have a lot more experience with this stuff than we had a few years ago. Maybe we should consider a reset. Jim -- Jim Fulton mailto:jim@zope.com Python Powered! CTO (540) 361-1714 http://www.python.org Zope Corporation http://www.zope.com http://www.zope.org

1 0