Eeek, I found a bug in PyGTK. Where do I report it?

Okay, you found a bug. The standard procedure is: a) Test against the latest SVN version of PyGTK, if you can. This helps catch errors that have already been fixed but haven't migrated into a release.

Remember to test against the SVN branch you are using. B) If you are unsure it's a bug, make a request discussing it on the mailing list, or present it to the IRC channel. C) File a new bug on the pygtk product at GNOME Bugzilla bugzilla.gnome.org Remembering the bug number will help when referencing the bug through email.

Bugs make remembering problems a lot easier by making sure problems are uniquely identified in a simple and focused way. Remember, a great deal of help can be provided by a good bug report. Including a testcase will make fixing MUCH easier, and if that's impossible, listing the exact steps to reproduce will help too.

D) If you can, write some code to fix the bug and attach a patch in the unified diff format against current SVN (svn diff -urNp will do the job) to the ... more.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.