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
The vobject package includes support for obtaining timezone information from the Windows registry, implemented in the win32tz.py file. It is not imported by any of the other vobject source files: it appears to have been provided basically as a helpful facility if needed by a client application.
This file looks like it has never been ported to Python 3: it imports _winreg (renamed to winreg in 3.0), and uses xrange() (without six.moves), for example.
It seems also that dateutil provides equivalent functionality from version 2.5.0, which I imagine is much better maintained.
With the change to API v1.0, this file could be removed, with a recommendation to switch to using dateutil instead. This would need an assessment of whether there's actually anything unique about what is implemented, vs. what's in dateutil.
The text was updated successfully, but these errors were encountered:
The vobject package includes support for obtaining timezone information from the Windows registry, implemented in the win32tz.py file. It is not imported by any of the other vobject source files: it appears to have been provided basically as a helpful facility if needed by a client application.
This file looks like it has never been ported to Python 3: it imports
_winreg
(renamed towinreg
in 3.0), and usesxrange()
(withoutsix.moves
), for example.It seems also that
dateutil
provides equivalent functionality from version 2.5.0, which I imagine is much better maintained.With the change to API v1.0, this file could be removed, with a recommendation to switch to using
dateutil
instead. This would need an assessment of whether there's actually anything unique about what is implemented, vs. what's indateutil
.The text was updated successfully, but these errors were encountered: