Showing content from http://mail.python.org/pipermail/python-dev/attachments/20060630/ba2e1a7d/attachment.htm below:
On 6/30/06, <b class="gmail_sendername">Frank Wierzbicki</b> <<a href="mailto:fwierzbicki@gmail.com">fwierzbicki@gmail.com</a>> wrote:<div><span class="gmail_quote"></span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Hello all,<br><br>According to the thread that includes<br><a href="http://mail.python.org/pipermail/python-dev/2006-June/065727.html">http://mail.python.org/pipermail/python-dev/2006-June/065727.html</a><br>there will be some effort in
2.6 to make the tests in Python more<br>consistent. I would like to help with that effort, partly to sneak in<br>some checks for CPython internal tests that should be excluded from<br>Jython, but mainly to understand the future implementation of Python
<br>for which the tests provide the only real spec. Which of the current<br>tests is closest to an "ideal" test, so I can use it as a model?</blockquote><div><br>We don't have any labeled as "ideal". Either doctests or unittest tests are considered good form these days. Probably looking at the newer tests would be a good start.
<br><br>-Brett<br></div><br></div>
RetroSearch is an open source project built by @garambo
| Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4