On Thu, Jan 6, 2022 at 7:20 AM Levi Muniz <levi.mu...@quantum.com> wrote:
> Thanks for the suggestions so far! > > I'll probably end up doing some combination of reading from RSS/Atom then > emailing myself with the updates. There seems to be a few services that can > do this, but most of them require creating an account and cost money at a > certain point. Might be a fun side project for me. :P > > That's definitely your prerogative > It's bizarre to me that there's no real standard push-style solution to > this problem yet. RSS is great, though I haven't considered using it until > now. It'd be a bit of an outlier for me to do that just for flake8. > > There are tonnes of services that will send you change requests with updated dependencies. A few examples - If you're already using GitHub, dependabot can do it. pyup.io can do it. Snyk can do package updates (at least for security updates). This is actually a solved problem, you just need to pick your solution. > Just some interesting thoughts: Who should be responsible for notifying > users of new releases? Developers themselves? Package repositories? SCM > systems? What format would be most widely accepted? > If GitHub weren't trying to lock down all aspects of development, they could do this based on when a tag is published. Instead, they want developers to do more work to lock them and their users into the platform by publishing releases and release artifacts. As soon as you start doing that, you get people complaining that all artifacts starting at the dawn of the project aren't published, and if one developer takes it upon themselves to publish one release, any future releases done by someone else suddenly become "missing". PyPI is already doing its best to operate at scale and is thoroughly abused by some automations. As a result, they've removed certain APIs. To ask them to implement this would be unreasonable in my opinion unless there were a better way to fund its operation and development. > The information contained in this transmission may be confidential. Any > disclosure, copying, or further distribution of confidential information is > not permitted unless such privilege is explicitly granted in writing by > Quantum. Quantum reserves the right to have electronic communications, > including email and attachments, sent across its networks filtered through > security software programs and retain such messages in order to comply with > applicable data security and retention requirements. Quantum is not > responsible for the proper and complete transmission of the substance of > this communication or for any delay in its receipt. > _______________________________________________ > code-quality mailing list -- code-quality@python.org > To unsubscribe send an email to code-quality-le...@python.org > https://mail.python.org/mailman3/lists/code-quality.python.org/ > Member address: graffatcolmin...@gmail.com >
_______________________________________________ code-quality mailing list -- code-quality@python.org To unsubscribe send an email to code-quality-le...@python.org https://mail.python.org/mailman3/lists/code-quality.python.org/ Member address: arch...@mail-archive.com
