Version 1.0.0 changes

[systemcatch]

See #832 for a complete list of changes in version 1.0.0 which has been a long time coming 🎉

Feel free to discuss or ask any questions here.

[flatiron32]

The documentation still says that arrow.get(None) returns the current time UTC.

[jadchaar]

Thanks for letting us know. This will be fixed in #939.

[K3UL]

Hello,
The changelog for 1.0 states that Arrow now supports Python 3.9 and PEP484 type annotations. What does it mean exactly ? Are there some examples ?

I have been using Arrow with Python 3.9 and annotations with version 0.17, without a problem so I am curious about this :)

[jadchaar]

Great question! Arrow could be used without any issue prior to v1.0 with a type annotation-based Python project, but uses and invocations of Arrow-based objects and types would not be checked by type checkers like mypy. Adding the PEP 484-style annotations to Arrow allows for type-checkers to statically analyze your uses of Arrow objects and types in your codebase to ensure that the correct types are being passed in and used throughout your code. So if you for example pass a type None to an Arrow function that does not support nullable types as input, mypy would throw a type-checking error so that the incompatibility can be fixed before it causes unintentional exceptions during execution :).

Thanks for using Arrow and we appreciate the question :D.

[K3UL]

Ah I see, it is about typing the Arrow codebase, I had a feeling it was something like that. I did see some new errors popping up in my checker (I use PyRight), especially a nice one telling me that I might be doing arrow.get(None) instead of a string, so I see what you mean.

Thank you very much for the quick answer (and for a great tool) !