FS#56487 - [python2-pyglet] dependency to python2-future
Attached to Project:
Community Packages
Opened by Michel (xantares) - Monday, 27 November 2017, 20:30 GMT
Last edited by Eli Schwartz (eschwartz) - Friday, 09 March 2018, 06:18 GMT
Opened by Michel (xantares) - Monday, 27 November 2017, 20:30 GMT
Last edited by Eli Schwartz (eschwartz) - Friday, 09 March 2018, 06:18 GMT
|
Details
python2-pyglet bundles a future module, but hacks the
sys.path to get it done
this crashes brainworkshop who's relying on the proper definition of sys.path (see code below) by simply depending on python2-future we avoid this hackish behavior the python3 package does not have this problem as future is a native module # Check if future is installed, if not use included batteries try: import future except ImportError: import os.path as op import sys future_base = op.abspath(op.join(op.dirname(__file__), 'extlibs', 'future')) sys.path.insert(0, op.join(future_base, 'py2_3')) if sys.version_info[:2] < (3, 0): sys.path.insert(0, op.join(future_base, 'py2')) del future_base del sys del op try: import future except ImportError: print('Failed to get python-future') raise |
This task depends upon
Closed by Eli Schwartz (eschwartz)
Friday, 09 March 2018, 06:18 GMT
Reason for closing: Fixed
Additional comments about closing: pyglet 1.3.1-1
Friday, 09 March 2018, 06:18 GMT
Reason for closing: Fixed
Additional comments about closing: pyglet 1.3.1-1
This package doesn't import concurrent.futures
Also python-pyglet seems to need python-future too.
And it is probably an upstream issue, not a packaging issue at that.
FYI, Debian seems to require future too:
https://anonscm.debian.org/cgit/python-modules/packages/pyglet.git/commit/?id=407dc016ebbc6257e89945e1c6a172fa274c3baf
I would actually suggest stripping out the vendored copies in addition to merely adding the dependency.