-
-
Notifications
You must be signed in to change notification settings - Fork 239
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
Shared lib builder drops package directory #169
Labels
bug
Something isn't working
Comments
Open
At least one of the problem is they both have symbols |
jayvdb
added a commit
to jayvdb/PyOxidizer
that referenced
this issue
Nov 8, 2019
Built extensions in packages often have common names like speedups, utils, _objects, cpython, etc. which reside inside the package namespace. The compiled extensions each have a PyInit_<module> which needs to be renamed to PyInit_<pkg>_<module> to avoid clashes when combined into a static binary. Fixes indygreg#169
jayvdb
added a commit
to jayvdb/PyOxidizer
that referenced
this issue
Nov 8, 2019
Built extensions in packages often have common names like speedups, utils, _objects, cpython, etc. which reside inside the package namespace. The compiled extensions each have a PyInit_<module> which needs to be renamed to PyInit_<pkg>_<module> to avoid clashes when combined into a static binary. Fixes indygreg#169
jayvdb
added a commit
to jayvdb/PyOxidizer
that referenced
this issue
Nov 9, 2019
Built extensions in packages often have common names like speedups, utils, _objects, cpython, etc. which reside inside the package namespace. The compiled extensions each have a PyInit_<module> which needs to be renamed to PyInit_<pkg>_<module> to avoid clashes when combined into a static binary. Fixes indygreg#169
jayvdb
added a commit
to jayvdb/PyOxidizer
that referenced
this issue
Nov 11, 2019
Built extensions in packages often have common names like speedups, utils, _objects, cpython, etc. which reside inside the package namespace. The compiled extensions each have a PyInit_<module> which needs to be renamed to PyInit_<pkg>_<module> to avoid clashes when combined into a static binary. Fixes indygreg#169
jayvdb
added a commit
to jayvdb/PyOxidizer
that referenced
this issue
Nov 14, 2019
Built extensions in packages often have common names like speedups, utils, _objects, cpython, etc. which reside inside the package namespace. The compiled extensions each have a PyInit_<module> which needs to be renamed to PyInit_<pkg>_<module> to avoid clashes when combined into a static binary. Fixes indygreg#169
jayvdb
added a commit
to jayvdb/PyOxidizer
that referenced
this issue
Nov 15, 2019
Built extensions in packages often have common names like speedups, utils, _objects, cpython, etc. which reside inside the package namespace. The compiled extensions each have a PyInit_<module> which needs to be renamed to PyInit_<pkg>_<module> to avoid clashes when combined into a static binary. Fixes indygreg#169
jayvdb
added a commit
to jayvdb/PyOxidizer
that referenced
this issue
Nov 15, 2019
Built extensions in packages often have common names like speedups, utils, _objects, cpython, etc. which reside inside the package namespace. The compiled extensions each have a PyInit_<module> which needs to be renamed to PyInit_<pkg>_<module> to avoid clashes when combined into a static binary. Fixes indygreg#169
jayvdb
added a commit
to jayvdb/PyOxidizer
that referenced
this issue
Nov 16, 2019
Built extensions in packages often have common names like speedups, utils, _objects, cpython, etc. which reside inside the package namespace. The compiled extensions each have a PyInit_<module> which needs to be renamed to PyInit_<pkg>_<module> to avoid clashes when combined into a static binary. Fixes indygreg#169
jayvdb
added a commit
to jayvdb/PyOxidizer
that referenced
this issue
Nov 19, 2019
Built extensions in packages often have common names like speedups, utils, _objects, cpython, etc. which reside inside the package namespace. The compiled extensions each have a PyInit_<module> which needs to be renamed to PyInit_<pkg>_<module> to avoid clashes when combined into a static binary. Fixes indygreg#169
jayvdb
added a commit
to jayvdb/PyOxidizer
that referenced
this issue
Nov 19, 2019
Built extensions in packages often have common names like speedups, utils, _objects, cpython, etc. which reside inside the package namespace. The compiled extensions each have a PyInit_<module> which needs to be renamed to PyInit_<pkg>_<module> to avoid clashes when combined into a static binary. Fixes indygreg#169
jayvdb
added a commit
to jayvdb/PyOxidizer
that referenced
this issue
Nov 19, 2019
Built extensions in packages often have common names like speedups, utils, _objects, cpython, etc. which reside inside the package namespace. The compiled extensions each have a PyInit_<module> which needs to be renamed to PyInit_<pkg>_<module> to avoid clashes when combined into a static binary. Fixes indygreg#169
jayvdb
added a commit
to jayvdb/PyOxidizer
that referenced
this issue
Nov 19, 2019
Built extensions in packages often have common names like speedups, utils, _objects, cpython, etc. which reside inside the package namespace. The compiled extensions each have a PyInit_<module> which needs to be renamed to PyInit_<pkg>_<module> to avoid clashes when combined into a static binary. Fixes indygreg#169
jayvdb
added a commit
to jayvdb/PyOxidizer
that referenced
this issue
Nov 22, 2019
This causes the .obj files to be unparsable by editbin, dumpbin, nm, objcopy, goblin and object. Related to indygreg#169
jayvdb
added a commit
to jayvdb/PyOxidizer
that referenced
this issue
Nov 22, 2019
Built extensions in packages often have common names like speedups, utils, _objects, cpython, etc. which reside inside the package namespace. The compiled extensions each have a PyInit_<module> which needs to be renamed to PyInit_<pkg>_<module> to avoid clashes when combined into a static binary. Fixes indygreg#169
jayvdb
added a commit
to jayvdb/PyOxidizer
that referenced
this issue
Nov 22, 2019
Built extensions in packages often have common names like speedups, utils, _objects, cpython, etc. which reside inside the package namespace. The compiled extensions each have a PyInit_<module> which needs to be renamed to PyInit_<pkg>_<module> to avoid clashes when combined into a static binary. Fixes indygreg#169
jayvdb
added a commit
to jayvdb/PyOxidizer
that referenced
this issue
Nov 26, 2019
This causes the .obj files to be unparsable by editbin, dumpbin, nm, objcopy, goblin and object. Related to indygreg#169
jayvdb
added a commit
to jayvdb/PyOxidizer
that referenced
this issue
Nov 26, 2019
Built extensions in packages often have common names like speedups, utils, _objects, cpython, etc. which reside inside the package namespace. The compiled extensions each have a PyInit_<module> which needs to be renamed to PyInit_<pkg>_<module> to avoid clashes when combined into a static binary. Fixes indygreg#169
jayvdb
added a commit
to jayvdb/PyOxidizer
that referenced
this issue
Nov 29, 2019
This causes the .obj files to be unparsable by editbin, dumpbin, nm, objcopy, goblin and object. Related to indygreg#169
jayvdb
added a commit
to jayvdb/PyOxidizer
that referenced
this issue
Nov 29, 2019
Built extensions in packages often have common names like speedups, utils, _objects, cpython, etc. which reside inside the package namespace. The compiled extensions each have a PyInit_<module> which needs to be renamed to PyInit_<pkg>_<module> to avoid clashes when combined into a static binary. Fixes indygreg#169
jayvdb
added a commit
to jayvdb/PyOxidizer
that referenced
this issue
Nov 30, 2019
Built extensions in packages often have common names like speedups, utils, _objects, cpython, etc. which reside inside the package namespace. The compiled extensions each have a PyInit_<module> which needs to be renamed to PyInit_<pkg>_<module> to avoid clashes when combined into a static binary. Fixes indygreg#169
jayvdb
added a commit
to jayvdb/PyOxidizer
that referenced
this issue
Dec 23, 2019
Built extensions in packages often have common names like speedups, utils, _objects, cpython, etc. which reside inside the package namespace. The compiled extensions each have a PyInit_<module> which needs to be renamed to PyInit_<pkg>_<module> to avoid clashes when combined into a static binary. Fixes indygreg#169
jayvdb
added a commit
to jayvdb/PyOxidizer
that referenced
this issue
Dec 23, 2019
This causes the .obj files to be unparsable by editbin, dumpbin, nm, objcopy, goblin and object. Related to indygreg#169
jayvdb
added a commit
to jayvdb/PyOxidizer
that referenced
this issue
Dec 23, 2019
Built extensions in packages often have common names like speedups, utils, _objects, cpython, etc. which reside inside the package namespace. The compiled extensions each have a PyInit_<module> which needs to be renamed to PyInit_<pkg>_<module> to avoid clashes when combined into a static binary. Fixes indygreg#169
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Shared libs that are in packages that also contain python code are stored in
site-packages/foo/bar.so
PyOxidizer is dropping the
foo
package name, creating conflicts.A very prominent example is
markupsafe
,simplejson
andlogbook
all have a_speedups.so
tornado
andwebsockets
andfastparquet
all have aspeedups.so
cytoolz
andh5py
andespressomd
all haveutils.so
, and further nested arezmq/backend/cython/utils.so
andyt/analysis_modules/photon_simulator/utils.so
dulwich
andh5py
have_objects.so
xxhash
andlmdb
havecpython.so
bsdiff4
andespeak
havecore.so
astropy
andsunpy
have_compiler.so
gevent
andkivy
both have_event.so
PyQt4 and PyQt5 have an almost identical set of built modules under their respective directories.
Cryptodome and Crypto also share a set of similar names.
Third level objects
sklearn/manifold/_utils.so
andsklearn/tree/_utils.so
probably also have this problem, breaking sklearn even if only it is installed.Third level objects
gssapi/raw/misc.so
andsamba/dcerpc/misc.so
likely also conflict.Third level
astropy/stats/_stats.so
andscipy/stats/_stats.so
As noted at #167 , brotli and brotlipy both expect
from brotli import _brotli
to import their .so , but that example is a bit messy as the two libraries conflict anyway.And that is just what I can find in my site-packages :P Obviously there will be many more conflicts I am unaware of.
The text was updated successfully, but these errors were encountered: