Make the NetIP Python library installable with PIP

[farhaven]

Currently, the Python NetIP library is just a module in a path "somewhere". Usually that path is ~/Engine/libraries/netip/python, but I think that is a bit brittle. This also makes it hard to reliably tell Python where it can find the library. The $PYTHONPATH hack we're using right now works for interactive shells but fails for example for things like Ansible-deployments.

Are there any reasons we shouldn't install the library with Pip?

[farhaven]

Edit: fp7-netide/IDE#7 could be solved really easily if we do this.

[doriguzzi]

Ok, good point. However, the current netip library should not be placed "somewhere" as you said, but it should be installed along with the Ryu framework as described in the ryu-backend and ryu-shim READMEs. That installation procedure avoids any problem with Ryu.

[schwabe]

Hm can't the netip python library be installed as separate library? There seem no reason for it to be installed in the ryu path.

[paaguti]

Good point. However, is it a real showstopper?

Brpa
El 07/10/2015 23:01, "Gregor Best" [email protected] escribió:

Currently, the Python NetIP library is just a module in a path
"somewhere". Usually that path is ~/Engine/libraries/netip/python, but I
think that is a bit brittle. This also makes it hard to reliably tell
Python where it can find the library. The $PYTHONPATH hack we're using
right now works for interactive shells but fails for example for things
like Ansible-deployments.

Are there any reasons we shouldn't install the library with Pip?

—
Reply to this email directly or view it on GitHub
#43.

[doriguzzi]

Again, when I am done with more urgent things, I will create this pip library. In the meantime, I don't think this is a real issue.
However, nothing prevent other people to create the library or explain me how to do that....

--rob