Given the growing complexity of many Python applications these days, developers often use other packages and libraries to help manage this complexity. TurboGears, for instance, will fetch several other packages from PyPi when it is installed and install these packages as well. PyPi provides access to packages that the Python community has provided, possibly because they feel it will be useful in a different context.
However, the PyPi code itself isn't exactly a simple Python package used to host egg files. It is a full-featured, hosted solution. The setuptools package can fetch eggs listed on a simple HTML page. In this case, you wouldn't even need anything other than Apache. However, what would be nice, is a middle-ground. A Python package that uses CherryPy or some other web framework to host the actual packages and provides a very simplistic management interface. I think something like this would be very valuable for packages that are limited by having to retrieving dependencies from PyPi and would need their own repository.
I'm not too sure how difficult this would actually by to implement, I'm only thinking of the need for such a solution at the moment. Perhaps I'll do some experimentation and write about what I find.
Showing posts with label pypi. Show all posts
Showing posts with label pypi. Show all posts
Friday, March 13, 2009
Thursday, July 31, 2008
The future of PYPI
I'm actually wondering what the future has in store for the Python Package Index. Can package developers really rely on PYPI for distributing their packages? What happens if PYPI goes away?
For the foreseeable future, I would say that PYPI is a dependable repository for Python package distribution. It is the standard method of installing Python packages and as long as it remains popular, I can't really see it going anywhere. Especially since this helps spread the usage of a growing language.
Another question is how will the Python Enterprise Application Toolkit evolve to incorporate new functionality such as checking for updates on PYPI for all my installed Python packages? If something like this is ever solidified, this will be a major popularity boost for Python.
For the foreseeable future, I would say that PYPI is a dependable repository for Python package distribution. It is the standard method of installing Python packages and as long as it remains popular, I can't really see it going anywhere. Especially since this helps spread the usage of a growing language.
Another question is how will the Python Enterprise Application Toolkit evolve to incorporate new functionality such as checking for updates on PYPI for all my installed Python packages? If something like this is ever solidified, this will be a major popularity boost for Python.
Subscribe to:
Posts
(
Atom
)