Distutils-SIG February 2010

distutils-sig@python.org

45 participants
58 discussions

[issue103] develop command needs a way to install extra requirements
by Tres Seaver 23 Feb '10

23 Feb '10

New submission from Tres Seaver <tseaver(a)palladion.com>: When running 'python setup.py develop', it would be useful to install one (or more) of the 'extra' requirements for the package-under-development. The attached patch allows installing one at a time: I don't have the options fu to make it a repeatable option. ---------- assignedto: pje files: setuptools-develop_w_extra.patch messages: 506 nosy: pje, tseaver priority: feature status: unread title: develop command needs a way to install extra requirements Added file: http://bugs.python.org/setuptools/file67/setuptools-develop_w_extra.patch _______________________________________________ Setuptools tracker <setuptools(a)bugs.python.org> <http://bugs.python.org/setuptools/issue103> _______________________________________________

1 0

Re: [Distutils] setuptools-0.6c11.win32-py2.6.exe
by P.J. Eby 22 Feb '10

22 Feb '10

At 04:13 AM 2/21/2010 +0100, Daniel Niccoli wrote: >Hello Phillip, > >if you install the x86-64 version of python, the windows installer >"setuptools-0.6c11.win32-py2.6.exe" does not find any Python >installation. I had to export the registry key >"HKEY_LOCAL_MACHINE\SOFTWARE\Python", change it to >"HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Python" and import it >afterwards to be able to install the software. The installer should >be changed to avoid trouble for other people. This is a *Python* installer issue; Please see: http://bugs.python.org/issue6792 Until the issue in Python itself is fixed, the only things I can do are document the problem and/or stop distributing an .exe installer.

2 1

Re: [Distutils] using distribute instead of distutils
by P.J. Eby 22 Feb '10

22 Feb '10

At 05:20 PM 2/22/2010 +0100, Jean Daniel wrote: >Hello, I am writing a pure python module called wordish, which is >similar to doctest in that it test snippets of code, parsed from an >rst article and produce a report. wordish is available on Pypi in >version 1.0 and the documentation is available at >jdb.github.com/wordish. So far, I only distributed one file, >*wordish.py* and the file was used like the following:: Â Â Â >python -m wordish my_article.rst I think I will turn to 'distribute' >for the future release so that console entry points can be created >automatically and installed in the shell path. I would like wordish >to be used in this way:: Â Â Â wordish my_article.rst I have read >the documentation for distutils, distribute but still, but the >overlap that the tools, and the problems that each tool solve. Can >my setup.py support the installation of the following files, or >should they be included in debian/fedora packages instead? 1. few >examples files? 2. static html documentation files? 3. man pages for >the console scripts? The distutils doesn't really support installing such things well; you can certainly include them in your *source* distribution, though. >Also, I upload a source distribution (sdist) to the Python Package >Index 4. should I use an *egg* instead? No, it's not necessary. Eggs are mainly useful as a drop-in-and-use format for application plugins (such as extensions to Chandler, Trac, and other plugin-enabled application environments), and distributing precompiled C extensions on certain platforms. easy_install and pip can both operate just fine on source distributions, and if your code is only pure Python, you don't need to distribute binaries.

2 1

using distribute instead of distutils
by Jean Daniel 22 Feb '10

22 Feb '10

Hello, I am writing a pure python module called wordish, which is similar to doctest in that it test snippets of code, parsed from an rst article and produce a report. wordish is available on Pypi in version 1.0 and the documentation is available at jdb.github.com/wordish. So far, I only distributed one file, *wordish.py* and the file was used like the following:: python -m wordish my_article.rst I think I will turn to 'distribute' for the future release so that console entry points can be created automatically and installed in the shell path. I would like wordish to be used in this way:: wordish my_article.rst I have read the documentation for distutils, distribute but still, but the overlap that the tools, and the problems that each tool solve. Can my setup.py support the installation of the following files, or should they be included in debian/fedora packages instead? 1. few examples files? 2. static html documentation files? 3. man pages for the console scripts? Also, I upload a source distribution (sdist) to the Python Package Index 4. should I use an *egg* instead? what does it change for me or the users? Thanks for your help,

1 0

[issue102] setuptools-0.6c11 regression in package_index.PackageIndex.fetch_distribution
by Tres Seaver 22 Feb '10

22 Feb '10

New submission from Tres Seaver <tseaver(a)palladion.com>: package_index.PackageIndex.fetch_distribution changed between 0.6c9 and 0.6c11, adding some logging, and returning a clone of the found distribution. However, the new code neglects to check that the dist is not None before cloning it. The attached patch fixes this bug. ---------- assignedto: pje files: setuptools-0.6c11-find_distribution_miss.patch messages: 504 nosy: pje, tseaver priority: bug status: unread title: setuptools-0.6c11 regression in package_index.PackageIndex.fetch_distribution Added file: http://bugs.python.org/setuptools/file66/setuptools-0.6c11-find_distributio… _______________________________________________ Setuptools tracker <setuptools(a)bugs.python.org> <http://bugs.python.org/setuptools/issue102> _______________________________________________

1 0

setuptools-0.6c11.win32-py2.6.exe
by Daniel Niccoli 21 Feb '10

21 Feb '10

Hello Phillip, if you install the x86-64 version of python, the windows installer "* setuptools-0.6c11.win32-py2.6.exe"* does not find any Python installation. I had to export the registry key "HKEY_LOCAL_MACHINE\SOFTWARE\Python", change it to "HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Python" and import it afterwards to be able to install the software. The installer should be changed to avoid trouble for other people. Kind regards Daniel

1 0

upload size limit on pypi
by kiorky 19 Feb '10

19 Feb '10

Hello, i am again packaging some webapp as a paster template. Now, it's turn to hudson to join minitage.paste.extras. The distribution will be around 50MB. What is the current distribution limit, and if lower, can we again increase the size ? -- -- Cordialement, KiOrKY GPG Key FingerPrint: 0x1A1194B7681112AF

2 3

Re: [Distutils] include special filetypes and subdirectories
by P.J. Eby 19 Feb '10

19 Feb '10

At 02:11 AM 2/19/2010 +0100, Assem Chelli wrote: >i have eclipse with cvs and pydev plugin's ,how can i do it,or its >automatically If your files are under CVS control (in which case you will have a bunch of directories named "CVS" in your project), then all you need is to add the include_package_data=True in your setup(). >2010/2/19, P.J. Eby <pje(a)telecommunity.com>: > > At 01:34 AM 2/19/2010 +0100, Assem Chelli wrote: > >>Hi > >> > >> > >> > >>how to change setup.py to include special filetypes and subdirectories > >>recursively in python eggs > > > > > > Option 1: Put them under revision control using CVS, Subversion, or > > any revision control system that has a setuptools plugin (in which > > case, you'll need the plugin installed in your development > > environment). Then, add 'include_package_data=True' in your setup() call. > > > > Option 2: Use the package_data setup() argument (see the distutils > > docs), and explicitly list the files and directories to > > include. This is not recursive, but will also work with plain distutils. > > > > Option 3: Use a MANIFEST.in file (see the distutils docs) and specify > > the directories to include, and also place > > 'include_package_data=True' in your setup() call. > > > > Of these, option 1 is generally the "best" option since it doesn't > > require you to maintain information in two or more places; the files > > are included as a side effect of your ordinary development practices, > > as long as you're using a revision control system. > > > >

1 0

include special filetypes and subdirectories
by Assem Chelli 19 Feb '10

19 Feb '10

Hi how to change setup.py to include special filetypes and subdirectories recursively in python eggs

2 1

Re: [Distutils] include special filetypes and subdirectories
by P.J. Eby 19 Feb '10

19 Feb '10

At 01:34 AM 2/19/2010 +0100, Assem Chelli wrote: >Hi > > > >how to change setup.py to include special filetypes and subdirectories >recursively in python eggs Option 1: Put them under revision control using CVS, Subversion, or any revision control system that has a setuptools plugin (in which case, you'll need the plugin installed in your development environment). Then, add 'include_package_data=True' in your setup() call. Option 2: Use the package_data setup() argument (see the distutils docs), and explicitly list the files and directories to include. This is not recursive, but will also work with plain distutils. Option 3: Use a MANIFEST.in file (see the distutils docs) and specify the directories to include, and also place 'include_package_data=True' in your setup() call. Of these, option 1 is generally the "best" option since it doesn't require you to maintain information in two or more places; the files are included as a side effect of your ordinary development practices, as long as you're using a revision control system.

1 0

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

2000

1999

1998

Distutils-SIG February 2010