On 09/06/2016 06:46 PM, Neal Gompa wrote:
On Tue, Sep 6, 2016 at 12:41 PM, Tomas Orsava
<torsava(a)redhat.com> wrote:
> Hi!
>
> I'm currently writing a PEP titled "Distributing a Subset of the Standard
> Library" to standardize and hopefully improve the behavior of Python without
> the its full standard library. This is relevant to Fedora, as we exclude
> several standard library modules into separate optional packages (e.g.
> python3-tkinter).
>
> I have a draft of the first two sections: Motivation and Specification.
>
https://fedora-python.github.io/pep-drafts/pep-A.html
>
> The source can be found here:
https://github.com/fedora-python/pep-drafts
Why doesn't Python offer dist data indicating the modules that are
included in the standard library? That way there doesn't need to be
much special handling to support whether it's an external package or a
standard library module. Things like dependency generators can pick
this up properly.
Python does not have dependency generators. Dependendency information is
added to "setup.py" files, manually.
Even if you got Python to start providing dist data for stdlib packages,
you would still need to convince the developers of all Python modules to
use that info in their packages.
The discussion linked in the PEP draft contains lots of info about the
status quo and opinions of Python core developers.
--
Petr Viktorin