[issue8840] io.StringIO: truncate+print disabled in 3.1.2

Pascal Chambon added the comment: The change was announced in http://docs.python.org/dev/whatsnew/2.7.html, but indeed it wasn't advertised in py3k changes - my apologies, I didn't check it was. I agree that the doc should be clarified on several aspects. * The returned value

[issue8840] truncate() semantics changed in 3.1.2

Pascal Chambon added the comment: Good B-) Woudl it be necessary to update the docstrings too ? -- ___ Python tracker <http://bugs.python.org/issue8840> ___ ___

[issue27141] Fix collections.UserList shallow copy

Changes by Pascal Chambon : -- nosy: +pakal ___ Python tracker <http://bugs.python.org/issue27141> ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue17716] IMPORTANT - Process corruption on partly failed imports

New submission from Pascal Chambon: Hello, we've encountered several times a very nasty bug on our framework, several times tests or even production code (served by mod_wsgi) ended up in a broken state, where imports like "from . import processing_exceptions", which were N

[issue17716] From ... import fails when parent package failed but child module succeeded, yet works in std import case

Pascal Chambon added the comment: Thanks for the feedback, I'm gonna read those docs and related issues asap, and check that planned evolutions will actually fix this. just as a side note in the meantime: I dont think that the problem here is the "purge " of sys.modules,

[issue17636] Modify IMPORT_FROM to fallback on sys.modules

Changes by Pascal Chambon : -- nosy: +Pascal.Chambon ___ Python tracker <http://bugs.python.org/issue17636> ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue17716] From ... import fails when parent package failed but child module succeeded, yet works in std import case

Pascal Chambon added the comment: (sorry for the long post, but it's a complex issue I guess) I forgot to precise that I have this behaviour with the latest python2.7, as well as python3.3 (I guess other versions behave the same). I agree that having side effects in script imports

[issue17716] From ... import fails when parent package failed but child module succeeded, yet works in std import case

Pascal Chambon added the comment: Well, since it's a tough decision to make (erasing all children modules when rolling back parent, or instead reconnecting with children on 2nd import of parent), I guess it should be discussed on python-dev first, shouldn

[issue7659] Attribute assignment on object() instances raises wrong exception

Pascal Chambon added the comment: I guess it can, since retrocompatibility prevents some normalization here. Or is it worth updating the doc about "AttributeError", misleading regarding the type of exception expected in this case ? -- status: pendi

<    1   2