Galen S. Swint

This appears to still be an issue - it leads to the need for quite a bit of troubleshooting of "what went wrong" when in fact it's a bug in...

With the release of Pandas 2.2, please be aware that Pandas seems to require SQLAlchemy 2.0+ with potential that they revert to support SA 1.4 in a later maintenance release....

Wanted to vote in favor of maintaining backward compatibility. We are also using a snowflake database behind sqlalchemy and are having this problem with the versioning. It would be nice...

Hi @skanwwal That's not an nfldb problem. Please check the anaconda or stackoverflow boards for your answer. Good luck, Galen

I forked nfldb with the idea that I might a) get it off of deprecated python, and then b) play with it eventually. But I would not describe myself as...

Strong vote against making it default. Currently on a google-search-binge to try to see why I can't get rid of nano as the default root editor. I'd remove it totally...

I'm also running into this and also running in a monorepo style (for better or worse). I support the notion of the git tag being "{project-name}/{pep440_version}" which is similar to...

Has anyone identified a potential workaround here? A bit frustrating that this issue has been hanging out since 2019. I too get an invalid spec error when I try to...

I have run into a variation of this and after a conversation with Claude and spelunking the Excel XML, it seems to be caused by the fact that the data...