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
When attempting to run a single script, the cwd (which is vscode will be the folder of the script) is considered for imports first. This causes Python to import ./types when expecting to import stdlib types (https://docs.python.org/3/library/types.html).
@mshafer-NI Does this affect users of nidaqmx-python or does it only affect developers working on nidaqmx-python? For users, the current directory should be outside the nidaqmx package.
nidaqmx/types.py has been there since the beginning: https://github.com/ni/nidaqmx-python/blob/0.5.2/nidaqmx/types.py . Renaming nidaqmx.types to something else would break compatibility. If this affects users, would it be acceptable to rename the submodule to _types.py and alias it in nidaqmx/__init__.py?
When attempting to run a single script, the cwd (which is vscode will be the folder of the script) is considered for imports first. This causes Python to import ./types when expecting to import stdlib types (https://docs.python.org/3/library/types.html).
This violates [O.2.1] ❌ DO NOT Redefine or “shadow” declarations
The text was updated successfully, but these errors were encountered: