Mailman 3 July 2008 - Distutils-SIG

[issue27] [PATCH] Fix shebang lines for Jython on POSIX
by Philip Jenvey 16 Jul '08

16 Jul '08

New submission from Philip Jenvey <pjenvey(a)underboss.org>: Jython's sys.executable is a shell script on POSIX (and .bat on Windows) and thus can't be used as a shebang line interpreter. The following patch works around this by calling sys.executable via /usr/bin/env in shebang lines on platforms where sys.platform.startswith('java') and sys.executable's MAGIC is '#!'. Jython on Windows is a separate issue -- Jython probably has to ship a .exe to solve the problem there. This fix doesn't apply to Windows because sys.executable's MAGIC is not '#!' there. Marking as a higher priority because installed scripts on Jython aren't executable without this fix Original distutils-sig discussion: http://www.nabble.com/Shebang-lines-on- Jython-td16730414.html ---------- files: jython-shebang-fix_r61342.diff messages: 60 nosy: pjenvey priority: critical status: unread title: [PATCH] Fix shebang lines for Jython on POSIX Added file: http://bugs.python.org/setuptools/file10/jython-shebang-fix_r61342.diff _______________________________________________ Setuptools tracker <setuptools(a)bugs.python.org> <http://bugs.python.org/setuptools/issue27> _______________________________________________

1 0

weird setuptools error...
by Chris Withers 15 Jul '08

15 Jul '08

This is while using buildout, but the weirdness is definitely setuptools... The buildout.cfg: [buildout] parts = eggs setuptools-version = == 0.6c8 zc.buildout-version = == 1.0.6 [eggs] recipe = zc.recipe.egg eggs = BeautifulSoup The output: >bin\buildout.exe Getting distribution for 'zc.recipe.egg'. Got zc.recipe.egg 1.1.0b1. Installing eggs. Getting distribution for 'BeautifulSoup'. zip_safe flag not set; analyzing archive contents... eggs\setuptools-0.6c8-py2.5.egg\setuptools\command\bdist_egg. py:422: UnicodeWarning: Unicode equal comparison failed to convert both argument s to Unicode - interpreting them as being unequal symbols = dict.fromkeys(iter_symbols(code)) Installing BeautifulSoup 3.0.7a Caused installation of a distribution: beautifulsoup 3.0.7a with a different project name. Got beautifulsoup 3.0.7a. What's that unicode warning all about? Chris -- Simplistix - Content Management, Zope & Python Consulting - http://www.simplistix.co.uk

1 0

autotools-like AC_COMPILE_IFELSE
by Laurent Gautier 15 Jul '08

15 Jul '08

Hi, I would like to know if it is possible to emulate some features of the GNU build tools with distutils (or related python module). In particular, I have a C-written Python module and I would like to try compiling very short (few lines) C programs in order to check that third-party C libraries the python module links to has given features. I suspect that I am not the first to ask, but I could not find much information about that topic on the net. Any help/pointer would be appreciated, L.

1 0

[zc.buildout] confusion from "work on a package" section
by Chris Withers 15 Jul '08

15 Jul '08

Reading: http://pypi.python.org/pypi/zc.buildout/1.0.6#work-on-a-package ...again. Can someone walk me through like the idiot I feel right now why having "develop = ." results in src/zc/ngi/ ending up on the python path? cheers, Chris -- Simplistix - Content Management, Zope & Python Consulting - http://www.simplistix.co.uk

2 3

[zc.buildout] "Adding and removing options" section unclear
by Chris Withers 15 Jul '08

15 Jul '08

Hi All, This section of the docs at http://pypi.python.org/pypi/zc.buildout/1.0.6 doesn't seem to make much sense. extension1.cfg and extension2.cfg are set up but no examples use them as far as I can see. The demo also uses extending of configurations as well as buildout extensions before these have been introduced as concepts. I'm *guessing* that: >>> write(sample_buildout, 'base.cfg', ... """ ... [buildout] ... parts = part2 ... ... [part2] ... recipe = ... option = b1 b2 b3 b4 ... """) >>> write(sample_buildout, 'extension1.cfg', ... """ ... [buildout] ... extends = base.cfg ... ... [part2] ... option -= b1 b2 ... """) ..will result in 'option' being 'b3 b4' when extension1.cfg is used, but there's no explanation of how this works. Are option values always split on spaces or is there another set of rules for this? Where is this documented? cheers, Chris -- Simplistix - Content Management, Zope & Python Consulting - http://www.simplistix.co.uk

3 9

[setuptools] how are entry points consumed
by Chris Withers 15 Jul '08

15 Jul '08

Hi all, Been reading: http://peak.telecommunity.com/DevCenter/setuptools#dynamic-discovery-of-ser… This seems to sort of cover eggs that provide entry points but doesn't cover at all how they're consumed. So, taking the blogtool.parsers example, what python code would blogtool actually use to get hold of all the different parsers? cheers, Chris -- Simplistix - Content Management, Zope & Python Consulting - http://www.simplistix.co.uk

1 0

Re: [Distutils] Where is setuptools 0.6c9?
by Phillip J. Eby 14 Jul '08

14 Jul '08

At 12:11 PM 7/14/2008 -0500, Alan Runyan wrote: >Just ran across the NameError that was fixed in revision 60846. >Looks like setup.py was bumped to 0.6c9 in revision 60848. That's standard procedure in order to avoid revision numbers going backwards: as soon as I make an official release, I bump the version so that all subsequent builds or checkouts are a .dev version of the *next* release. >Was 0.6c9 intended to be released? It has not been, no. If it were, the version in SVN would be 0.6c10. When 0.6final is released, the SVN version will jump to 0.6.1, and so on.

2 1

Where is setuptools 0.6c9?
by Alan Runyan 14 Jul '08

14 Jul '08

Just ran across the NameError that was fixed in revision 60846. Looks like setup.py was bumped to 0.6c9 in revision 60848. Was 0.6c9 intended to be released? I heard a rumor of released software "gone missing" from pypi. Curious to the status. cheers alan

1 0

Setuptools documentation
by Florian Mayer 10 Jul '08

10 Jul '08

Hello! I have read the setuptools documentation and have tried out the parse_version comparison, and it turns out that the documentation says is just wrong. I am using version 0.6c8 of setuptools. The documentation says, quoting: "Don't use - or any other character than . as a separator, unless you really want a post-release. Remember that 2.1-rc2 means you've already released 2.1, whereas 2.1rc2 and 2.1.c2 are candidates you're putting out before 2.1". It also shows a little example for that: >>> parse_version('2.1-rc2') < parse_version('2.1') False While this sounds pretty weird(how can a rc be after the release?) but also logical if you just consider any character but "." to be post-release, which you can do, but do not have to. Still if they say this is the rule it is okay, although I would not quite agree with that, as many people use underscores or dashes as a separation. So what the real problem is, is that the documentation says things that are untrue with at least the latest version. As said before I have setuptools 0.6c8 and the behaviour is not like the documentation says in any way. Here is a little example: >>> parse_version("2.1-rc2") < parse_version("2.1") True Notice the difference? It's exactly the *opposite* of what the documentation says. I really ask you to correct this issue as it might confuse new users. The documentation I mean can be found at http://peak.telecommunity.com/DevCenter/setuptools, if it is not done by you or you cannot edit it, I apologise and will send another email to its maintainer, but as I could not find out who maintains this site, I just assumed that you, as the maintainer of setuptools are maintaining the documentation. Thanks in advance for your time reading this and correcting the documentation. Best regards, Florian Mayer

4 4

Re: [Distutils] Setuptools documentation
by Phillip J. Eby 09 Jul '08

09 Jul '08

At 08:18 PM 7/9/2008 +0200, Jeroen Ruigrok van der Werven wrote: >-On [20080709 20:06], Phillip J. Eby (pje(a)telecommunity.com) wrote: > >"lately" != "never again" > >I understand that. >And I can also understand you might not no anyone yet you feel comfortable >with sharing commit access with someone else. 2 things: 1. I don't even have time to review people's work in order to become comfortable, and 2. I don't control commit access to setuptools, anyway... it's Python's SVN, not mine.

1 0