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.

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

Add "T" separator to FORMAT_RFC3339 #1138

Open
krowbar opened this issue Oct 27, 2022 · 2 comments · May be fixed by #1201
Open

Add "T" separator to FORMAT_RFC3339 #1138

krowbar opened this issue Oct 27, 2022 · 2 comments · May be fixed by #1201
Assignees

Comments

@krowbar
Copy link

krowbar commented Oct 27, 2022

Include "T" separator in the format string for FORMAT_RFC3339

Currently the FORMAT_RFC3339 does not include the "T" separator, but technically it is required.
From https://www.rfc-editor.org/rfc/rfc3339#page-7

ISO 8601 states that the "T" may be omitted under some circumstances. This grammar requires the "T" to avoid ambiguity.

I realize that str() already returns the RFC3339 format with the "T".

@krisfremen
Copy link
Member

hey @krowbar, str() returns ISO8601 which does have the "T", as per https://github.com/arrow-py/arrow/blob/1.2.3/arrow/arrow.py#L792

in order to not break backwards compatibility of people that might already be using this formatter, I'd say we can add another one, FORMAT_RFC3339_STRICT, to add the "T".

@jadchaar @anishnya @systemcatch thoughts?

@conoremclaughlin
Copy link

Chiming in to say this bit us. Expected the T as the most standard string format for datetimes now.

@krisfremen krisfremen self-assigned this Oct 31, 2024
@krisfremen krisfremen linked a pull request Nov 6, 2024 that will close this issue
5 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants