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
Right now, this is namespaced as backports.zoneinfo, but it would make the upgrade path much easier if we also installed a zoneinfo package in site-packages.
The way I see it is that backports.zoneinfo would be a running backport of the latest features for a while (at least until we decide that the module is more or less stable), and the zoneinfo module would be there so that you can write code that seamlessly upgrades to using the standard library module, rather than using something ungainly like:
People may not realize that zoneinfo and backports.zoneinfomay point to two different things.
It may be mildly annoying to do the wheel and sdist builds if sometimes the package provides zoneinfo and backports.zoneinfo, and other times it provides just backports.zoneinfo.
Another option would be to create a second PyPI package, either zoneinfo-name or zoneinfo, explicitly mark it as python_requires >=3.6,< 3.8, and have it expose the backports.zoneinfo module as zoneinfo. I'm somewhat inclined to do it that way rather than put both in the same package, as it seems neater (though people may be confused about which one to install).
The text was updated successfully, but these errors were encountered:
Right now, this is namespaced as
backports.zoneinfo
, but it would make the upgrade path much easier if we also installed azoneinfo
package insite-packages
.The way I see it is that
backports.zoneinfo
would be a running backport of the latest features for a while (at least until we decide that the module is more or less stable), and thezoneinfo
module would be there so that you can write code that seamlessly upgrades to using the standard library module, rather than using something ungainly like:The biggest downsides I immediately see are:
zoneinfo
andbackports.zoneinfo
may point to two different things.zoneinfo
andbackports.zoneinfo
, and other times it provides justbackports.zoneinfo
.Another option would be to create a second PyPI package, either
zoneinfo-name
orzoneinfo
, explicitly mark it aspython_requires >=3.6,< 3.8
, and have it expose thebackports.zoneinfo
module aszoneinfo
. I'm somewhat inclined to do it that way rather than put both in the same package, as it seems neater (though people may be confused about which one to install).The text was updated successfully, but these errors were encountered: