Message309040
| Author |
brgirgis |
| Recipients |
brgirgis, eric.araujo, ezio.melotti, michael.foord, r.david.murray, rbcollins |
| Date |
2017年12月25日.18:10:03 |
| SpamBayes Score |
-1.0 |
| Marked as misclassified |
Yes |
| Message-id |
<CAGCV+-m03h2V9N5MiW8yC5ktC_vCUqV0nRsYmRo=r0Wm1gBgzQ@mail.gmail.com> |
| In-reply-to |
<1514134385.74.0.912454111764.issue32419@psf.upfronthosting.co.za> |
| Content |
Hi Eric,
Yes it is like David said. For the projects you don't distribute the code
with the deployment package, you end up distributing only pyc files. As of
how to get these files, you can make use of py_compile or compileall
modules. For compileall, however, you have to pass the legacy flag to avoid
the __pycache__ standard.
What I found strange in the unittest code while trying to resolve this
issue is that, it is relying on hardcoded searches for __init__.py to find
if a module is loadable. I would have imagined that there is a standard why
to answer this question.
Best regards,
Bassem
Bassem Girgis, PhD
Email: brgirgis@gmail.com
On Sun, Dec 24, 2017 at 10:53 AM, Serhiy Storchaka <report@bugs.python.org>
wrote:
>
> Change by Serhiy Storchaka <storchaka+cpython@gmail.com>:
>
>
> ----------
> stage: -> test needed
>
> _______________________________________
> Python tracker <report@bugs.python.org>
> <https://bugs.python.org/issue32419>
> _______________________________________
> |
|