hardcoded version.txt leads to "IOError: [Errno 2] No such file or directory: 'setup.py'" about zest.releaser HOT 7 CLOSED

Well, normally everything works with a setup.py.

Allowing a version.txt in the main directory is a left-over from ancient pre-setuptools zope products. But... surprisingly handy if it is a non-setuptools project like some documentation or even something with a Makefile or so.

The error you get is because zest.releaser cannot find a version.txt (which you moved to a subdirectory). In those cases there must be a setup.py, so it reads it. And fails.

I could add a better error message ("neither version.txt or setup.py found"), but that gives too much prominence to the version.txt, which is effectively a corner case (even though I use it myself, too :-) )

I also don't think it is a good idea to start looking in subdirectories for the version.txt. Moving it back into the project root is the quickest solution.

from zest.releaser.

You are too modest, zest.releaser is a great tool even for non-python projects!
In that case the "cornercase" become the main use-case.

I just converted tens of packages to docs/version.rst, docs/changes.rst
I now started to do the same conversion for buildouts which results in a very nice consistency

To be able to release, I currently to need patch

versionfile = self.filefind(['version.txt', 'version'])
into
versionfile = self.filefind(['version.txt', 'version', 'version.rst']) # use TXT_EXTENSIONS

But then I need to make sure all teammembers apply the same patch, or otherwise I'll be the only one able to make releases. :(

IMHO, this seems like a small change to complete #65

from zest.releaser.

Ah, I see.

a) I forgot that zest.releaser checks in subdirectories :-)

b) Hey, I forgot to add the TXT_EXTENSIONS fix to the spot you've indicated.

I've fixed it in 1dc7628

(I forgot to make a branch, so it isn't a pull request).

I'm trying to upload 3.53.1, but pypi upload is failing for me.

from zest.releaser.

https://sourceforge.net/p/pypi/support-requests/438/

from zest.releaser.

@WouterVH can you try 3.53.2? The upload finally succeeded :-)

from zest.releaser.

For the record/clarity:

• At Zest we add version.txt in the buildout root of our client projects and use zest.releaser to make tag releases.
• For old Zope/Plone Products, I expect the version to be in a sub directory, for example Products/Poi/version.txt.

from zest.releaser.

Ok, then the version.txt (note: version.rst is fine, too, now) is in more widespread use than I thought.

All my buildouts also have setup.py that lists all the dependencies, so I already have a place for the version :-)

I assume it all works OK, so I'm closing this issue.

from zest.releaser.