-
Notifications
You must be signed in to change notification settings - Fork 515
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
RuntimeError: original source dist cannot contain .pyc files #137
Comments
I cannot find any explicit reason for the .pyc being included, but maybe the problem is the use of Can you try editing your https://github.com/rochacbruno/flasgger/blob/master/MANIFEST.in#L2 remove that line and try again. We may need to include all static files include one by one or use specific wildcard to get them instead of |
@rochacbruno thank you for a response.
Have cloned flasgger, modified the MANIFEST.in as you suggested and ran my build script. This time it would build all dependency-modules: In the end it failed for the same reason. By the way, reverting MINIFEST.in back didn't affect anything. So looks like, unfortunately, it is not the case. |
The # find /tmp/ -type f -name '*.pyc'
pip2deb_flasgger==0.6.6_2Kpip0/ tmpFXJFhK/
root@2ea58c377e15:/shared# find /tmp/pip2deb_flasgger\=\=0.6.6_2Kpip0/ -type f -name '*.pyc'
/tmp/pip2deb_flasgger==0.6.6_2Kpip0/flasgger-0.6.6/tmp_sdist_dsc/flasgger-0.6.6/flasgger/__pycache__/utils.cpython-36.pyc
/tmp/pip2deb_flasgger==0.6.6_2Kpip0/flasgger-0.6.6/tmp_sdist_dsc/flasgger-0.6.6/flasgger/__pycache__/marshmallow_apispec.cpython-36.pyc
/tmp/pip2deb_flasgger==0.6.6_2Kpip0/flasgger-0.6.6/tmp_sdist_dsc/flasgger-0.6.6/flasgger/__pycache__/__init__.cpython-36.pyc
/tmp/pip2deb_flasgger==0.6.6_2Kpip0/flasgger-0.6.6/tmp_sdist_dsc/flasgger-0.6.6/flasgger/__pycache__/constants.cpython-36.pyc/tmp/pip2deb_flasgger==0.6.6_2Kpip0/flasgger-0.6.6/tmp_sdist_dsc/flasgger-0.6.6/flasgger/__pycache__/base.cpython-36.pyc
/tmp/pip2deb_flasgger==0.6.6_2Kpip0/flasgger-0.6.6/flasgger-0.6.6/flasgger/__pycache__/utils.cpython-36.pyc
/tmp/pip2deb_flasgger==0.6.6_2Kpip0/flasgger-0.6.6/flasgger-0.6.6/flasgger/__pycache__/marshmallow_apispec.cpython-36.pyc
/tmp/pip2deb_flasgger==0.6.6_2Kpip0/flasgger-0.6.6/flasgger-0.6.6/flasgger/__pycache__/__init__.cpython-36.pyc
/tmp/pip2deb_flasgger==0.6.6_2Kpip0/flasgger-0.6.6/flasgger-0.6.6/flasgger/__pycache__/constants.cpython-36.pyc
/tmp/pip2deb_flasgger==0.6.6_2Kpip0/flasgger-0.6.6/flasgger-0.6.6/flasgger/__pycache__/base.cpython-36.pyc
/tmp/pip2deb_flasgger==0.6.6_2Kpip0/flasgger-0.6.6/tmp_py2dsc/flasgger-0.6.6/flasgger/__pycache__/utils.cpython-36.pyc
/tmp/pip2deb_flasgger==0.6.6_2Kpip0/flasgger-0.6.6/tmp_py2dsc/flasgger-0.6.6/flasgger/__pycache__/marshmallow_apispec.cpython-36.pyc
/tmp/pip2deb_flasgger==0.6.6_2Kpip0/flasgger-0.6.6/tmp_py2dsc/flasgger-0.6.6/flasgger/__pycache__/__init__.cpython-36.pyc
/tmp/pip2deb_flasgger==0.6.6_2Kpip0/flasgger-0.6.6/tmp_py2dsc/flasgger-0.6.6/flasgger/__pycache__/constants.cpython-36.pyc
/tmp/pip2deb_flasgger==0.6.6_2Kpip0/flasgger-0.6.6/tmp_py2dsc/flasgger-0.6.6/flasgger/__pycache__/base.cpython-36.pyc |
They don't get included if I use the git URL in But of course it would be nice to be able to download these as a normal pip package as well. |
looks like |
And the problem must be the https://github.com/rochacbruno/flasgger/blob/master/MANIFEST.in |
https://docs.python.org/2/distutils/sourcedist.html#commands Maybe this can be used in the MANIFEST file:
something like (if I understand it correctly):
|
Excluded __pycache__ and *.py[co] from dist. Fixed #137.
Trying to convert PIP packages into Debian packages using python-stdeb (for maintainability purposes). Having scripts and mechanism to do it, which works perfectly fine. It converts any PIP package into debian except for
flasgger
version 0.6.0+ (so 0.5.14 and every version below getting converted just fine):Again this happens only of Flasgger version >= 0.6.0.
Was something changed severely between 0.5.14 and 0.6.0 that could cause the problem with PYC files?
The text was updated successfully, but these errors were encountered: