On 29Jul2018 1253, Serhiy Storchaka wrote: > The benefit is that it will be easier to run all C API tests at once, > and only them, and it will be clearer what C API is covered by tests. > The disadvantage is that you will need to run several files for testing > marshal for example. Can we make the regular tests import and also run the related C API tests? So that a normal run wouldn't normally include the entire C API test directory, but would include test classes in the related Python test modules? (Maybe there's a way to decorate the test classes for this?) I agree with the intent, but also think that's quite a disadvantage. It would be good to avoid it. Cheers, Steve
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