[Chicago] Question about Packaging

Samir Faci samir at esamir.com
Fri Feb 9 14:39:54 EST 2018


I have an python app that I'm trying to package up as an egg? wheel? or
whatever it is that we are supposed to use.

I currently have an egg but I think i'm doing something wrong since the
location of the files keeps on changing.

I'm running on an old centos that's locked to python 2.6.

When I install my egg, i creates a folder under:

/usr/lib/python2.6/site-packages/

titled:  mii_monitoring-1.0.27-py2.6.egg/

Every other egg I see installed looks like different.

it seems to create

packageName
packageName-version-py2.6.egg-info   or packageName-version.dist-info

Two questions.

1.  Should be looking at wheels instead of eggs? I'm mainly using eggs to
deploy the python files in a location so I can reference them in a crontab
to be executed.

2.  Is there something i'm doing wrong or a guide I should be looking at.
It seems odd that my package isn't versioned or installed like every other
package I see on the system.


Snippet

[root tmp]# easy_install ./mii_monitoring-1.0.29-py2.7.egg
Processing mii_monitoring-1.0.29-py2.7.egg
creating /usr/lib/python2.6/site-packages/mii_monitoring-1.0.29-py2.7.egg
Extracting mii_monitoring-1.0.29-py2.7.egg to /usr/lib/python2.6/site-packages
Removing mii-monitoring 1.0.27 from easy-install.pth file
Adding mii-monitoring 1.0.29 to easy-install.pth file

Installed /usr/lib/python2.6/site-packages/mii_monitoring-1.0.29-py2.7.egg

​



-- 
Thank you
Samir Faci
https://keybase.io/csgeek
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/chicago/attachments/20180209/516dd48a/attachment.html>


More information about the Chicago mailing list