Distutils-SIG

Download

distutils-sig@python.org

November 2011

22 participants
32 discussions

Odd limitation in packaging/distutils2
by Paul Moore 04 Nov '11

04 Nov '11

This seems odd... PS D:\Data\PyPI> D:\Data\cpython\PCbuild\python -m packaging.run install nose installing third-party projects from an uninstalled Python is not supported And yet after downloading the nose source... PS D:\Data\PyPI> bsdtar xzf D:\Downloads\Python\nose-1.1.2.tar.gz PS D:\Data\PyPI> cd .\nose-1.1.2 PS D:\Data\PyPI\nose-1.1.2> D:\Data\cpython\PCbuild\python -m packaging.run install Installing from source directory: 'D:\\Data\\PyPI\\nose-1.1.2' Downloading http://pypi.python.org/packages/source/d/distribute/distribute-0.6.14.tar.gz Extracting in c:\users\gustav\appdata\local\temp\tmpecso_w Now working in c:\users\gustav\appdata\local\temp\tmpecso_w\distribute-0.6.14 Building a Distribute egg in D:\Data\PyPI\nose-1.1.2 warning: no files found matching 'Makefile' under directory 'docs' warning: no files found matching 'indexsidebar.html' under directory 'docs' creating build creating build\src ... etc (The build actually failed, but for reasons unrelated to the fact that it's an uninstalled Python, as far as I can see). Why not allow installing direct from PyPI? Paul.

4 10

Some distutils2/packaging questions
by Paul Moore 03 Nov '11

03 Nov '11

Hi, I hope this is the right list for usage questions on distutils2/packaging. If not, please point me at the correct list. I'm looking at how I'd translate existing setup.py configurations into the new setup.cfg format. One situation I'm not sure how to deal with is the package_data argument to setup(). This allows me to specify data files which are to be installed as part of a package. How would I do this in distutils2/packaging? The resources entry seems like the intended place, but I don't see how I can specify the destination without making too many assumptions about precisely where the package will get installed. Any suggestions? Thanks, Paul.

2 1