[Python-Dev] PEP 594 - a proposal for unmaintained modules
Steven D'Aprano
steve at pearwood.info
Sun May 26 21:55:02 EDT 2019
More information about the Python-Dev mailing list
Sun May 26 21:55:02 EDT 2019
- Previous message (by thread): [Python-Dev] PEP 594 - a proposal for unmaintained modules
- Next message (by thread): [Python-Dev] PEP 594 - a proposal for unmaintained modules
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Sun, May 26, 2019 at 04:03:11PM +0300, Ivan Pozdeev via Python-Dev wrote: > On 24.05.2019 9:55, Steven D'Aprano wrote: > >I don't know if this is a good idea or a terrible idea or somewhere in > >between, so I'm throwing it out to see if anyone likes it. [...] > This would greately damage Python's image as a mature, reliable product, > something that you can bank on for your critical tasks. > > By including something into the offer, we implicitly endorse it and claim > that we want out users to use that rather than competing offers. Do we? I don't think that is the case for everything -- we certainly don't want people using private or undocumented functions, nor do we want them using deprecated code. [...] > You may argue that marking it as unsupported would do the same but it > wouldn't. This mean I'll have to be constantly on the lookout for hidden > notes and such, Is "from unmaintained import module" enough to tell you that the module is unmaintained? -- Steven
- Previous message (by thread): [Python-Dev] PEP 594 - a proposal for unmaintained modules
- Next message (by thread): [Python-Dev] PEP 594 - a proposal for unmaintained modules
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Python-Dev mailing list