Comments (4)
It looks like named timezones are just ignored in parse.rs. The comment suggests that the C's original strptime
is broken.
println!("{}", time::strptime("Tue Jan 01 12:37:48 GMT 2013", "%a %b %d %T %Z %Y").unwrap() ==
time::strptime("Tue Jan 01 12:37:48 ETC 2013", "%a %b %d %T %Z %Y").unwrap());
=> true
However using time offsets does work
println!("{}", time::strptime("Tue Jan 01 12:37:48 +00:00 2013", "%a %b %d %T %z %Y").unwrap() ==
time::strptime("Tue Jan 01 12:37:48 +05:00 2013", "%a %b %d %T %z %Y").unwrap());
My workaround's going to be string replacement (for now).
Perhaps there could be another parse function that does what's expected?
from time.
My current thought is to drop the "support" for %Z
in 0.2. That specific formatting option requires knowledge of the actual timezone, not just the offset, and this info isn't stored anywhere. Parsing may happen, though it isn't likely.
from time.
The minimal support for %Z
has been completely dropped for 0.2.
from time.
Closing in favor of #193, which would include this.
from time.
Related Issues (20)
- Cannot Deserialize timestamp with milliseconds HOT 3
- PrimitiveDateTime does not parse with insufficient information HOT 4
- Breaking change wish-list HOT 9
- local-offset feature is leaking memory on Apple platforms HOT 2
- Compilation error for "wasm-bindgen"
- Compile error with version 0.3.32 when compiling for wasm32-unknown-unknown HOT 1
- fn OffsetDateTime::date_time(self) if private HOT 1
- Optional weekday for rfc2822 HOT 2
- year repr:last_two removed in 0.3.x? HOT 1
- Optional leading zeros and parsing HOT 3
- Implement `FromStr` for `PrimitiveDateTime` and `OffsetDateTime` HOT 1
- `subsec_{milli,micro,nano}seconds` may have over-inclusive documented ranges HOT 1
- Default `impl Deserialize`/`impl Serialize for time::OffsetDateTime` is a footgun HOT 1
- Mark the date_time function from OffsetDateTime as public HOT 1
- Bug with leap second parsing ISO 8601 HOT 6
- Renaming of `FormatItem` is a breaking change HOT 5
- How to use `serde::format_description` with `format_description::well_known` ? HOT 5
- Confusing deprecation message for `time::Instant` HOT 3
- Formatting bug on ISO8601 HOT 6
- Make `format` methods localizable HOT 6
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from time.