A RetroSearch Logo

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Search Query:

Showing content from https://mail.python.org/pipermail/python-dev/2017-November/150536.html below:

[Python-Dev] PEP 561 rework

[Python-Dev] PEP 561 rework [Python-Dev] PEP 561 reworkSebastian Rittau srittau at rittau.biz
Tue Nov 14 04:02:07 EST 2017
Am 14.11.2017 um 02:38 schrieb Guido van Rossum:
> On Mon, Nov 13, 2017 at 3:50 PM, Sebastian Rittau <srittau at rittau.biz 
> <mailto:srittau at rittau.biz>> wrote:
>
>     I am really looking forward to the implementation of this PEP and
>     I am glad that it is close to acceptance. One thing that is not
>     really clear to me is how module-only packages are handled. Say I
>     have a package "foo" that installs the file "foo.py" to
>     site-packages, where would I install "foo.pyi" and py.typed to? Or
>     is this case not supported and I have to convert the foo module
>     into a package containing just __init__.py?
>
>
> Good call. I think that conversion to a package is indeed the best 
> approach -- it doesn't seem worth it to add more special-casing for 
> this scenario.
>
> Ethan, if you agree, you should just add a sentence about this to the PEP.
>
This seems like the best solution, especially since setuptools does not 
really support installing package data for pure modules.

  - Sebastian
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/python-dev/attachments/20171114/4f0c1f3b/attachment.html>
More information about the Python-Dev mailing list

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4