python-cffi broken
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
PLD Linux |
New
|
Undecided
|
Unassigned |
Bug Description
seems python-cffi is very broken, __pycache__ is imho python3 specific way of storing .pyc/.pyo
version: python-
$ winswitch_applet
** (process:19871): WARNING **: Trying to register gtype 'GMountMountFlags' as enum when in fact it is of type 'GFlags'
** (process:19871): WARNING **: Trying to register gtype 'GDriveStartFlags' as enum when in fact it is of type 'GFlags'
** (process:19871): WARNING **: Trying to register gtype 'GSocketMsgFlags' as enum when in fact it is of type 'GFlags'
[II] 2014/22/04 13:52:10.954517 applet.<module>() python version 2.7.6 (default, Feb 21 2014, 20:00:27) \n[GCC 4.8.2 20140221 (release)]
[II] 2014/22/04 13:52:10.954636 applet.<module>() gtk version (2, 24, 22), pygtk version (2, 24, 0)
[DD] 2014/22/04 13:52:10.969388 main_loop.
Traceback (most recent call last):
File "/usr/bin/
applet_
File "/usr/share/
File "/usr/share/
File "/usr/share/
File "/usr/lib64/
from twisted.internet import _glibbase
File "/usr/lib64/
from twisted.internet import base, posixbase, selectreactor
File "/usr/lib64/
from twisted.internet import error, udp, tcp
File "/usr/lib64/
from twisted.
File "/usr/lib64/
from twisted.
File "/usr/lib64/
from OpenSSL.SSL import Error, ZeroReturnError, WantReadError
File "/usr/share/
File "/usr/share/
File "/usr/share/
File "/usr/lib64/
File "/usr/lib64/
File "/usr/lib64/
File "/usr/lib64/
File "/usr/lib64/
File "/usr/lib64/
IOError: [Errno 2] No such file or directory: '/usr/lib64/
`__pycache__` usage is not limited to Python3 `*.py` files. That directory is used by 'compiled' code of python modules, but is a good place for other similar artifacts. It seems like a great choice for files 'compiled' by cffi – this way multiple Python interpreter versions can use python modules from the same directory. And the system 'site-packages' is not the only place where python modules may be stored.
The problem here is, that there are no cffi-compiled files included for the 'cryptography. hazmat. bindings' module and cffi tries to compile them on runtime. It is good it failed – so we can see the packaging problem.
The 'compiled' extension modules should be included in the 'cryptography. hazmat. bindings' and, maybe, the 'cryptography. hazmat. bindings' should be modified not to try to recompile that.
Here are some hints: /cffi.readthedo cs.org/ en/release- 0.8/#distributi ng-modules- using-cffi
https:/