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
DEPRECATION: scour is being installed using the legacy 'setup.py install' method, because it does not have a 'pyproject.toml' and the 'wheel' package is not installed. pip 23.1 will enforce this behaviour change. A possible replacement is to enable the '--use-pep517' option. Discussion can be found at https://github.com/pypa/pip/issues/8559
#309
Open
JoKalliauer opened this issue
Mar 9, 2023
· 2 comments
I tried pip3 install --upgrade https://github.com/codedread/scour/archive/master.zip
and received
Defaulting to user installation because normal site-packages is not writeable
Collecting https://github.com/codedread/scour/archive/master.zip
Using cached https://github.com/codedread/scour/archive/master.zip
Preparing metadata (setup.py) ... done
Requirement already satisfied: six>=1.9.0 in /usr/lib/python3.11/site-packages (from scour==0.38.2) (1.16.0)
Installing collected packages: scour
DEPRECATION: scour is being installed using the legacy 'setup.py install' method, because it does not have a 'pyproject.toml' and the 'wheel' package is not installed. pip 23.1 will enforce this behaviour change. A possible replacement is to enable the '--use-pep517' option. Discussion can be found at https://github.com/pypa/pip/issues/8559
Running setup.py install for scour ... done
Successfully installed scour-0.38.2
not sure if that might get a future issue on my side or for scour, or maybe no issue at all.
The text was updated successfully, but these errors were encountered:
I think it is just a unimportant message. I think if you update to pip 23.1: python3 -m pip install --upgrade pip it should not get this message any more
I tried
pip3 install --upgrade https://github.com/codedread/scour/archive/master.zip
and received
not sure if that might get a future issue on my side or for scour, or maybe no issue at all.
The text was updated successfully, but these errors were encountered: