Comments on: Setup.py sdist not including all files http://blog.mfabrik.com/2009/07/24/setup-py-sdist-not-including-all-files/ Freedom delivered. Mon, 19 Sep 2011 19:02:42 +0000 hourly 1 http://wordpress.org/?v=3.2.1 By: Mikko Ohtamaa http://blog.mfabrik.com/2009/07/24/setup-py-sdist-not-including-all-files/comment-page-1/#comment-867 Mikko Ohtamaa Mon, 27 Jul 2009 12:57:07 +0000 http://blog.twinapex.fi/?p=230#comment-867 Thank you for everyone for very constructive comments. I was indeed using SVN so I was bitten by the version bug. For ordinal users, it is very hard to distinguish between setuptools and distutils. setup.py is the only interface they see and the only interface they should interact with (...because it's the only one they see) In the future versions I hope setuptools/distutils/distribute/whatever will simply have a setup.py statement included_files="x" where x could be 1) version control system name which is used to get the included file list. Possible options svn1.4, svn1.5, hg, git, so on 2) regexp patterns which are used to include files (current MANIFEST.in content) Because the option is in setup.py it would be clearly visible and self-explaining for everyone. Thank you for everyone for very constructive comments.

I was indeed using SVN so I was bitten by the version bug.

For ordinal users, it is very hard to distinguish between setuptools and distutils. setup.py is the only interface they see and the only interface they should interact with (…because it’s the only one they see)

In the future versions I hope setuptools/distutils/distribute/whatever will simply have a setup.py statement

included_files=”x”

where x could be

1) version control system name which is used to get the included file list. Possible options svn1.4, svn1.5, hg, git, so on

2) regexp patterns which are used to include files (current MANIFEST.in content)

Because the option is in setup.py it would be clearly visible and self-explaining for everyone.

]]> By: Toni Mueller http://blog.mfabrik.com/2009/07/24/setup-py-sdist-not-including-all-files/comment-page-1/#comment-866 Toni Mueller Mon, 27 Jul 2009 10:58:06 +0000 http://blog.twinapex.fi/?p=230#comment-866 If you don't use SVN, but something else (anything, actually), then you can maybe coerce setuptools to respect that other SCM, or be screwed. Found it out the hard way, too. :| If you don’t use SVN, but something else (anything, actually), then you can maybe coerce setuptools to respect that other SCM, or be screwed. Found it out the hard way, too. :|

]]> By: PJ Eby http://blog.mfabrik.com/2009/07/24/setup-py-sdist-not-including-all-files/comment-page-1/#comment-863 PJ Eby Sat, 25 Jul 2009 17:03:29 +0000 http://blog.twinapex.fi/?p=230#comment-863 That silent failure mode is actually inherited from the distutils, btw. Setuptools simply doesn't fix it. That silent failure mode is actually inherited from the distutils, btw. Setuptools simply doesn’t fix it.

]]> By: Clayton Parker http://blog.mfabrik.com/2009/07/24/setup-py-sdist-not-including-all-files/comment-page-1/#comment-854 Clayton Parker Fri, 24 Jul 2009 16:47:28 +0000 http://blog.twinapex.fi/?p=230#comment-854 You don't need to declare a manifest file if you use a subversion working copy (<= svn 1.5 at the moment, another thing Distribute will help with). You could do the following: $ svn co http://svn.plone.org/svn/collective/plonetheme.twinapex/tags/1.0 plonetheme.twinapex $ cd plonetheme.twinapex $ python setup.py sdist upload This method uses the .svn/entries files to know what should be a part of the distribution. You don’t need to declare a manifest file if you use a subversion working copy (<= svn 1.5 at the moment, another thing Distribute will help with). You could do the following:

$ svn co http://svn.plone.org/svn/collective/plonetheme.twinapex/tags/1.0 plonetheme.twinapex
$ cd plonetheme.twinapex
$ python setup.py sdist upload

This method uses the .svn/entries files to know what should be a part of the distribution.

]]> By: Steve McMahon http://blog.mfabrik.com/2009/07/24/setup-py-sdist-not-including-all-files/comment-page-1/#comment-853 Steve McMahon Fri, 24 Jul 2009 15:15:28 +0000 http://blog.twinapex.fi/?p=230#comment-853 Hi Mikko, An alternative to building a manifest is to build the sdist from within an svn checkout. Everything under version control will be included automatically. Of course, then there are all the problems with setup.py and newer versions of svn.... Steve Hi Mikko,

An alternative to building a manifest is to build the sdist from within an svn checkout. Everything under version control will be included automatically.

Of course, then there are all the problems with setup.py and newer versions of svn….

Steve

]]>