Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Yanked 1.4.0 release

See original GitHub issue

Hi people,

We’ve seen your newly reported issues since the release of version 1.4.0. Specifically #325 #330 seem to suggest that we introduced some behavior changes in a minor version bump. We want to correctly support all SQLAlchemy 1.4.0 and upcoming 2.0.0 features even if that means breaking our existing behaviors. While we re-evaluate the introduced changes we went ahead and yanked this release from PyPi.

Thank you for your understanding and please stay tuned for future releases!

Issue Analytics

State:
Created a year ago
Comments:5

Top GitHub Comments

1reaction

sfc-gh-alingcommented, Aug 6, 2022

thanks @kklein for info, I’m afraid conda-forge doesn’t provide a way to yank the package as pypi. we will do a patch release soon to fix the issues.

0reactions

jtillycommented, Oct 17, 2022

I’m afraid conda-forge doesn’t provide a way to yank the package as pypi. we will do a patch release soon to fix the issues.

Just FYI (probably not relevant anymore), but you can mark packages on conda-forge as broken. Just make a PR at https://github.com/conda-forge/admin-requests/

For this particular case, you would add a single file broken/snowflake-sqlalchemy-1.4.0.txt that contains noarch/snowflake-sqlalchemy-1.4.0-pyhd8ed1ab_0.tar.bz2.