On 28 Dec, 2012, at 21:23, Lennart Regebro <regebro@gmail.com> wrote:

> Happy Holidays! Here is the update of PEP 431 with the changes that emerged after the earlier discussion.

Why is the new timezone support added in a submodule of datetime?

Because several people wanted it that way and nobody objected.
 
">

(original) (raw)


On 29 Dec, 2012, at 5:48, Lennart Regebro <regebro@gmail.com> wrote:

On Fri, Dec 28, 2012 at 10:12 PM, Ronald Oussoren <ronaldoussoren@mac.com> wrote:

On 28 Dec, 2012, at 21:23, Lennart Regebro <regebro@gmail.com> wrote:

\> Happy Holidays! Here is the update of PEP 431 with the changes that emerged after the earlier discussion.

Why is the new timezone support added in a submodule of datetime?

Because several people wanted it that way and nobody objected.

Adding the new

function and exception to datetime itself wouldn't clutter the API that much


It will make the datetime.py twice as long though, and the second longest module in the stdlib, beaten only by decimal.py. Perhaps this is not a problem.

The module could be split into several modules in a package without affecting the public API if that would help with maintenance, simular to unittest.

Ronald