Mailman 3 September 2008 - Distutils-SIG

access to setup() arguments
by chris 04 Sep '08

04 Sep '08

If I have something like this in a setup.py setup( name = 'foo', ... ) is there a way to access name and get back foo? Thanks, Chris

1 2

Re: [Distutils] [issue35] mercurial support
by Phillip J. Eby 04 Sep '08

04 Sep '08

At 05:40 PM 9/4/2008 +0200, Sebastien Douche wrote: >On Mon, Aug 25, 2008 at 20:00, Paul Egan <setuptools(a)bugs.python.org> wrote: > > > > New submission from Paul Egan <paulegan(a)mail.com>: > > > > Patch to add mercurial support to setuptools: > > * Extends setuptools.file_findersAdds with hg repository support > > * Adds tag-hg-revision & filter-hgignore-files options to the > egg-info command > >Hi Paul, >Thanks for your patch. After some tests, like works great. Here, we >think seriously to migrate on HG (as many OSS projects). > >Philipp, are you open to accepting HG/Bzr/git in Setuptools ? No, but I'm open to patches that modify the core to accept plugins for functions that are currently hard-coded to CVS or SVN. File finding is already possible via plugins, and you can easily find such plugins by browsing the "setuptools plugins" category on PyPI. Revision tag information is the main thing not pluggable at the moment; patches welcome. (See also my notes on the above ticket for more info)

1 0

[issue35] mercurial support
by Paul Egan 04 Sep '08

04 Sep '08

New submission from Paul Egan <paulegan(a)mail.com>: Patch to add mercurial support to setuptools: * Extends setuptools.file_findersAdds with hg repository support * Adds tag-hg-revision & filter-hgignore-files options to the egg-info command ---------- files: mercurial.diff messages: 127 nosy: paulegan priority: feature status: unread title: mercurial support Added file: http://bugs.python.org/setuptools/file16/mercurial.diff _______________________________________________ Setuptools tracker <setuptools(a)bugs.python.org> <http://bugs.python.org/setuptools/issue35> _______________________________________________

2 1

[issue41] need support for post-install scripts
by htgoebel 04 Sep '08

04 Sep '08

New submission from htgoebel <h.goebel(a)goebel-consult.de>: easy_install needs some mechanism for running post-installation scripts. This is required by eg. pywin32 (see issue18) and py2exe. If uninstall is implemented (see issue21), pre-/post-uninstall scripts need to be supported, too. I suggest adding new entry-points: - easy-install.post-install - easy-install.pre-uninstall - easy-install.post-uninstall (pre-install does not make sense, since typically the package can not be used prior to installation :-) ---------- messages: 154 nosy: htgoebel priority: feature status: unread title: need support for post-install scripts _______________________________________________ Setuptools tracker <setuptools(a)bugs.python.org> <http://bugs.python.org/setuptools/issue41> _______________________________________________

1 0

development-egg in current directory
by Hartmut Goebel 03 Sep '08

03 Sep '08

Hi, I'm currently installing development eggs into the current directory (the checkout directory) like this: PYTHONPATH=.:$PYTHONPATH \ python setup.py develop --install-dir . --script-dir . Since this has problems when re-running (see issue40), I wonder whether this is the correct use of the 'develop' egg. Any hints? -- Schönen Gruß - Regards Hartmut Goebel Dipl.-Informatiker (univ.), CISSP Goebel Consult Spezialist für IT-Sicherheit in komplexen Umgebungen http://www.goebel-consult.de

3 6

[issue40] development egg: recusion to deep when re-running setup.py develop
by htgoebel 03 Sep '08

03 Sep '08

New submission from htgoebel <h.goebel(a)goebel-consult.de>: I'm installing a development egg like this:: PYTHONPATH=.:$PYTHONPATH python setup_.py develop --install-dir . --script-dir . Now when re-running the command above, it will fail:: File "/usr/lib/python2.5/site-packages/setuptools-0.6c8-py2.5.egg/pkg_resources.py", line 1072, in safe_name File "/usr/lib/python2.5/re.py", line 150, in sub return _compile(pattern, 0).sub(repl, string, count) File "/usr/lib/python2.5/re.py", line 230, in _compile p = _cache.get(cachekey) RuntimeError: maximum recursion depth exceeded in cmp This seams to be a problem with *.egg-link. If I add these lines to teh fron tom my setup.py, re-running is fine: import glob, os for fn in glob.glob('*.egg-link'): os.remove(fn) ---------- messages: 153 nosy: htgoebel priority: bug status: unread title: development egg: recusion to deep when re-running setup.py develop _______________________________________________ Setuptools tracker <setuptools(a)bugs.python.org> <http://bugs.python.org/setuptools/issue40> _______________________________________________

1 0

Where to report bugs for setuptools?
by Hartmut Goebel 03 Sep '08

03 Sep '08

Hi, I know I asked this some weeks ago, I did forget :-) Where to report bugs for setuptools? The setuptools website does not give any hint. -- Schönen Gruß - Regards Hartmut Goebel Dipl.-Informatiker (univ.), CISSP Goebel Consult Spezialist für IT-Sicherheit in komplexen Umgebungen http://www.goebel-consult.de

1 1

[issue39] website: does not tell where to report bugs
by htgoebel 03 Sep '08

03 Sep '08

New submission from htgoebel <h.goebel(a)goebel-consult.de>: There seams to be not a single link from the http://peak.telecommunity.com/DevCenter/ wiki to the bug tracker. This makes it hard to report bugs. Please add a link to these pages: * FrontPage * setuptools * EasyInstall ---------- messages: 152 nosy: htgoebel priority: urgent status: unread title: website: does not tell where to report bugs _______________________________________________ Setuptools tracker <setuptools(a)bugs.python.org> <http://bugs.python.org/setuptools/issue39> _______________________________________________

1 0

Unicode in distutils meta-data
by Tarek Ziadé 03 Sep '08

03 Sep '08

Hello, I would like to summarize here http://bugs.python.org/issue2562. Currently, distutils does not allows the usage of Unicode for some meta-data fields that should be able to use it. These fields are: - author - maintainer - description - long_description For instance, if you use u"Barnabé" in the author field, the DistributionMetada.write_pkg_file will fail when it tries to serialize the information into a file. The problem is that the current implementation makes the assumption that all fields are ascii string. This won't be a problem in Python 3k, of course, but currently concerns the 2.x series. One possible solution would be to move these fields to Unicode for the 2.6 series. In the meantime, many people are using str type for those fields, so as Martin mentioned, a backward compatibility would be better to support either plain string either Unicode. Other fields should be left imho in ascii, since an url for instance has to be ascii. But maybe it would be better, as Martin mentioned, to use Unicode for all fields. In any case, if we do use Unicode for some fields, we will need to provide the codec to be used to serialize the data in a file. My proposal here would be to add a 'encoding' field in the metadata that defaults to 'utf8', and that would let people explicitely indicates the encoding. I have written a quick patch here of a possible implementation, so you can see the problem : http://bugs.python.org/file9967/unicode.metadata.patch Regards, Tarek -- Tarek Ziadé | Association AfPy | www.afpy.org Blog FR | http://programmation-python.org Blog EN | http://tarekziade.wordpress.com/

2 2

setup script not found when directory name is 100 characters
by Maurits van Rees 03 Sep '08

03 Sep '08

Hi, I'm sure I have read this somewhere, but my search skills are failing me. When easy installing a package this goes wrong: $ bin/easy_install ../foo.bar/dist/foo.bar-1.0.3.tar.gz Processing foo.bar-1.0.3.tar.gz error: Couldn't find a setup script in ../foo.bar/dist/foo.bar-1.0.3.tar.gz The cause is that there is a directory foo.bar-1.0.3/.../baz for which the length of this path is exactly 100 characters. When I release a version 1.1 instead, this path is reduced to 98 characters and easy_install happily installs it. Does anyone know which version of setuptools or easy_install introduced this problem or fixes it? Or a link where this is explained? Thanks, -- Maurits van Rees | http://maurits.vanrees.org/ Work | http://zestsoftware.nl/ "This is your day, don't let them take it away." [Barlow Girl]

3 5