This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author lemburg
Recipients eric.araujo, ezio.melotti, l0nwlf, lemburg, maker, r.david.murray
Date 2011-05-27.13:12:16
SpamBayes Score 5.6616627e-09
Marked as misclassified No
Message-id <4DDFA323.2020708@egenix.com>
In-reply-to <1306500467.38.0.751022412473.issue8898@psf.upfronthosting.co.za>
Content
Michele Orrù wrote:
> 
> Michele Orrù <maker.py@gmail.com> added the comment:
> 
> Any idea about how to unittest mime.aliases?

Test the APIs you probably created for accessing it.

> Also, since I've just created a new file, are there some buracratic issues? I mean, do I have to add something at the top of the file?
> (I'm just signing the Contributor Agreement)

You just need to put the usual copyright line at the top of
the file, together with the sentence from the agreement.

Apart from that, you also need to make sure that the other build
setups include the new file (PCbuild, Makefile.pre.in, etc.). If you
don't know how to do this, you can ask someone else to take
care of this, since it usually requires domain knowledge (e.g.
to add the file to the Windows builds).
History
Date User Action Args
2011-05-27 13:12:17lemburgsetrecipients: + lemburg, ezio.melotti, eric.araujo, r.david.murray, l0nwlf, maker
2011-05-27 13:12:16lemburglinkissue8898 messages
2011-05-27 13:12:16lemburgcreate