This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author ezio.melotti
Recipients brett.cannon, chris.jerdonek, eric.araujo, ezio.melotti, r.david.murray, rhettinger, sandro.tosi
Date 2013-03-02.18:31:44
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1362249104.94.0.991694349585.issue10967@psf.upfronthosting.co.za>
In-reply-to
Content
> So you are agreeing with my proposal?

I will have to see a concrete proposal first.  If a resource API is useful enough to be added to unittest, and we can come up with a decent API we can move it there, otherwise it can just stay in regrtest.  There's also the issue that the unittest API is already quite big, and adding even more things there might do more harm than good.

There are several other parts of regrtest that can take advantage of already existing unittest features first, and convert them might be enough to close this issue even if the existing resource infrastructure is kept in regrtest.
History
Date User Action Args
2013-03-02 18:31:45ezio.melottisetrecipients: + ezio.melotti, brett.cannon, rhettinger, eric.araujo, r.david.murray, sandro.tosi, chris.jerdonek
2013-03-02 18:31:44ezio.melottisetmessageid: <1362249104.94.0.991694349585.issue10967@psf.upfronthosting.co.za>
2013-03-02 18:31:44ezio.melottilinkissue10967 messages
2013-03-02 18:31:44ezio.melotticreate