At second thought it might not be a bug in python-tz, but some
undefined behavior that results from the pandas use of tz._utcoffset:
> tz = pytz.timezone('Asia/Tokyo')
> dt = datetime.datetime(2011,1,1)
>
> In[76]: tz.utcoffset(dt)
> Out[76]: datetime.timedelta(0, 32400)
>
> In
On Tue, 28 Mar 2017 15:18:20 +0200, Gert Wollny wrote:
> I did some digging:
> > Maybe it's a bug in python-tz?
> Most likely:
FWIW, python-tz also has a FTBFS bug:
https://bugs.debian.org/858133
Cheers,
gregor
--
.''`. https://info.comodo.priv.at/ - Debian Developer
Hello,
I did some digging:
> Maybe it's a bug in python-tz?
Most likely:
Pandas uses this code to get the time offset for the local time
in tslib.pyx:
cpdef _get_utcoffset(tzinfo, obj):
try:
return tzinfo._utcoffset
except AttributeError:
return
Hi James,
I'm just forwarding the issue to python-tz maintainers - may be
they will be able to clarify it.
Thanks for the hint
Andreas.
On Tue, Mar 28, 2017 at 12:05:22PM +0100, James Cowgill wrote:
> > I admit that when reading the bug report I have no idea how to fix it.
> > I can
Hi,
On 28/03/17 10:37, Andreas Tille wrote:
> tags 858260 help
> thanks
>
> Hi,
>
> I admit that when reading the bug report I have no idea how to fix it.
> I can confirm that I can reproduce the issue in a recent unstable
> chroot. I have added maintainers of tzdata, Debian Science and Debian
5 matches
Mail list logo
