DST not handled correctly
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
suds (Ubuntu) |
Invalid
|
Undecided
|
Unassigned |
Bug Description
suds.sax.
The offset of the local (non-DST) timezone, in seconds west of UTC (negative in most of Western Europe, positive in the US, zero in the UK).
So using time.timezone that way only works half the year. The result is that when a datetime is used in a SOAP call, the value in the request contains the correctly formatted local time followed by an incorrect specification of which time zone was used. For example 2013-06-26 16:05:58.887627 CEST was rendered in the SOAP request as 2013-06-
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: python-suds 0.4.1-2ubuntu1 [modified: usr/share/
ProcVersionSign
Uname: Linux 3.2.0-48-generic i686
NonfreeKernelMo
ApportVersion: 2.0.1-0ubuntu17.3
Architecture: i386
Date: Wed Jun 26 17:26:42 2013
EcryptfsInUse: Yes
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1)
MarkForUpload: True
PackageArchitec
SourcePackage: suds
UpgradeStatus: Upgraded to precise on 2012-05-08 (413 days ago)
Hi Kasper
As this is an older bug report (on 12.04) and suds has been updated to the 0.7 release I'm going to mark this bug as 'Invalid'; if you still see this issue with the latest suds package version in Ubuntu 17.10, please set back to new and confirm that this is still an issue.
Thanks!