Re: python setup.py sdist -does not include all files under revision

[Jason Gerard DeRose <jderose@xxxxxxxxxxxxxxx>]

Lukasz Szybalski wrote:
> Hello,
> I'm trying to make a release and would like to upload tar.gz file to launchpad.
> After some searching I found out that this command should get that done for me:
> 
> python setup.py sdist
> 
> Unfortunately it does not include all files in the package/ files
> under revision.
> 
> I've installed setuptools_bzr in a hope that 'python setup.py sdist'
> would include all the folders I have included in my package.

I've never used setuptools_bzr, but my personal recommendation is to
manually create your MANIFEST.in file... you probably don't want always
to include everything under version control in your sdist package. Often
times you will have certain scripts and whatnot that are handy from
within the checkout, but just don't make sense to include in the sdist
package.

For what it's worth, I've been working on a tool to make it super easy
to go from the bzr branch of a Python project (packaged using
setuptools) to a Debian/Ubuntu package, including building under
pbuilder and uploading to your PPA. For the past 5 months I've been too
busy with my day job to really work on it, but prior to that I made a
decent start. It's called bzr-release:

  https://launchpad.net/bzr-release

It's self-hosting so it is itself a good example of how to use it, plus
I have two other projects using it:

  https://launchpad.net/pyawesome

  https://launchpad.net/snakebite

Please let me know if you happen to be interested in testing/developing
bzr-release... I'm sure some outside interest would help guilt/inspire
me to work on it more.  ;)

Best of luck!

Cheers,
Jason DeRose

> Unfortunately that is not the case.
> 
> If I go back to the some previous version that is till in svn then it
> seems to work correctly and include every file.
> 
> Any ideas how can I make this work with bzr -> launchpad.
> 
> Thanks,
> 
> 
> python setup.py sdist
> running sdist
> running egg_info
> writing requirements to datahub.egg-info/requires.txt
> writing datahub.egg-info/PKG-INFO
> writing top-level names to datahub.egg-info/top_level.txt
> writing dependency_links to datahub.egg-info/dependency_links.txt
> writing entry points to datahub.egg-info/entry_points.txt
> writing manifest file 'datahub.egg-info/SOURCES.txt'
> warning: sdist: standard file not found: should have one of README, README.txt
> creating datahub-0.7dev
> creating datahub-0.7dev/datahub
> creating datahub-0.7dev/datahub.egg-info
> making hard links in datahub-0.7dev...
> hard linking setup.cfg -> datahub-0.7dev
> hard linking setup.py -> datahub-0.7dev
> hard linking datahub/__init__.py -> datahub-0.7dev/datahub
> hard linking datahub.egg-info/PKG-INFO -> datahub-0.7dev/datahub.egg-info
> hard linking datahub.egg-info/SOURCES.txt -> datahub-0.7dev/datahub.egg-info
> hard linking datahub.egg-info/dependency_links.txt ->
> datahub-0.7dev/datahub.egg-info
> hard linking datahub.egg-info/entry_points.txt ->
> datahub-0.7dev/datahub.egg-info
> hard linking datahub.egg-info/not-zip-safe -> datahub-0.7dev/datahub.egg-info
> hard linking datahub.egg-info/requires.txt -> datahub-0.7dev/datahub.egg-info
> hard linking datahub.egg-info/top_level.txt -> datahub-0.7dev/datahub.egg-info
> copying setup.cfg -> datahub-0.7dev
> Writing datahub-0.7dev/setup.cfg
> tar -cf dist/datahub-0.7dev.tar datahub-0.7dev
> gzip -f9 dist/datahub-0.7dev.tar
> removing 'datahub-0.7dev' (and everything under it)
> 
> 
> 
>

Attachment: signature.asc
Description: OpenPGP digital signature