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
Task: sync command - populate overlay with successful ebuilds from pypi
When I will get bored or stuck with task #1, I'll start working on command that will generate ebuilds from all packages in pypi to an overlay.
Initial "sync" command is implemented. Still lacking proper error handling, metadata generation and manifest update support. Will be a lot easier to implement with current configuration management.
Additional, following mini-tasks were performed:
- fixed echo command to work properly
- correct handling of whitespace in rendered ebuilds
- replace 4 spaces with a tab in rendered ebuilds
Upcoming week (20th - 26th July)
Task: fix TODOs in the code
Code currently has about `60 TODOs <http://hudson.fubar.si/job/g-pypi2/portage=portage2.1,python=2.6/58/tasksResult/?>`_ that need to be address for a better codebase.
Task: Implement "python setup.py bdist_ebuild" command
I'll peek into distutils heart and implement most basic bdist command to output an ebuild. I will basically the same stuff we currently do, except it will parse data from setup.py itself and not through pypi.
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
- wiki/user stories for scrum development
Last two weeks were crazy at university. Now I shall have time to work on gpypi2 full-time until the end of program.
Install gpypi2
$ sudo pip install http://bitbucket.org/iElectric/g-pypi2/get/tip.zip
or
$ sudo easy_install http://bitbucket.org/iElectric/g-pypi2/get/tip.zip
Create an ebuild
$ sudo gpypi2 create flask
* Generating ebuild: Flask 0.4
* Your ebuild is here: /usr/local/portage/dev-python/flask/flask-0.4.ebuild
* Dependency needed: Werkzeug
* Dependency needed: Jinja2
* Generating ebuild: Werkzeug 0.6.2
* Your ebuild is here: /usr/local/portage/dev-python/werkzeug/werkzeug-0.6.2.ebuild
* Generating ebuild: Jinja2 2.5
* Your ebuild is here: /usr/local/portage/dev-python/jinja2/jinja2-2.5.ebuild
* Dependency needed: Babel
* Generating ebuild: Babel 0.9.5
* Your ebuild is here: /usr/local/portage/dev-python/babel/babel-0.9.5.ebuild
NOTE: ebuilds will probably not function yet, features are yet to be completed/added. Report bugs to `issue tracker <http://bitbucket.org/iElectric/g-pypi2/issues?status=new&status=open>`_.
Previous week (21st June - 5th July)
Task: Use SrcUriNamer
gpypi2.enamer.SrcUriNamer is awaiting for quite 2 weeks now to be finally used. It's basically factory that generates SRC_URI and HOMEPAGE according to mirror provider. A lot of additional refactoring will be needed to Enamer to use this utility instead of current guessing/parsing.
Not done. With Jesus we decided to postpone this for one of the last tasks, since it's not that big benefit to gpypi2 and there are more important details to be implemented. It's also a big blocker for good unittest coverage, but that shall be sorted out.
Task: Fix bugs reported by users
Lot of bugs are going to pop up; fix bugs, write tests and add documentation.
None reported :(
Task: Increase test coverage
I'm still not satisfied with test coverage. I'll try to increase it a bit more. It's 10 days week of exams on my university, soon I will be able to put in more effort in implementing features.
Unittest coverage is about 75%. Won't get further than that until SrcUriNamer is properly implemented and tested. Few additional tests can be made at PortageUtils, but that's a minor issue. Here is a rundown of additional changes to code:
- slight improvements to documentation
- option to choose PyPi base URL
- changed behaviour to use XML-RPC and SETUPTOOLS/SIMPLEPAGE method for retrieving SRC_URI
- updated licences dictionary mapping
- fixed echo command to work properly (without cleanup atm)
Upcoming week (22nd June - 28th June)
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.
Task: sync command - populate overlay with successful ebuilds from pypi
When I will get bored or stuck with task #1, I'll start working on command that will generate ebuilds from all packages in pypi to an overlay.
Cheers, Domen
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
- wiki/user stories for scrum development
I'm more than happy to announce first pre-alpha prototype. Intended goal is to make people start using the tool and reporting back their critics.
Install gpypi2
$ sudo pip install http://bitbucket.org/iElectric/g-pypi2/get/tip.zip
or
$ sudo easy_install http://bitbucket.org/iElectric/g-pypi2/get/tip.zip
Create an ebuild
$ sudo gpypi2 create flask
* Generating ebuild: Flask 0.4
* Your ebuild is here: /usr/local/portage/dev-python/flask/flask-0.4.ebuild
* Dependency needed: Werkzeug
* Dependency needed: Jinja2
* Generating ebuild: Werkzeug 0.6.2
* Your ebuild is here: /usr/local/portage/dev-python/werkzeug/werkzeug-0.6.2.ebuild
* Generating ebuild: Jinja2 2.5
* Your ebuild is here: /usr/local/portage/dev-python/jinja2/jinja2-2.5.ebuild
* Dependency needed: Babel
* Generating ebuild: Babel 0.9.5
* Your ebuild is here: /usr/local/portage/dev-python/babel/babel-0.9.5.ebuild
NOTE: ebuilds will probably not function yet, features are yet to be completed/added. Report bugs to `issue tracker <http://bitbucket.org/iElectric/g-pypi2/issues?status=new&status=open>`_.
Previous week (15-21 June)
Main goal of previous week was to get closer to first prototype. Done.
Task: First snippet of command line interface
Put enough together to assemble ebuilds from command line. I think many issues may pop up, and lots of bugs shall be fixed. I'm currently mostly doing stuff from my head, with not much practise whatsoever. Mostly, we should get a result of better test coverage (currrently about 50%). The only component left untouched is the configuration. I would like to touch this topic after all my exams are over, leaving me time and productivity.
Command line interface was added, test coverage is up to 60%. Lots of small fixes were done. As a bonus, I added portage output syntax colors.
Task: get_dependencies - another refactor to enamer
Title says it all. Also handling of multiple version operators should be added. Example: foobar>=0.5&& foobar<0.6 should resolve in <0.6 blocker and >=0.5 requirement.
Multiple operators on version dependencies are handled as blockers, implemented in tip. However get_dependencies was not refactored, since I still might be adding functionality. Not really necessary for now.
Upcoming week (22-28 June)
Task: Use SrcUriNamer
gpypi2.enamer.SrcUriNamer is awaiting for quite 2 weeks now to be finally used. It's basically factory that generates SRC_URI and HOMEPAGE according to mirror provider. A lot of additional refactoring will be needed to Enamer to use this utility instead of current guessing/parsing.
Task: Fix bugs reported by users
Lot of bugs are going to pop up; fix bugs, write tests and add documentation.
Task: Increase test coverage
I'm still not satisfied with test coverage. I'll try to increase it a bit more. It's 10 days week of exams on my university, soon I will be able to put in more effort in implementing features.
Cheers, Domen
I'm very happy first stage of my Gentoo mirror project is done.
More information about server, how to use it with Gentoo and statitics can be read here
Server is an old box of my girlfriend (thanks!). The box used to have issues with rebooting during ubuntu gnome session, I hope it was graphic's card fault (no graphic desktop is running now).
Consider this beta testing period, spread the world of Slovenian Gentoo mirror! Link is 50/50mbit FTTH. Current location of server is temporary, until I find free provider to sponzor full 100mbit link. Leave any questions at domen[AT]dev.si