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
After upgrading to Pipenv 2022.4.21 I get this warning on running lock and sync etc.:
/home/gert/.local/lib/python3.10/site-packages/setuptools/config/__init__.py:28: SetuptoolsDeprecationWarning: As setuptools moves its configuration towards `pyproject.toml`,
`setuptools.config.read_configuration` became deprecated.
For the time being, you can use the `setuptools.config.setupcfg` module
to access a backward compatible API, but this module is provisional
and might be removed in the future.
warnings.warn(dedent(msg), SetuptoolsDeprecationWarning)
There's no traceback so I'm not sure what causes this, but to me it appears it could well be Pipenv's vendored dependency:
A silent and successful pipenv lock and installation of the venv with pipenv sync --dev.
Actual result
The spurious warnings above.
Steps to replicate
As I don't have this on every Pipenv-enabled 'project', but only on one particular one, I think it's because I include a dependency that's editable-installed in the Pipfile like this.
$ pipenv lock
Creating a virtualenv for this project...
Pipfile: /home/gert/temp/sampleproject/Pipfile
Using /usr/bin/python3 (3.10.4) to create virtualenv...
⠼ Creating virtual environment...created virtual environment CPython3.10.4.final.0-64 in 155ms
creator CPython3Posix(dest=/home/gert/.local/share/virtualenvs/sampleproject-KET6yNd_, clear=False, no_vcs_ignore=False, global=False)
seeder FromAppData(download=False, pip=bundle, setuptools=bundle, wheel=bundle, via=copy, app_data_dir=/home/gert/.local/share/virtualenv)
added seed packages: pip==22.0.4, setuptools==62.1.0, wheel==0.37.1
activators BashActivator,CShellActivator,FishActivator,NushellActivator,PowerShellActivator,PythonActivator
✔ Successfully created virtual environment!
Virtualenv location: /home/gert/.local/share/virtualenvs/sampleproject-KET6yNd_
Locking [dev-packages] dependencies...
Building requirements...
/home/gert/.local/lib/python3.10/site-packages/setuptools/config/__init__.py:28: SetuptoolsDeprecationWarning: As setuptools moves its configuration towards `pyproject.toml`,
`setuptools.config.read_configuration` became deprecated.
For the time being, you can use the `setuptools.config.setupcfg` module
to access a backward compatible API, but this module is provisional
and might be removed in the future.
warnings.warn(dedent(msg), SetuptoolsDeprecationWarning)
Use case: development of your own package, with a Pipfile in its repo.
Issue description
After upgrading to Pipenv 2022.4.21 I get this warning on running
lock
andsync
etc.:There's no traceback so I'm not sure what causes this, but to me it appears it could well be Pipenv's vendored dependency:
pipenv/pipenv/vendor/requirementslib/models/setup_info.py
Lines 516 to 518 in b5c7c1e
This is fixed upstream with sarugaku/requirementslib#316
Expected result
A silent and successful
pipenv lock
and installation of the venv withpipenv sync --dev
.Actual result
The spurious warnings above.
Steps to replicate
As I don't have this on every Pipenv-enabled 'project', but only on one particular one, I think it's because I include a dependency that's editable-installed in the
Pipfile
like this.pipenv lock
Use case: development of your own package, with a Pipfile in its repo.
$ pipenv --support
Pipenv version:
'2022.4.21'
Pipenv location:
'/home/gert/.local/lib/python3.10/site-packages/pipenv'
Python location:
'/usr/bin/python'
Python installations found:
3.11.0
:/home/gert/.pyenv/versions/3.11-dev/bin/python3
3.10.4
:/usr/bin/python3
3.10.4
:/usr/bin/python
3.10.4
:/home/gert/.pyenv/versions/3.10.4/bin/python3
PEP 508 Information:
System environment variables:
SHELL
SESSION_MANAGER
WINDOWID
QT_SCREEN_SCALE_FACTORS
COLORTERM
PYENV_SHELL
XDG_CONFIG_DIRS
XDG_SESSION_PATH
LANGUAGE
SSH_AUTH_SOCK
SHELL_SESSION_ID
DESKTOP_SESSION
LC_MONETARY
GTK_RC_FILES
XCURSOR_SIZE
GTK_MODULES
XDG_SEAT
PWD
XDG_SESSION_DESKTOP
LOGNAME
XDG_SESSION_TYPE
SYSTEMD_EXEC_PID
XAUTHORITY
MOTD_SHOWN
GTK2_RC_FILES
HOME
LANG
XDG_CURRENT_DESKTOP
KONSOLE_DBUS_SERVICE
KONSOLE_DBUS_SESSION
PROFILEHOME
XDG_SEAT_PATH
KONSOLE_VERSION
KDE_SESSION_UID
XDG_SESSION_CLASS
TERM
USER
COLORFGBG
KDE_SESSION_VERSION
PAM_KWALLET5_LOGIN
DISPLAY
SHLVL
LC_MEASUREMENT
XDG_VTNR
XDG_SESSION_ID
PAPERSIZE
XDG_RUNTIME_DIR
LC_TIME
QT_AUTO_SCREEN_SCALE_FACTOR
XCURSOR_THEME
KDE_FULL_SESSION
PATH
DBUS_SESSION_BUS_ADDRESS
KDE_APPLICATIONS_AS_SCOPE
MAIL
LC_NUMERIC
OLDPWD
KONSOLE_DBUS_WINDOW
_
PIP_SHIMS_BASE_MODULE
PIP_DISABLE_PIP_VERSION_CHECK
PIP_PYTHON_PATH
PYTHONDONTWRITEBYTECODE
PYTHONFINDER_IGNORE_UNSUPPORTED
Pipenv–specific environment variables:
Debug–specific environment variables:
PATH
:~/.local/bin:/home/gert/.pyenv/shims:/usr/local/sbin:/usr/local/bin:/usr/bin:/usr/lib/jvm/default/bin:/usr/bin/site_perl:/usr/bin/vendor_perl:/usr/bin/core_perl
SHELL
:/bin/bash
LANG
:en_US.UTF-8
PWD
:/home/gert/temp/sampleproject
Contents of
Pipfile
('/home/gert/temp/sampleproject/Pipfile'):Contents of
Pipfile.lock
('/home/gert/temp/sampleproject/Pipfile.lock'):The text was updated successfully, but these errors were encountered: