Open
Description
openedon May 27, 2022
For example, this code:
import SalesforcePy.commons as sfc
fails with:
./test.py:1:2: N813 camelcase 'SalesforcePy.commons' imported as lowercase 'sfc'
Shouldn't pep-naming just look at the package name being imported ( consider this is an import of a package or module, and then not fail in this case?commons
) instead of looking at the parent package names too
I'm assuming this rule exists for when a class name is being imported, as discussed in https://stackoverflow.com/a/37590149/2654518. In this case:
from SalesforcePy.commons import BaseRequest as baserequest
sure should fail with:
./test.py:1:2: N813 camelcase 'BaseRequest' imported as lowercase 'baserequest'
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Metadata
Assignees
Labels
No labels