On 26 octobre 15:00, Aurélien Campéas wrote: > [...] > >>Now, to move on, I have nothing against dropping the current type > >>constraints if one can get reasonnable evidence that if wont break > >>code. > > > >I don't see proper way to keep bw compat for this corner case if we decide > >to fix the @monkeypatch semantic. Though, as you, I don't have any client > >usage in mind, so it seems acceptable to me. > > I'm talking about evidence, not principled "proof". > That would mean checking several of our/customer apps that rely > heavily on @monkeypatch.
How do we get evidence here? I don't know, beside by talking about it here so that people feeling concerned may check their own code base et eventually jump in if they find someting that may be concerned. I'm also telling that I don't know any usage in **my** code base, and that discussed usage seems weird enough to me to feel that no (more than a single) usage of this exists in the wild. So if no one put his hand up here because his code base is concerned, I'll change the semantic of @monkeypatch with proper warning in ChangeLog file. This is surely not "pure" (semantic breakage), but definitly pragmatic (drop a very dark corner case for the sake of code simplicity, readability, and easy compatibility across python versions. -- Sylvain Thénault, LOGILAB, Paris (01.45.32.03.12) - Toulouse (05.62.17.16.42) Formations Python, Debian, Méth. Agiles: http://www.logilab.fr/formations Développement logiciel sur mesure: http://www.logilab.fr/services CubicWeb, the semantic web framework: http://www.cubicweb.org _______________________________________________ Python-Projects mailing list [email protected] http://lists.logilab.org/mailman/listinfo/python-projects
