So I did what Phillip suggested. Also I now don't filter out the
less-stable releases completely -- I remove the links, but still list
them, so it's easier to see what the proxy does. For example:
http://pypi-stable.maluke.com/simple/setuptools/
http://pypi-stable.maluke.com/simple/lxml
http://pyp
On 10 July 2011 18:51, P.J. Eby wrote:
> At 05:24 PM 7/10/2011 +0300, Sergey Schetinin wrote:
>>
>> If you know of any releases that are final but are filtered out in
>> that mirror, that would be more constructive.
>
> ISTM that you are currently filtering out packages whose *only* available
> ve
At 05:24 PM 7/10/2011 +0300, Sergey Schetinin wrote:
If you know of any releases that are final but are filtered out in
that mirror, that would be more constructive.
ISTM that you are currently filtering out packages whose *only*
available versions are alpha, beta, candidate, etc. So if a pac
On 10 July 2011 09:01, Andreas Jung wrote:
> Sorry but a pretty worthless effort since there is no enforced version
> schema and in addition the classifiers are often just unmaintained or wrong.
Sure. All it does is fix the problem right now, without telling anyone
to change how they do releases
Tarek Ziadé wrote:
This is not true anymore for metadata 1.2 which follow pep 386.
Which is likely a very small number of packages.
Andreas
<>___
Catalog-SIG mailing list
Catalog-SIG@python.org
http://mail.python.org/mailman/listinfo/catalog-sig
This is not true anymore for metadata 1.2 which follow pep 386. Pypi already
implements it. Pushing a non-386 version gets your action rejected.
Plus distutils 2 has a prefer final flag
Cheers
Tarek
Le 10 juil. 2011 08:01, "Andreas Jung" a écrit :
> Sorry but a pretty worthless effort since ther
Andreas Jung writes:
> Sorry but a pretty worthless effort since there is no enforced version
> schema and in addition the classifiers are often just unmaintained or
> wrong.
Conversely, the presence of a tool that uses the classifier information
in this way could encourage people to put useful
