Arie Bovenberg
Arie Bovenberg
As described in issues #3827 and #3843 there is some (unavoidable) overhead in calling PyO3 wrapped functions. An idea: the ability to fall back on lower level pyo3_ffi code for...
(A bit of an obscure edge case, but worth documenting for future reference.) The `require-subclass` mode warns of any classes which _could_ be slotted, but are not. ```python class A(int):...
For debugging issues it'd be useful to be able to include some debug output. This could include: - Given paths/arguments - Settings used, and from which files they come -...
slotscheck should support something like: ```python # slotscheck: ignore[require-superclass,overlaps] class A(Base): __slots__ = ('a', 'b') # slotscheck: ignore class B(Base): __slots__ = () ```
Currently slotscheck has the `require-subclass` option, which enforces the use of `__slots__` wherever slotted classes are subclassed. However, this greatly depends on whether builtin/extension classes are considered "slotted". For example,...
It's already documented why: ``` slotscheck mymodule/ ``` doesn't work if the current directory is not explicitly in `sys.path`. However, this is a corner of Python unknown to many. To...
This should offer a good 'fuzzing' test to potentially detect introduction of new bugs
Currently it's possible to filter out modules/classes. However it'd be nice to have different sets of rules per part of the code. For example, enforcing slots strictly within a particular...