[Python-Dev] Re: g_ascii_strtod/snprintf and Python
Michael Hudson
mwh at python.net
Thu Aug 14 14:41:01 EDT 2003
More information about the Python-Dev mailing list
Thu Aug 14 14:41:01 EDT 2003
- Previous message: [Python-Dev] Re: g_ascii_strtod/snprintf and Python
- Next message: [Python-Dev] Re: g_ascii_strtod/snprintf and Python
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Alexander Larsson <alexl at redhat.com> writes: >> Basically (AFAICT, and someone please correct me if I'm wrong) this >> means checking out >> >> http://www.python.org/psf/psf-contributor-agreement.html >> >> and filling out the Python Contributor Agreement, and mailing it in to >> the PSF. This would allow you to check in the code in question (at which >> point we would be a lot closer to having this fixed for good.) > > Which form do I need to fill out? "Proposed Contributor Agreement" seems > a bit much. I don't need a cvs account. Maybe "Proposed Contibution > Licensing Agreement"? Well, the situation is a bit confused at the moment. To my knowledge *noone* has signed one of these agreements yet -- I certainly haven't. Cheers, mwh -- ZAPHOD: Listen three eyes, don't try to outwierd me, I get stranger things than you free with my breakfast cereal. -- The Hitch-Hikers Guide to the Galaxy, Episode 7
- Previous message: [Python-Dev] Re: g_ascii_strtod/snprintf and Python
- Next message: [Python-Dev] Re: g_ascii_strtod/snprintf and Python
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Python-Dev mailing list