Greetings, following is the weekly update for gpypi2 project. It's main purpose is to generate ebuilds from Python Package Index. Quick links to project info: Repository, issue tracker Hudson CI instance Sphinx documentation generated by hudson on each commit GPyPi knows about metadata.xml, ChangeLog and Manifest! Previous week (2nd - 9th August) Task: metadata, echangelog and manifest generation In the last week of implementing features I will add support for Gentoo developers workflow. Done. Implementation is in gpypi2/workflow.py. One issue though: echangelog has no idea how to add files to SCM, will have to find another abstraction tool for that.

Greetings, following is the weekly update for gpypi2 project. It's main purpose is to generate ebuilds from Python Package Index. Quick links to project info: Repository, issue tracker Hudson CI instance Sphinx documentation generated by hudson on each commit GPyPi now supports building ebuilds directly from Python packages. It's tied into distutils: python setup.py sdist_ebuild Configuration is not as verbose as through pypi, but that is a subject to change.

Greetings, following is the weekly update for gpypi2 project. It's main purpose is to generate ebuilds from Python Package Index. Quick links to project info: Repository, issue tracker Hudson CI instance Sphinx documentation generated by hudson on each commit Very successful 2 weeks. Two days of vacations and nice shiney configuration utility together with questionnaire. Previous 2 weeks (5th - 19th July) Task: Write configuration skeleton Currently, gpypi2 code only takes configuration from command line. I'd like to extend that to config file (.ini), get data directly from setup.py and interactive questionaire. In order for that to function properly, configuration needs to be done in right sequence. Following week I will write down the design and implement initial working prototype. Configuration dispatcher fully implemented! Also we have already working questionnaire functionality. Details can be found at http://docs.fubar.si/gpypi2/userguide.html#configuration

Thanks to http://xercestech.com/app-engine-server-monitor.geek Go to https://appengine.google.com/ and register application with {app-name} wget http://googleappengine.googlecode.com/files/google_appengine_1.3.5.zip unzip google_appengine_1.3.5.zip cd google_appengine git clone git://github.com/mrsteveman1/aeservmon.git {app-name} vim {app-name}/app.yaml # set application python appcfg.py update {app-name} Result: http://web-monitoring.appspot.com/

Packaging love-hate world in Python is with every Python developer. Each time you need something from setuptools/distribute/distutils you actually find something new, useful. Can not deny that. There are quite some people working hard on distutils2 to remove the "miserable" word from packaging. I'm really hoping that lack of communication with Python developers and Linux distribution will be fixed when people will not only care, but also give constructive thoughts how distutils could be improved (and thus make life easier even to Linux distributions).