Re: [Biopython] Switching to PEP440 compliant versioning for our development code

On Thu, Jun 23, 2016 at 6:14 AM, Peter Cock <[email protected]>
wrote:

> Dear Biopythoneers,
>
> Currently we use a simple two level versioning scheme
> of 1.N for Biopython (currently at 1.67), which is all fine for
> the recent PEP standards which are important for when
> we release code via PyPI, and determining dependencies
> and ordering releases.
>
> However, as currently documented on our release process,
> in between releases we append a plus, currently 1.67+,
> and these versions are not PEP440 compliant.
>
> [...]

> having read PEP440, I think it would be clearer
> to use 1.78.dev (a development pre-release of what will
> be 1.68) instead?
>

+1

I agree with this change. But in my experience, the suffix that plays best
with Python versioning- and packaging-related tools, and follows PEP440
most literally, would be "<next_version>.dev0".

-Eric

_______________________________________________
Biopython-dev mailing list
[email protected]
http://mailman.open-bio.org/mailman/listinfo/biopython-dev