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
I'm interested in pytz linting, specifically preventing pytz timezone classes (BaseTzInfo) from being used directly as the tzinfo argument with datetime.datetime(tzinfo=) and with .replace(tzinfo=), since that is almost always an error.
Would you be open to a PR adding pytz added as a dependency and checks around those cases?
The text was updated successfully, but these errors were encountered:
@djmattyg007 Yes, I would agree 🙂 We have some legacy code in pytz that we aren't prepared to rewrite, but we also don't want any new usage of pytz sneaking into the codebase. It would be easier to enforce this with a linting rule since we can't yet remove pytz as a direct dependency and it is a downstream dependency of a lot of other packages we use at this point.
I'm interested in pytz linting, specifically preventing pytz timezone classes (
BaseTzInfo
) from being used directly as thetzinfo
argument withdatetime.datetime(tzinfo=)
and with.replace(tzinfo=)
, since that is almost always an error.Would you be open to a PR adding pytz added as a dependency and checks around those cases?
The text was updated successfully, but these errors were encountered: