This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author et
Recipients dstufft, eric.araujo, et
Date 2019-03-08.12:43:19
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1552048999.95.0.516949912161.issue36238@roundup.psfhosted.org>
In-reply-to
Content
distutils spits out a warning:

package init file 'xxx/__init__.py' not found (or not a regular file)

... when using Cythonized __init__.pyx instead. However, the installed package works absolutely fine, it can be imported & used perfectly, so this warning seems bogus.

I checked, and this warning is generated inside distutils/command/build_py.py in the build_py class in method check_package(). I suggest that this warning isn't generated in case a C extension is found for the __init__ module, checked in whatever way is appropriate at this stage (e.g. by seeing if there's an __init__.pyx)
History
Date User Action Args
2019-03-08 12:43:19etsetrecipients: + et, eric.araujo, dstufft
2019-03-08 12:43:19etsetmessageid: <1552048999.95.0.516949912161.issue36238@roundup.psfhosted.org>
2019-03-08 12:43:19etlinkissue36238 messages
2019-03-08 12:43:19etcreate