Wednesday, September 12, 2012

Presenting ... the inupypi server

After using the pypiserver: http://pypi.python.org/pypi/pypiserver/ for sometime to house our internal eggs and libraries, we (one of my colleagues at least, very very quietly I might add) decided add to give back to the Python community by developing our own pypiserver called InuPyPi: http://pypi.python.org/pypi/inupypi/0.2.3 which is based on Flask. Some of the features of our pypi server are:


  • A nice(r) web interface for packages.
  • Supports multiple eggbasket folder per server.
  • Auto searching for updates of packages (planned)
  • One click update for outdated packages (planned)
  • Command-line tool to upload to server something like 'python setup.py upload' (planned. This will be pretty close to doing)
For those who are interested to contribute the project, the project lives in github: https://github.com/hallaj/inupypi. We will appreciate suggestions and help with our pypi server. 

2 comments:

fruch said...

But why anther pypi implementation? Just for the web interface ? Who uses them any how.

Sorry for flambitting, but I was looking for pypi server implementation last week, and found too many of them.

I really liked pypiserver cause it was sample and had this one file implementation (first time I've seen this weird/unique way of distributing python package)

lowks said...

We use them for our private egg basket repo. We liked pypiserver too but we wanted to do certain things our way and we did not see eye to eye regarding how to implement them.