Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

time.Parse - numeric time zones and spacing #518

Closed
hoisie opened this issue Jan 12, 2010 · 5 comments
Closed

time.Parse - numeric time zones and spacing #518

hoisie opened this issue Jan 12, 2010 · 5 comments
Labels
FrozenDueToAge

Comments

@hoisie
Copy link
Contributor

hoisie commented Jan 12, 2010 

There are two variations of UnixDate that don't parse (and it would make
sense if they did):

1. `Tue Jan 12 02:52:59 -0800 2010` - via ruby's Time.now -- with numeric
time zone

2. `Tue Jan 12 02:43:17 PST 2010` - one space instead of two between Month
and day)
@robpike
Copy link
Contributor

robpike commented Jan 13, 2010

Comment 1:

Owner changed to r...@golang.org.

Status changed to Started.

@robpike
Copy link
Contributor

robpike commented Jan 13, 2010

Comment 2:

I'll think about the ruby time format - it's unique and weird.  Meanwhile I've addressed
the spacing issues.

@robpike
Copy link
Contributor

robpike commented Jan 13, 2010

Comment 3:

Status changed to Thinking.

@hoisie
Copy link
Contributor Author

hoisie commented Jan 13, 2010

Comment 4:

Thanks for doing the spacing thing, it makes things a lot easier for me. 
About the ruby time -- it popped up in the twitter api: 
http://apiwiki.twitter.com/Return-Values (see created_at), but I'm not sure how common 
it really is. I'd hope that web developers would be smart enough to use Time.now.utc 
instead of just Time.now, but who knows...

@robpike
Copy link
Contributor

robpike commented Jan 14, 2010

Comment 5:

This issue was closed by revision d9283b2.

Status changed to Fixed.

Merged into issue #-.

@hoisie hoisie added the fixed label Jan 14, 2010
@golang golang locked and limited conversation to collaborators Jun 24, 2016
@rsc rsc unassigned robpike Jun 22, 2022
This issue was closed.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
FrozenDueToAge
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@hoisie @robpike @gopherbot