You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 15, 2020. It is now read-only.
@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 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...
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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)
The text was updated successfully, but these errors were encountered: