search

pypa / pep470

5 stars 6 forks source link

Running pep470 results in "old" updates via RSS #2

Open peterjc opened 9 years ago

peterjc commented 9 years ago

We just ran the tool to upload some of our older releases to be hosted on PyPI.

This triggered a flurry of tweets from https://github.com/tell-k/pypi-updates from historic @Biopython releases, resulting in potential user confusion. See also https://twitter.com/Biopython/status/647326773500362752

Is there any easy way for the pep470 tool to exclude these updates from the RSS feed on PyPI?

(Or should I file an issue to see if the Twitter-bot can be more selective? CC @tell-k)

tell-k commented 9 years ago

@peterjc

(Or should I file an issue to see if the Twitter-bot can be more selective? CC @tell-k)

That's difficult, unfortunately. The feed is not known whether due to pep470.

See also https://pypi.python.org/pypi?:action=rss

if you wish, I may delete old tweets manually. thx

peterjc commented 9 years ago

@tell-k - I'm not too worried about the automatic tweets for @Biopython, there's little point deleting the tweets now - but thanks for the offer.

However, I anticipate you'll see a lot more of this in the next month as people start using pep470 after receiving emails from the PyPI Administrator Donald Stufft suggesting it - so if triggering changes in the RSS feed can be avoided it would be good.

tell-k commented 9 years ago

@peterjc I agree with you. If there is any good solution, I gladly do it. thx.

peterjc commented 9 years ago

@tell-k My only suggestion is that your code check all available versions of a package on PyPI in order to spot if an RSS entry is an old or new release. Assuming PEP440 rules are followed, that should be straightforward https://www.python.org/dev/peps/pep-0440/ and if you cannot determine this this automatically, then I'd tweet it anyway. This does seem like quite a complex solution though - not an easy fix.

I think the best fix is probably within PyPI though...