[issue31700] one-argument version for Generator.typing

2021-11-30 Thread Zeth


Zeth  added the comment:

I don't get why this is closed. It is a bug. The Generator type annotation 
works differently than the others, it shouldn't.

Sebastian Rittau is correct here, the closer doesn't seem to have understood. 

As for using Iterator instead as the documentation suggests, that makes a 
mockery of the whole process. You might as well set everything to Any.

--
nosy: +zeth

___
Python tracker 
<https://bugs.python.org/issue31700>
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue37962] Improve ISO 8601 timezone support in the datetime.fromisoformat() method

2019-08-27 Thread Zeth


Zeth  added the comment:

Did you read the attached PR? For three lines longer, the method becomes more 
generally useful now.

As pointed out in the other thread that you pointed to, Javascript can parse 
Python's seralised datetime object but Python cannot parse Javascript's due to 
the fact that you don't want to.

That other thread points to a third thread that starts in 2012 so it seems that 
you really think that is a feature rather than a bug.

The name of the method is fromisoformat, not "parse our internal home made 
format". The line in the documentation seems a bit weird to me to be honest. It 
is saying that we could make it generally useful for you user but we don't want 
to.

The reply to this bug, "use the dateutil.parser.isoparse that I maintain 
instead" is beside the point, we are talking about the standard library one. 
Why not put that in the standard library then if it can actually parse iso 8601 
format?

--

___
Python tracker 
<https://bugs.python.org/issue37962>
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue37962] Improve ISO 8601 timezone support in the datetime.fromisoformat() method

2019-08-27 Thread Zeth


New submission from Zeth :

The datetime.datetime.fromisoformat() method unnecessarily rejects datetime 
strings that are valid under ISO 8601 if timezone uses the UTC  designator or 
it only has hours.

In ISO 8601, section 4.2.5.1: "When it is required to indicate the difference 
between local time and UTC of day, the representation of the difference can be 
expressed in hours and minutes, or hours only."

And Section 4.2.4, UTC shall be expressed "by the UTC designator [Z]".

A key use case of the latter is being able to parse JavaScript Date objects 
(e.g. dates that have come from a web frontend or a JSON document). This 
considerably improves the usefulness of the datetime.fromisoformat method.

--
messages: 350630
nosy: zeth
priority: normal
pull_requests: 15224
severity: normal
status: open
title: Improve ISO 8601 timezone support in the datetime.fromisoformat() method

___
Python tracker 
<https://bugs.python.org/issue37962>
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com



[issue37876] Tests for Rot13 codec

2019-08-16 Thread Zeth


New submission from Zeth :

Julius Caesar might have written the Rot13 codec, but he forgot to write unit 
tests, dragging down test coverage.

--
components: Tests
messages: 349874
nosy: zeth
priority: normal
pull_requests: 15033
severity: normal
status: open
title: Tests for Rot13 codec
type: enhancement
versions: Python 3.9

___
Python tracker 
<https://bugs.python.org/issue37876>
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com