d5f14bd374
Simplify test case example code
2013-01-27 13:24:31 -05:00
b5b2b3f196
#16835 : update PEP 399 idiom to make it compatible with unittest test discovery.
2013-01-04 22:23:50 +02:00
270126b5d1
Fix some markup where the wrong text markup style was used for bold and italic.
2012-12-09 13:31:24 -05:00
d46cbd81f8
Mark PEP 399 as final. Along the way update the post history and fix a
...
very nit-picky detail that Benjamin pointed out.
2011-08-19 21:00:37 -07:00
74a80ac945
Update to remove the 100% branch coverage requirement to simply say
...
comprehensive coverage is needed. Also mention how more abstract C
APIs should be used over type-specific ones to make sure APIs in C
code do not restrict to a specific type when not needed.
2011-07-17 17:18:06 -07:00
71e040460e
Minor clarification
2011-04-16 13:47:30 -07:00
5efdbbb390
Mention that tests that cover C-specific issues are a good thing.
2011-04-12 15:03:54 -07:00
3acdd3085c
Update PEP 399 to include comments from python-dev.
2011-04-12 14:59:45 -07:00
cfb1d26c38
Explicitly mention accelerator modules can be a subset of functionality.
2011-04-06 10:05:50 -07:00
e68bd8b5ae
Fix some spelling mistakes found by Ezio.
2011-04-06 09:38:21 -07:00
e5cf0673e5
Fix a spelling mistake in the title of PEP 399
2011-04-04 16:47:09 -07:00
c69f92775b
Draft of PEP 399: Pure Python/C Accelerator Module Compatibiilty Requirements
2011-04-04 16:37:07 -07:00
Brett Cannon
Ezio Melotti