You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For example, FilePath.child, IFilePath.child and ZipFile.child use different argument names, which means that you can't be certain that it is safe to call the child method with keyword arguments.
Maybe it would also be a good idea for twistedchecker to automatically to zope.interface.verify.verifyClass tests, except that would require actually importing the module.
I am not sure if this is the right place to do this check.
It would need to import the module and the interface... and you might have modules which are only loaded on a specific OS so you would need to run the checker on multiple operating systems
For my project, for each class I have a test_initialization unit test, in which I check for interface implementation using a test helper.
Maybe we can update the Twisted reviewer's check list and add a note that for new classes we need a test against interface implementation.
For example, FilePath.child, IFilePath.child and ZipFile.child use different argument names, which means that you can't be certain that it is safe to call the child method with keyword arguments.
Maybe it would also be a good idea for twistedchecker to automatically to zope.interface.verify.verifyClass tests, except that would require actually importing the module.
Imported from Launchpad using lp2gh.
The text was updated successfully, but these errors were encountered: