Allow override of release cooldown in update-python-resources

[robinbowes]

I'm finding that this feature is blocking me releasing a new version of my python-based apps/tools for 24h.

My workflow is:

1. tag release
2. build and push to PyPi
3. bump version in Homebrew formula
4. rebuild tap

Step 4. is blocked because brew update-python-resources ignores anything newer than 24h, which I get for dependencies, but not for the new artefact that I've just built and pushed myself.

Is this an intentional block, or an oversight?

Would it be possible to add some mechanism that doesn't block like this?

[botantony]

All PyPI resources (except for the main formula URL) are on cooldown and there's no way to make an exception. You can update resources manually/via script or create formulae for your Python libraries (see certifi or cryptography for example) and use it in your formula:

depends_on "your/tap/pylib"

pypi_packages exclude_packages: ["pylib"]

[MikeMcQuaid]

@robinbowes We'd accept an opt-in flag to bypass this cooldown as long as it only applies to third-party taps and the main package and not dependencies. Work for you?

[robinbowes]

Yes, that would work for me. I'll have a dig when I get a minute and see if I can figure it out. Thanks!

[robinbowes]

@MikeMcQuaid a PR is here