From: "Domen Kožar" <domen@dev.si>
To: gentoo-dev <gentoo-dev@lists.gentoo.org>
Subject: [gentoo-dev] [GSOC] Python, GSoC and distutils2
Date: Thu, 17 Jun 2010 21:34:03 +0200 [thread overview]
Message-ID: <1276803243.5093.11.camel@oblak> (raw)
[-- Attachment #1: Type: text/plain, Size: 813 bytes --]
Greetings, I'm working on g-pypi2 project over this summer for Gentoo,
and among other things, I learned a lot about how Gentoo handles Python
package distributions.
There are quite some students working on distutils2 implementations, so
I thought Gentoo as source distribution has a lot to say how would
upstream Python tools help towards better standard and API to make life
just a little bit easier.
I have put together a piratepad/etherpad for easier collaboration if
anyone is willing to drop his thoughts how Python distribution of
packages could be improved, follow the link
http://piratepad.net/EIYOmjJKaJ
.. read more about GSoC team
http://bitbucket.org/tarek/distutils2/wiki/GSoC_2010_teams
.. blog planet with reports http://teckla.idyll.org/~t/planet-distutils/
Cheers, Domen
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 490 bytes --]
reply other threads:[~2010-06-17 19:34 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1276803243.5093.11.camel@oblak \
--to=domen@dev.si \
--cc=gentoo-dev@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox