We Keep Coding

pypy5.6 install confluent_kafka cause: undefined symbol PyUnicode_FromFormat Error

When install confluent_kafka on pypy5.6, its has an error of : undefined symbol PyUnicode_FromFormat Error, i dont know how its happend ？
the os is: CentOs5.6
the full error output is :
Python 2.7.12 (aff251e543859ce4508159dd9f1a82a2f553de00, Nov 12 2016, 08:50:18)
[PyPy 5.6.0 with GCC 6.2.0] on linux2
Type "help", "copyright", "credits" or "license" for more information.
import confluent_kafka
Traceback (most recent call last):
File "", line 1, in
File "/usr/local/pypy/site-packages/confluent_kafka/init.py", line 2, in
from .cimpl import *
ImportError: unable to load extension module '/usr/local/pypy/site-packages/confluent_kafka/cimpl.pypy-41.so': /usr/local/pypy/site-packages/confluent_kafka/cimpl.pypy-41.so: undefined symbol: PyUnicode_FromFormat
How can I resolve this issue?

PyUnicode_FromFormat is not implemented so far inside PyPy. We'll get to it at some point (maybe soon if you have an example that requires it). You can also contribute it directly, if you want to get involved.
FWIW it is implemented in the py3.5 branch implementing Python 3.5, but not in trunk (supporting Python 2.7). Trunk only implements PyString_FromFormat. It's mostly a matter of back-porting the implementation, and "downgrading" the C code: in py3.5 it comes from CPython 3.5, so for trunk we'd need the same C code from CPython 2.7 instead.

Problems in pexpect (python3.3)

Running 3.3 python on CentOS 7.
Tryin' to write simple script but can't get pexpect module to work as I want
if I use interpreter python 3.3, I can write this commands correctly
[root#localhost expect]# python3.3
Python 3.3.3 (default, Apr 7 2015, 02:31:24)
[GCC 4.8.3 20140911 (Red Hat 4.8.3-9)] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> import pexpect
>>> child = pexpect.spawn('telnet 10.1.1.1')
but If I run file pexpect.py with exactly same commands, I get
[root#localhost expect]# python3.3 /usr/etc/pexpect.py
Traceback (most recent call last):
File "/usr/etc/pexpect.py", line 1, in <module>
import pexpect
File "/usr/etc/pexpect.py", line 3, in <module>
child = pexpect.spawn('telnet 10.1.1.1');
AttributeError: 'module' object has no attribute 'spawn'
I found some similar info in the google, advice was to move .py file to another folder.
It didn't work for me.
Another advice was to delete " pycache" folder (I've got same in my pexpect.py location), but it didn't work aswell. Errors are still the same, this folder are still created after running the script (trying, I mean).
Any ideas?

You have called your file pexpect.py. You need to rename it to something else as you are importing from your file not the pexpect module. You also need to delete any .pyc in the same folder. It does not matter where you move your script, the current folder is still going to be in the path before where the actual pexpect module is.

Python3 on Ubuntu giving errors on help() command

I used help() in the python3 shell on Ubuntu 14.04
I got this output
Please help , don't know whats wrong.
Python 3.4.0 (default, Apr 11 2014, 13:05:11)
[GCC 4.8.2] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> help()
Traceback (most recent call last):
File "<stdin>", line 1, in <module>
File "/usr/lib/python3.4/_sitebuiltins.py", line 98, in __call__
import pydoc
File "/usr/lib/python3.4/pydoc.py", line 65, in <module>
import platform
File "/home/omega/platform.py", line 2, in <module>
print("System : ",platform.uname().system)
AttributeError: 'module' object has no attribute 'uname'
>>>

The problem is that platform is the name of a stdlib module, which help uses. By creating a module of your own with the same name that occurs before the stdlib in your sys.path, you're preventing Python from using the standard one.
The fact that your own platform module tries to use the stdlib module of the same name just compounds the problem. That isn't going to work; your import platform inside that module is just importing itself.
The solution is to not collide names like this. Look at the list of the standard modules, and don't create anything with the same name as any of them if you want to use features from that module, directly or indirectly.
In other words: Rename your platform.py to something else, or put it inside a package.

File "/home/omega/platform.py", line 2, in <module>
print("System : ",platform.uname().system)
This is the problem, go to platform.py and fix it, it will be ok. It says, platform has not any method called uname you probably misstyped.

Error when using musixmatch python wrapper

I have been trying to use the the musixmatch python wrapper but I am getting a strange error when trying to run the example. Can anybody tell me what should be done to fix the library?
$ python
Python 2.6.6 (r266:84292, Dec 26 2010, 22:31:48)
[GCC 4.4.5] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>> import musixmatch.ws
Traceback (most recent call last):
File "<stdin>", line 1, in <module>
File "musixmatch/ws.py", line 14, in <module>
import musixmatch.api
File "musixmatch/api.py", line 167, in <module>
class XMLResponseMessage(ResponseMessage, etree.ElementTree):
TypeError: Error when calling the metaclass bases
metaclass conflict: the metaclass of a derived class must be a (non-strict) subclass of the metaclasses of all its bases

As explained by #jdi in this question, it is a metaclass confict : Python does not know from which class to derive XMLResponseMessage from. ( it can't be from both due two possible diamond inheritance)
There is an Active State Recipe which solves this problem automatically (noconflict module): http://code.activestate.com/recipes/204197-solving-the-metaclass-conflict/ . The drawback is that you have to dive into the lib code and modify it to resolve the conflict.
From what I've seen, this lib was tailored for the developper purpose, and can only be run with his environment : neither python 2.7 (metaclass clash) nor python 3.3 ( unable to install the egg module) are able to install and test the module. I would advise you to fork the code, and adapt it to your needs.

"from _json import..." - python

I am inspecting the JSON module of python 3.1, and am currently in /Lib/json/scanner.py. At the top of the file is the following line:
from _json import make_scanner as c_make_scanner
There are five .py files in the module's directory: __init__ (two leading and trailing underscores, it's formatting as bold), decoder, encoder, scanner and tool. There is no file called "json".
My question is: when doing the import, where exactly is "make_scanner" coming from?
Yes, I am very new to Python!

It's coming from a C-compiled _json.pyd (or _json.so, etc, etc, depending on the platform) that lives elsewhere on the sys.path. You can always find out where that is in your specific Python installation by importing the module yourself and looking at its __file__, e.g.:
>>> import _json
>>> _json.__file__
'/Library/Frameworks/Python.framework/Versions/2.6/lib/python2.6/lib-dynload/_json.so'
As you see, in my installation of Python 2.6, _json comes from the lib-dynload subdirectory of lib/python2.6, and the extension used on this platform is .so.

It may be coming from a file, or it may be built-in. On Windows, it appears to be built-in.
Python 3.1.2 (r312:79149, Mar 21 2010, 00:41:52) [MSC v.1500 32 bit (Intel)] on win32
Type "help", "copyright", "credits" or "license" for more information.
>>> import _json
>>> _json.__file__
Traceback (most recent call last):
File "<stdin>", line 1, in <module>
AttributeError: 'module' object has no attribute '__file__'
and there is no _json.pyd or _json.dll in the offing.
If you want to see the source, having a binary file on your machine or not is irrelevant -- you'll need the SVN browser.