- the bug is not low as it causes SEGFAULT in a skripting languge, something NEVER should happen.
- the 2.16 release is so broken, that the most obvious things don't work like subclassing, wtf... something worked always good
- this bug affects many software, not just pida.
THIS IS A MAJOR BUG
so, now the question.
why is there no fix in jaunty updates ?
Ohh, i forgott, i could put some really ugly workaround in there with a note:
Hey, this totally sucks but ubuntu doesn't like to fix obvious, severe bugs. They prefer to put the broken upstream ones in place.
NO NO NO, i will not do it. If you lucky I will say, install python-central, python-gobject and some other stuff from karmic and you will not get the crashes anymore....
sorry that i have to knock on this again.
- the bug is not low as it causes SEGFAULT in a skripting languge, something NEVER should happen.
- the 2.16 release is so broken, that the most obvious things don't work like subclassing, wtf... something worked always good
- this bug affects many software, not just pida.
THIS IS A MAJOR BUG
so, now the question.
why is there no fix in jaunty updates ?
i already put in a http:// pida.co. uk/trac/ wiki/Frequently AskedQuestions so people may find out why it is unstable, but will most likely blame us.
Ohh, i forgott, i could put some really ugly workaround in there with a note:
Hey, this totally sucks but ubuntu doesn't like to fix obvious, severe bugs. They prefer to put the broken upstream ones in place.
NO NO NO, i will not do it. If you lucky I will say, install python-central, python-gobject and some other stuff from karmic and you will not get the crashes anymore....