Python packaging 

I noticed tzdata which is considered a part of the CPython project, a "first party package" but hosted on PyPI. Quoting

> The term "first party" here is distinguished from "third party" in that, although it is is distributed via PyPI and is not currently included in Python by default, it is to be considered an official sub-project of CPython rather than a "blessed" third-party package.

Python packaging 

It is possible that first or blessed third party packages might be the future if (the contentious "removing dead batteries" proposal) decides to go forward.

But unlike the latter here is a clear need for separating tzdata, since timezones are often announced in short notice and must be deployed on a reactive style.

Show thread

Python packaging 

I am divided on the thing. On one hand, yes it is cool to have a minimalistic Python deployed on new platforms: the web and the native mobile space.

However, I don't like that because it:
1. breaks backwards compatibility
2. adds another layer of dependency resolution
3. takes away the batteries included nature of Python, which is one of its defining characteristic.

Python packaging 

@ashwinvis I think it is a good step. There are ancient packages that are not useful to most users. They are not talking about removing packages to solve real everyday problems.

Sign in to participate in the conversation
Mastodon @ SUNET

The social network of the future: No ads, no corporate surveillance, ethical design, and decentralization! Own your data with Mastodon!