Important Notice: Our web hosting provider recently started charging us for additional visits, which was unexpected. In response, we're seeking donations. Depending on the situation, we may explore different monetization options for our Community and Expert Contributors. It's crucial to provide more returns for their expertise and offer more Expert Validated Answers or AI Validated Answers. Learn more about our hosting issue here.

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

bug PyGTK report
0
Posted

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

0

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 b

0

Okay, you found a bug. The standard procedure is: a) Test against the latest git version of PyGTK, if you can. This helps catch errors that have already been fixed but haven’t migrated into a release. 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 git (“git format-patch” will do the job) to the bug reported. After the patch has been reviewed and

Related Questions

What is your question?

*Sadly, we had to bring back ads too. Hopefully more targeted.