[gentoo-soc] GSOC weekly report #0: g-pypi

[gentoo-soc] GSOC weekly report #0: g-pypi

[Domen Kožar]

[-- Attachment #1: Type: text/plain, Size: 2128 bytes --]

Greetings!

I just noticed I sent this email on 17.05.2010 to gentoo-soc-subscribe,
so here is resend to correct list!

----------------

There is a lot going on already with gsoc2010 projects, I will try to
explain more about g-pypi status. At best, I will send email every
Monday summarizing past week and plan for the following one. 

For those unfamiliar with term g-pypi, here is how I would describe it:

- cli tool for querying Python Package Index and creating ebuild from it
- manages automatically manifests, portage categories and echangelog if
requested
- at final state it should be able to populate "g-pypi" overlay with
successfully built ebuilds

Previous week (10-16 May)
-------------------------

Main goal was to prepare environment and tools for development.

Repository, issue tracker: http://bitbucket.org/iElectric/g-pypi2
Hudson CI instance: http://hudson.fubar.si/job/g-pypi2/
Sphinx skeleton documentation: http://docs.fubar.si/gpypi2/

More about each sprint (weekly coding interval) and tickets can be read
at http://neurogeek.ath.cx/g-pypi

enamer.py (metadata conversion) and portage_util.py (portage lookup
information) have already been ported from original g-pypi package.
Currently we have almost 100% test coverage for enamer and 0% coverage
for portage_utils. Mocker will be used for portage_utils testing, but
currently I have to see exactly what functions do we actually still need
from the current module.


Upcoming week (17-23 May)
-------------------------

I'm actually on vacations from 18-24 May, with no internet connection
(according to current information). Can not promise much, but here is
the basic idea what could be done offline during some "fresh air" pauses
in Montenegro:

* port ebuild.py and cli.py
* migrate enamer functions to a class that can be later pluggable (for
sake of modularity)
* write class that tries to get SRC_URI (currently implementation will
query pypi and sourceforge by issuing HEAD HTTP request)
* test enamer functions against whole pypi mirror (specially version
parsing)


Cheers, Domen

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 490 bytes --]