Mailman 3 July 2009 - Distutils-SIG

introspecting package data
by Chris Withers 07 Jul '09

07 Jul '09

Hi All, I hope this is a silly question and I'm just missing something, but how do I introspect information from setup.py when I'm not using setuptools? (ie: pkg_resources for those who refuse to drink the setuptools koolaid?) cheers, Chris

6 13

[issue79] SVN Entries parsing should use local svn command for implementation
by Jason R. Coombs 05 Jul '09

05 Jul '09

New submission from Jason R. Coombs <jaraco(a)jaraco.com>: Per issue #64, there is a need for a more future-resistant SVN entries parsing mechanism for setuptools. The existing implementation is brittle and depends on file formats which are internal to the SVN implementation. @dw has proposed setuptools use 'svn info --xml' to retrieve entry information. I propose a patch must support the following: 1) Support fallback to native pure-python parsing if command is not found or cannot be executed. 2) Use subprocess (requires Python 2.4) for broad platform support (including Jython). 3) The current implementation appears to gather more detail from the entries file than is exposed by 'svn info --xml'. Ensure that the command-based implementation provides the same logical result. 4) The implementation should have a well-defined and configurable means to locate the SVN client. If there is no 'svn' command in the search path, there should be an alternative means for setuptools to locate the command (such as one or more of: a registry entry, environment variable, package manager callback, etc.). Some features that may also be considered. 1) Support linking to the TortoiseSVN DLL for Windows users (use ctypes to avoid compile-time dependencies). 2) Support shelling to a Java VM to support users of Subclipse. Comments and suggestions are appreciated. After there is a consensus, I'm willing to draft an implementation. ---------- messages: 320 nosy: dw, jaraco priority: feature status: unread title: SVN Entries parsing should use local svn command for implementation _______________________________________________ Setuptools tracker <setuptools(a)bugs.python.org> <http://bugs.python.org/setuptools/issue79> _______________________________________________

1 0

easy_install: fix for new Sourceforge download pages
by Hartmut Goebel 04 Jul '09

04 Jul '09

Hi, since Sourceforge did change their download pages, easy_install is no longer able to fetch files there-from. Shame in Sourceforge! For one of my tools I fixed this using the following code: ......8<--------------- def _download_html(self, url, headers, filename): if url.startswith('http://sourceforge.net/projects/'): if self._download_from_sf(url, filename): return return PackageIndex._download_html(self, url, headers, filename) def _download_from_sf(self, url, filename): page = open(filename).read() basename = os.path.basename(filename) for match in HREF.finditer(page): link = urlparse.urljoin(url, htmldecode(match.group(1))) if link.startswith('http://downloads.sourceforge.net/sourceforge/'): path = urlparse.urlparse(url)[2] base = urllib2.unquote(path.split('/')[-1]) if base == basename: os.unlink(filename) self._download_to(link, filename) return True return False ......8<--------------- -- Schönen Gruß - Regards Hartmut Goebel Dipl.-Informatiker (univ.), CISSP, CSSLP Goebel Consult Spezialist für IT-Sicherheit in komplexen Umgebungen http://www.goebel-consult.de

1 0

PEP 376: uninstall before upgrading an install?
by Kevin Teague 03 Jul '09

03 Jul '09

Currently, if you install a distribution via distutils (python setup.py install), then later get a new version of that distribution and upgrade your install, if the files to be installed change from one version to the next the old, unused files get left in-place (generally this is quite rare, since re-naming packages/modules means developers need to change imports, etc. which is a hassle, but it is possible). e.g. If "Spam-1.0" provides "ham.py, eggs.py" and "Spam-2.0" provides "eggs.py, toast.py", then upgrading would leave an extra ham.py file kicking around in site-packages, or vice-versa with toast.py if downgrading. At least, I'm being lazy and not actually testing this behaviour, but I think that this is the current status with Distutils installs? With a record of all installed files for a given version of a distribution though, it would be possible to detect that a distribution was already installed and that an upgrade/downgrade/ sidegrade is being performed, and if an uninstall was first done on the old version before the new version was installed, this would prevent any stray files from appearing in site-packages. Has this already been considered? And if not, is there any reason why an uninstall shouldn't happen before a distribution is upgraded in- place?

1 0

Standalone version of Distutils - nighlty builds
by Tarek Ziadé 03 Jul '09

03 Jul '09

Hello I have done what's needed to be able install the current Distutils trunk version as a standalone package in a Python installation. I am not planning to publish it at this time but rather when 2.7/3.2 are about to be released. If you are interested in working with the lasted Distutils version, please install it and let me know how it goes ;) I have a cron that build the distribution every night: http://nightly.ziade.org/ Cheers Tarek -- Tarek Ziadé | http://ziade.org

1 0

setuptools v. subversion 1.6
by Chris Withers 01 Jul '09

01 Jul '09

Hi All, I see setuptools still doesn't like subversion 1.6 working copies. Is that likely to change this century? :-( Worse still, I tried using: http://svn.collab.net/repos/svn/trunk/tools/client-side/change-svn-wc-forma… ..to downgrade the working copy with: python ../change-svn_wc_format.py --verbose . 1.4 However, setuptools still whines: $ bin/buildout setup setup.py sdist Running setup script 'setup.py'. running sdist running egg_info writing requirements to mypackage.egg-info/requires.txt writing mypackage.egg-info/PKG-INFO writing top-level names to mypackage.egg-info/top_level.txt writing dependency_links to mypackage.egg-info/dependency_links.txt unrecognized .svn/entries format in ...uselessly: it does't actually tell me where the entries file is that it has problems with. What am I doing wrong? Is this a bug in change-svn-wc-format.py? How can I work around this? cheers, Chris

2 6