On Tue, Feb 11, 2014 at 11:33 AM, anatoly techtonik <techtonik@gmail.com> wrote:

I think that final decision whatever package version is prerelease or not
should be made by package maintainer, and (s)he should have a final
judgement over this fact. But inventors of prerelease feature didn't even
think that people may not want and still don't want this features.

But package maintainers have the final judgement!  A package is NOT a pre-release if it has a PEP 440 compliant version number without any pre-release or development segment. A simple rule.

The problem is how to deal with old packages with non compliant versions which now are not get installed by default. I would say:
- If you are the maintainer of the legacy package, just release a new version with a compliant version.
- If you are the maintainer of a project that needs this legacy package, just adjust your requirements file as described in [0]

The versioning scheme proposed in PEP440 has a lot of advantages (which are described in the PEP). But it comes with some rules that we need to comply.

cheers,

Hernán

[0] http://www.pip-installer.org/en/latest/logic.html#pre-release-versions




On Tue, Feb 11, 2014 at 11:33 AM, anatoly techtonik <techtonik@gmail.com> wrote:
On Tue, Feb 11, 2014 at 10:48 AM, Paul Moore <p.f.moore@gmail.com> wrote:
> On 11 February 2014 07:20, Georg Brandl <g.brandl@gmx.net> wrote:
>>> "Make it optional" is a very good principle for those cases
>>> when you can not predict how users are going to use your
>>> feature and if they need it at all.
>>
>> I have no idea what you are talking about.  Care to give some context?
>
> Anatoly has just raised a series of issues against pip, all
> essentially reiterating the same point that he doesn't like pip's new
> handling of prerelease vs release versions (which was thrashed out and
> agreed in a PEP)  I assume he's trying to get support for some vague
> meta-point here in the hope that by doing so he'll feel justified in
> arguing further on the pip issues :-(

Right. Smart people invented prerelease feature for PyPI, which works
the following way:

 - if pip thinks that your version is not PEP compliant, it won't install it,
   because it thinks that everything what is not PEP aware is prerelease

I think that final decision whatever package version is prerelease or not
should be made by package maintainer, and (s)he should have a final
judgement over this fact. But inventors of prerelease feature didn't even
think that people may not want and still don't want this features.

That's why I proposed "Make it optional" principle as an engineering
practice for solutions that affect the whole net.
_______________________________________________
Python-ideas mailing list
Python-ideas@python.org
https://mail.python.org/mailman/listinfo/python-ideas
Code of Conduct: http://python.org/psf/codeofconduct/