[issue9259] Python 2.7 breaks assigned __exit__s

2010-07-26 Thread Dave Malcolm
Changes by Dave Malcolm : -- nosy: +dmalcolm ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.

[issue9259] Python 2.7 breaks assigned __exit__s

2010-07-14 Thread Éric Araujo
Éric Araujo added the comment: Since you know the project, the bug and the fix, I think you’re in a better position than me to talk with them. -- ___ Python tracker ___

[issue9259] Python 2.7 breaks assigned __exit__s

2010-07-14 Thread Ariel Ben-Yehuda
Ariel Ben-Yehuda added the comment: Done it for myself. However, I am not a GI Maintainer - you should talk with them and send them this patch. -- ___ Python tracker ___ ___

[issue9259] Python 2.7 breaks assigned __exit__s

2010-07-14 Thread Éric Araujo
Éric Araujo added the comment: Since Benjamin Peterson, release manager for 2.7, confirmed that the change was intentional, I’m closing again. To solve the bug in GI, you need to define a metaclass with those __enter__ and __exit__ methods, then use it as metaclass for LibtoolImporter. Please

[issue9259] Python 2.7 breaks assigned __exit__s

2010-07-14 Thread Éric Araujo
Éric Araujo added the comment: I am afraid we have conflicting viewpoints. You are saying that upgrading Python broke code, and I agree it’s a bad thing. Usually such regression reports are accepted and fixed. In this case however, the code was already broken in the previous version, it was

[issue9259] Python 2.7 breaks assigned __exit__s

2010-07-14 Thread Ariel Ben-Yehuda
Ariel Ben-Yehuda added the comment: My test on Class Methods was based on the GI Code that does not run on Python 2.7. -- ___ Python tracker ___

[issue9259] Python 2.7 breaks assigned __exit__s

2010-07-14 Thread Éric Araujo
Éric Araujo added the comment: Please produce a test to prove that Python behaves in contradiction to the documentation. Otherwise I’m afraid it’s a GI bug, like in your tests :) -- ___ Python tracker

[issue9259] Python 2.7 breaks assigned __exit__s

2010-07-14 Thread Ariel Ben-Yehuda
Ariel Ben-Yehuda added the comment: Bug or not bug, Python2.7 breaks Gobject-Introspection. -- status: closed -> open ___ Python tracker ___ _

[issue9259] Python 2.7 breaks assigned __exit__s

2010-07-14 Thread Éric Araujo
Changes by Éric Araujo : -- resolution: -> invalid stage: -> committed/rejected status: open -> closed type: -> behavior ___ Python tracker ___

[issue9259] Python 2.7 breaks assigned __exit__s

2010-07-14 Thread Éric Araujo
Éric Araujo added the comment: Thank you for the report. Unfortunately, the 2.6 behavior was a bug, as I explained on #9220: Magic methods are looked up on the object’s class, not in the object’s __dict__. (Your test with class methods

[issue9259] Python 2.7 breaks assigned __exit__s

2010-07-14 Thread Antoine Pitrou
Changes by Antoine Pitrou : -- nosy: +benjamin.peterson ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://m

[issue9259] Python 2.7 breaks assigned __exit__s

2010-07-14 Thread Ariel Ben-Yehuda
New submission from Ariel Ben-Yehuda : Hello, I think there is a problem with Python 2.7: I installed it, and tried to compile GObject-Introspection 0.9.2. Here is the result: ... GISCAN GLib-2.0.gir Traceback (most recent call last): File "../tools/g-ir-scanner", line 36, in from gisc