Closed DanielSwain closed 10 months ago
I'm glad to be able to close this issue. If anyone wants to use setuptools
to build a library, I suggest ignoring the Django instructions (which call for creating setup.cfg
and setup.py
files in addition to pyproject.toml
). Just follow the setuptools
instructions here. You only need a pyproject.toml
file. When I rebuilt the library using python3 -m build --sdist
following the above instructions, I was then able to install it using the latest pipenv (2023.11.15) with the command that had formerly been working: python3 -m pipenv install git+ssh://git@bitbucket.org/our_organization/our-private-repo.git@master
.
Issue description
I know that a problem with installing private repos cropped up in late summer 2023, and it had been fixed for a while. For two or three months I was able to install a private repo with:
python3 -m pipenv install git+ssh://git@bitbucket.org/our_organization/our-private-repo.git@master
I recently updated pipenv and went back to working on our library (I didn't notice the previous version of pipenv during the update), and the above
install
line stopped working.Expected result
The above
install
had been working to cause the private repo to be installed correctly, and it resulted in an entry inPipfile
like this:our-private-repo = {ref = "master", git = "ssh://git@bitbucket.org/our_organization/our-private-repo.git"}
Actual result
In order to try to get things to work, I then added
egg=
to the install command:python3 -m pipenv install git+ssh://git@bitbucket.org/our_organization/our-private-repo.git@master#egg=our-private-repo --verbose
and went back through all Pipenv versions with the aboveinstall
. It finally worked at version 2023.7.23.I did find this issue where @matteius mentioned that the
egg
syntax has been deprecated, so I then tried:python3 -m pipenv install git+ssh://git@bitbucket.org/our_organization/our-private-repo.git@master#subdirectory=our-private-repo --verbose
with a more recent version of pipenv. That resulted in the following traceback which includes a message that says nosetup.py
orpyproject.toml
file could be found. However, both files are in the repo.NOTE: I am also using
wagtail-django-recaptcha = {ref = "master", git = "git+https://github.com/torchbox-forks/wagtail-django-recaptcha"}
in this project that is usingour-private-repo
.As an aside, it would be nice if the installation of private repos would be explained in the docs (including information about
egg
andsubdirectory
).The following output is the result of using the
egg
syntax as part of theinstall
line:Pipenv location:
'/usr/local/lib/python3.8/dist-packages/pipenv'
Python location:
'/usr/bin/python3'
OS Name:
'posix'
User pip version:
'23.3.1'
user Python installations found:
PEP 508 Information:
System environment variables:
SHELL
PYENV_HOOK_PATH
PYENV_SHELL
SUDO_GID
SSH_AUTH_SOCK
SUDO_COMMAND
SSH_AGENT_PID
SUDO_USER
PYENV_VERSION
PWD
PYENV_VIRTUALENV_INIT
LOGNAME
HOME
LANG
LS_COLORS
PYENV_DIR
WORKON_HOME
LESSCLOSE
TERM
LESSOPEN
USER
SHLVL
PYENV_ROOT
PATH
SUDO_UID
MAIL
OLDPWD
PYTHONDONTWRITEBYTECODE
PIP_DISABLE_PIP_VERSION_CHECK
DJANGO_SETTINGS_MODULE
DEFAULT_FROM_EMAIL
ALLOWED_HOSTS
ACCOUNT_DEFAULT_HTTP_PROTOCOL
PYTHONFINDER_IGNORE_UNSUPPORTED
Pipenv–specific environment variables:
Debug–specific environment variables:
PATH
:/root/.pyenv/versions/3.10.8/bin:/root/.pyenv/libexec:/root/.pyenv/plugins/python-build/bin:/root/.pyenv/plugins/pyenv-virtualenv/bin:/root/.pyenv/plugins/pyenv-update/bin:/root/.pyenv/plugins/pyenv-installer/bin:/root/.pyenv/plugins/pyenv-doctor/bin:/root/.pyenv/plugins/pyenv-virtualenv/shims:/root/.pyenv/shims:/root/.pyenv/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin
SHELL
:/bin/bash
LANG
:C.UTF-8
PWD
:/path/to/my-site
Contents of
Pipfile
('/our_info/Pipfile'):Contents of
Pipfile.lock
('/path/to/Pipfile.lock'):