[py-dev] broken/notimplemented?
Hi Guido, (and maciej?) in the 0.9.1 release i see that "py.test.broken" and "py.test.notimplemented" were introduced into the namespace. What is the rationale? they don't have docstrings for one and they seem to be redundant, i.e. just be versions of skip. In r59284 i removed them for now and adjusted the test to show how you can get the same effect with skip. Also doesn't seem to me like it's used anywhere. holger -- Holger Krekel - freelance manager and programmer pylib py.test/greenlets/svn APIs: http://pylib.org PyPy Python/Compiler tool chain: http://codespeak.net/pypy merlinux collaborative contracting: http://merlinux.eu
holger krekel wrote:
in the 0.9.1 release i see that "py.test.broken" and "py.test.notimplemented" were introduced into the namespace. What is the rationale?
Hm, doesn't ring a bell, I probably have merged them in because there seemed to be a dependency on them from other bits of code, or because the checkin was part of other changes, or even because the checkin message for the change was confusing... Anyway, not sure if they can just go, I guess it's best to ask Maciek. Cheers, Guido
Guido Wesdorp wrote:
holger krekel wrote:
in the 0.9.1 release i see that "py.test.broken" and "py.test.notimplemented" were introduced into the namespace. What is the rationale?
Hm, doesn't ring a bell, I probably have merged them in because there seemed to be a dependency on them from other bits of code, or because the checkin was part of other changes, or even because the checkin message for the change was confusing... Anyway, not sure if they can just go, I guess it's best to ask Maciek.
Cheers,
Guido
I think I had at some point some idea about that, but I don't remember details.
participants (3)
-
Guido Wesdorp -
holger krekel -
Maciek Fijalkowski