Re: Using a ChangeLog as a canonical source of package metadata

2015-01-14 Thread Ben Finney
Ben Finney ben+pyt...@benfinney.id.au writes: The idea is to parse from the Changelog the version metadata, and record it in Setuptools metadata. Then the ‘pkg_resources’ module of Setuptools allows programmatic access to that metadata. One tricky aspect is: at what specific point should the

Re: Using a ChangeLog as a canonical source of package metadata

2015-01-13 Thread Steven D'Aprano
On Tue, 13 Jan 2015 00:09:04 -0800, wxjmfauth wrote: Le mardi 13 janvier 2015 08:00:06 UTC+1, Steven D'Aprano a écrit : On Mon, 12 Jan 2015 05:24:00 -0800, wxjmfauth wrote: To tell you the truth, I'm unable to put your product to work. If you follow the instructions in the README,

Re: Using a ChangeLog as a canonical source of package metadata

2015-01-12 Thread Steven D'Aprano
On Mon, 12 Jan 2015 05:24:00 -0800, wxjmfauth wrote: To tell you the truth, I'm unable to put your product to work. If you follow the instructions in the README, and it still doesn't work, that's a bug and I will be happy to fix it. If you insist on doing things your own way, and breaking

Re: Using a ChangeLog as a canonical source of package metadata (was: Announce: PyPrimes 0.2.1a)

2015-01-11 Thread Steven D'Aprano
Ben Finney wrote: [...] The perils of duplicate sources of information: a Changelog makes claims about which version is latest, but the packaging metadata comes from somewhere else. This problem is addressed quite well, in my opinion, by the Debian packaging tools. The tools by default read

Re: Using a ChangeLog as a canonical source of package metadata

2015-01-11 Thread Ben Finney
Steven D'Aprano steve+comp.lang.pyt...@pearwood.info writes: I currently read this metadata from the Python code itself. The advantages of putting the metadata into the source code include: - the source code is the definitive source of information about itself; The Changelog document should

Re: Using a ChangeLog as a canonical source of package metadata

2015-01-11 Thread Steven D'Aprano
On Sun, 11 Jan 2015 12:37:03 -0800, wxjmfauth wrote: 1) I downloaded pyprimes-0.2.1a.tar.gz 2) I extracted the relevant part, the py files, the pyprimes subdirectory, awful.py, compat23.py, factors.py, test.py, .. and put in d:\junk That is not the way packages work. pyprimes is a

Using a ChangeLog as a canonical source of package metadata (was: Announce: PyPrimes 0.2.1a)

2015-01-08 Thread Ben Finney
Steven D'Aprano steve+comp.lang.pyt...@pearwood.info writes: Ben Finney wrote: The source has a ‘CHANGES.txt’ file which has no entry later than version 0.2a. Why was the later version made, and when will the change log be updated for that? Ah, I knew I forgot something! The perils of

Re: Using a ChangeLog as a canonical source of package metadata (was: Announce: PyPrimes 0.2.1a)

2015-01-08 Thread Chris Angelico
On Fri, Jan 9, 2015 at 11:06 AM, Ben Finney ben+pyt...@benfinney.id.au wrote: I've now produced a small Python library which knows how to transform a reST Changelog to package metadata; and how to get that package metadata into and out of a Python distribution with Distutils. The result is