Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

PYTHONPATH Manager lockout #22081

Closed
DDT-1of1 opened this issue May 15, 2024 · 1 comment
Closed

PYTHONPATH Manager lockout #22081

DDT-1of1 opened this issue May 15, 2024 · 1 comment

Comments

@DDT-1of1
Copy link

Description

What steps will reproduce the problem?

Enter a path to site packages causes error message indicating NO LONGER ALLOWED for that use.

NOTE: VISA MODULE not found basis for error. Same version of Spyder on new PC as an older PC that DOES allow entry in PYTHONPATH Manager. Yet new installation has crippled use of Python path manager. SO WHY is Spyder version the SAME? Console allows loading the desired module so I KNOW the Windows configuration is correct enough for Spyder to work EXCEPT A CODE CHANGE that does not allow PYTHONPATH manager to accept input. Horrible violation of version control! Install conda compliant Python is not allowed by Company. Forcing me to NOT USE Spyder. What a shame I now have to use Visual Studio. Thanks for making great tool than I now cannot use.

Versions

  • Spyder version: 5.5.4 (standalone)
  • Python version: 3.8.10 64-bit
  • Qt version: 5.15.2
  • PyQt5 version: 5.15.10
  • Operating System: Windows-10-10.0.19045-SP0

Dependencies

# Mandatory:
atomicwrites >=1.2.0          :  1.4.1 (OK)
chardet >=2.0.0               :  5.2.0 (OK)
cloudpickle >=0.5.0           :  3.0.0 (OK)
cookiecutter >=1.6.0          :  2.6.0 (OK)
diff_match_patch >=20181111   :  20230430 (OK)
intervaltree                  :  None (OK)
IPython >=8.12.2,<8.13.0      :  8.12.3 (OK)
jedi >=0.17.2,<0.20.0         :  0.19.1 (OK)
jellyfish >=0.7               :  1.0.3 (OK)
jsonschema >=3.2.0            :  4.21.1 (OK)
keyring >=17.0.0              :  25.1.0 (OK)
nbconvert >=4.0               :  7.16.3 (OK)
numpydoc >=0.6.0              :  1.7.0 (OK)
paramiko >=2.4.0              :  3.4.0 (OK)
parso >=0.7.0,<0.9.0          :  0.8.4 (OK)
pexpect >=4.4.0               :  4.9.0 (OK)
pickleshare >=0.4             :  0.7.5 (OK)
psutil >=5.3                  :  5.9.8 (OK)
pygments >=2.0                :  2.17.2 (OK)
pylint >=3.1,<4               :  3.1.0 (OK)
pylint_venv >=3.0.2           :  3.0.3 (OK)
pyls_spyder >=0.4.0           :  0.4.0 (OK)
pylsp >=1.11.0,<1.12.0        :  1.11.0 (OK)
pylsp_black >=2.0.0,<3.0.0    :  2.0.0 (OK)
qdarkstyle >=3.2.0,<3.3.0     :  3.2.3 (OK)
qstylizer >=0.2.2             :  0.2.2 (OK)
qtawesome >=1.3.1,<1.4.0      :  1.3.1 (OK)
qtconsole >=5.5.1,<5.6.0      :  5.5.1 (OK)
qtpy >=2.1.0                  :  2.4.1 (OK)
rtree >=0.9.7                 :  1.2.0 (OK)
setuptools >=49.6.0           :  69.2.0 (OK)
sphinx >=0.6.6                :  7.1.2 (OK)
spyder_kernels >=2.5.1,<2.6.0 :  2.5.1 (OK)
textdistance >=4.2.0          :  4.6.1 (OK)
three_merge >=0.1.1           :  0.1.1 (OK)
watchdog                      :  4.0.0 (OK)
zmq >=24.0.0                  :  25.1.2 (OK)

# Optional:
cython >=0.21                 :  3.0.10 (OK)
matplotlib >=3.0.0            :  3.7.5 (OK)
numpy >=1.7                   :  1.24.4 (OK)
pandas >=1.1.1                :  2.0.3 (OK)
scipy >=0.17.0                :  1.10.1 (OK)
sympy >=0.7.3                 :  1.12 (OK)
@DDT-1of1
Copy link
Author

NOTE: VISA MODULE not found is basis for crippling error . Same version of Spyder on new PC as an older PC that DOES allow entry in PYTHONPATH Manager. Yet new installation has crippled use of Python path manager. SO WHY is Spyder version the SAME? Console allows loading the desired module so I KNOW the Windows configuration is correct enough for Spyder to work EXCEPT A CODE CHANGE that does not allow PYTHONPATH manager to accept input. Horrible violation of version control! Install conda compliant Python is not allowed by Company. Forcing me to NOT USE Spyder. What a shame I now have to use Visual Studio. Thanks for making great tool than I now cannot use.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant