japronto: Installing fails on OSX

There is no requirements.txt and installation fails:

$ python3 setup.py install
Traceback (most recent call last):
  File "setup.py", line 10, in <module>
    import build
  File "/Users/r0fls/Documents/code/foss/japronto/build.py", line 11, in <module>
    import pytoml
ImportError: No module named 'pytoml'

Installing this way should install the dependencies.

About this issue

Original URL
State: closed
Created 7 years ago
Comments: 32 (16 by maintainers)

Most upvoted comments

I hate python packaging with passion. I am gonna change that to statically link picohttpparser with cextensions.

squeaky-pl on Feb 2, 2017

@r0fls, you need to copy src/picohttpparser/libpicohttpparser.so to /usr/local/lib

solie on Feb 2, 2017

0.1.1 is out, closing this.

squeaky-pl on Feb 9, 2017

Works perfectly.

On 8 Feb 2017, 5:27 PM +0530, maz_solie notifications@github.com, wrote:

Yup, working good!

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub (https://github.com/squeaky-pl/japronto/issues/1#issuecomment-278308670), or mute the thread (https://github.com/notifications/unsubscribe-auth/AKL6ARYK4ET7qzrDQCke4-FVDgAJ9qmAks5raa2XgaJpZM4LzBo0).

ojss on Feb 8, 2017

Yup, working good!

solie on Feb 8, 2017

Works! Well played 😄

aphillipo on Feb 8, 2017

Okay so;

pip3 install git+git://github.com/squeaky-pl/japronto.git@master

Works flawlessly for me! Thanks!

aphillipo on Feb 7, 2017

Please wait for 0.1.1 wheels. When I’m done with wheels I am gonna ping you back to test if the wheels are installable and work and then let’s do the 0.1.1 release.

squeaky-pl on Feb 7, 2017

Yup, all is good now!

solie on Feb 7, 2017

@solie can you pull again and retry to confirm it doesnt fail with clang

squeaky-pl on Feb 7, 2017

Here it is:

python3 -c 'from distutils.ccompiler import new_compiler; from distutils.sysconfig import customize_compiler; c = new_compiler(); customize_compiler(c); print(c.compiler_so)' ['clang', '-Wno-unused-result', '-Wsign-compare', '-Wunreachable-code', '-fno-common', '-dynamic', '-DNDEBUG', '-g', '-fwrapv', '-O3', '-Wall', '-Wstrict-prototypes']

solie on Feb 7, 2017

Confirmed its working for me!

On 7 Feb 2017, 4:35 PM +0530, Paweł Piotr Przeradowski notifications@github.com, wrote:

@r0fls @solie @henry0312 Can you try when you have a moment? — You are receiving this because you commented. Reply to this email directly, view it on GitHub, or mute the thread.

ojss on Feb 7, 2017

Hi OSX users, I made a branch where I try to address build problems. Can somebody with a Mac check it out?

git clone https://github.com/squeaky-pl/japronto
cd japronto
git checkout build-uplist
python setup.py bdist_wheel

The related PR is here: https://github.com/squeaky-pl/japronto/pull/37/files

Thanks

squeaky-pl on Feb 7, 2017

I guess I just have messed up some python env before, so I fixed my env and rerun the python3 setup.py bdist_wheel, found out that just commenting out the strip line is enough, so no need to change the build.py and setup.py. I don’t even need to use CFLAGS.

solie on Feb 1, 2017

@r0fls can you try commenting out strip line since it shouldn’t be too important really, like @solie did. I am gonna fix this mess today.

squeaky-pl on Feb 1, 2017

I pushed a dirty fix on master. The whole build system needs serious refactoring though.

You can now try compiling with clang, I don’t know much about clang and OSX but if it complains about C99 you need to invoke it like CFLAGS="-std=c99" python setup.py bdist_wheel at least under older GCC. Let me know how it goes.

squeaky-pl on Jan 31, 2017