Check fad sdist .tar.gz files about zest.releaser HOT 7 CLOSED

Even better would be a check that exports the source tree from version control (svn export, git archive, bzr export, hg archive) and compares it to the archive produced by setup.py sdist.

I've ad-hoc makefile rules doing that on 'make distcheck' on all of my projects. It helps me catch files I've forgotten to add to MANIFEST.in.

from zest.releaser.

check-manifest now has a zest.releaser entry-point that will check MANIFEST.in for completeness before the release.

from zest.releaser.

Sounds nice! I'll try it out. If it works the way it sounds, I'll add a suggestion somewhere in the zest.releaser docs.

It has been a long time since I added the entry point mechanism: did it work OK for you? Docs good enough? Just wondering in general :-) Not many people actually made use of them, that's why I want to know.

from zest.releaser.

It worked fine. I used zest.pocompile as an example, which taught me about zest.releaser.utils.ask, which was very useful.

There was one minor stumbling block: I initially misspelled the entry point name as zest.releaser.prerelease.before. After I fixed it to be zest.releaser.*prereleaser*.before, I wasted some time in pdb because I didn't realize pip install . wouldn't actually update the egg metadata in my virtualenv because the 0.8.dev version number didn't change. pip install -U . fixed that and then it was plain sailing.

from zest.releaser.

@mauritsvanrees : would check-manifest be something for the recommended list? See #49

from zest.releaser.

@reinout: definitely, it was already on that list for me. :-)

And that seems enough reason to close this issue.

Alternatively, either zest.releaser or a plugin could actually try installing it in a virtualenv:

virtualenv dummy
cd dummy
bin/pip install --no-deps ../dist/my-distribution-file.tgz

Or with similar code after the release try to install it from PyPI:

bin/pip install --no-deps actual-package-name

That means a dependency on virtualenv, though everyone should already have that. Best done as a plugin I guess.

Anyway, I'll close this issue now, but at least there are a few more ideas to work on if anyone wants to.

from zest.releaser.

I said I would close the issue, so I should do that...

from zest.releaser.