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
Significant latency between publishing a python module in PyPi and being able to pull it via pipenv update . I can update it immediately via pip install -U , but not with pipenv. After 30 minutes or more - not sure exactly how long, I can run pipenv update and it will show that it is updated in the Pipfile.lock as expected.
This may not be a bug - but a feature resulting from caching, but I can't figure out how to bypass the cache if so.
Expected result
Expect that pipenv update updates the module immediately after publishing it on PyPi
Actual result
Significant latency, minutes to hours in order to update a module after publishing an update on PyPi.
This is a problem with PyPI, it is known to require significant time to propagate your upload (caching and CDN reasons, I believe). We can’t help it, because there is simply no way for us to know the upload. If you feel this is significantly impacting your workflow, consider providing a feedback to pypa/warehouse (the repo for PyPI), or posting to the distutils-sig mailing list. I am not very optimistic there would be a vast and fast improvement, unfortunately, since this is basically a physical limitation of the current infrastructure.
p.s. I believe PyPA would happily accept donations if you want to solve this by throwing resources to it. This is not tongue in cheek.
Issue description
Significant latency between publishing a python module in PyPi and being able to pull it via pipenv update . I can update it immediately via pip install -U , but not with pipenv. After 30 minutes or more - not sure exactly how long, I can run pipenv update and it will show that it is updated in the Pipfile.lock as expected.
This may not be a bug - but a feature resulting from caching, but I can't figure out how to bypass the cache if so.
Expected result
Expect that pipenv update updates the module immediately after publishing it on PyPi
Actual result
Significant latency, minutes to hours in order to update a module after publishing an update on PyPi.
Steps to replicate
pipenv update <module>
$ pipenv --support
Pipenv version:
'2018.7.1'
Pipenv location:
'/opt/local/Library/Frameworks/Python.framework/Versions/3.6/lib/python3.6/site-packages/pipenv'
Python location:
'/opt/local/Library/Frameworks/Python.framework/Versions/3.6/bin/python3.6'
Other Python installations in
PATH
:2.7
:/opt/local/bin/python2.7
2.7
:/opt/local/bin/python2.7
2.7
:/usr/bin/python2.7
2.7
:/opt/local/Library/Frameworks/Python.framework/Versions/2.7/bin/python2.7
3.4
:/opt/local/bin/python3.4m
3.4
:/opt/local/bin/python3.4
3.5
:/opt/local/bin/python3.5m
3.5
:/opt/local/bin/python3.5
3.6
:/opt/local/bin/python3.6m
3.6
:/opt/local/bin/python3.6
3.6
:/opt/local/Library/Frameworks/Python.framework/Versions/3.6/bin/python3.6
3.6.3
:/opt/local/bin/python
2.7.10
:/usr/bin/python
2.7.14
:/opt/local/Library/Frameworks/Python.framework/Versions/2.7/bin/python
2.7.14
:/opt/local/bin/python2
2.7.14
:/opt/local/Library/Frameworks/Python.framework/Versions/2.7/bin/python2
3.6.3
:/opt/local/bin/python3
3.6.3
:/opt/local/Library/Frameworks/Python.framework/Versions/3.6/bin/python3
PEP 508 Information:
System environment variables:
MANPATH
OPENBELAPIHOME
rvm_bin_path
TERM_PROGRAM
GEM_HOME
TERM
SHELL
IRBRC
TMPDIR
PERL5LIB
Apple_PubSub_Socket_Render
TERM_PROGRAM_VERSION
GITHUB_AUTH_CLIENT_ID
OLDPWD
MY_RUBY_HOME
TERM_SESSION_ID
GIT_EDITOR
ANSIBLE_VAULT_PASSWORD_FILE
USER
CC_MAIN_PW
_system_type
COMMAND_MODE
rvm_path
BSTEST_KEYCLOAK_SECRET
SSH_AUTH_SOCK
__CF_USER_TEXT_ENCODING
GIT_AUTHOR_NAME
WORKON_HOME
CHANGELOG_GITHUB_TOKEN
PROJECT_HOME
rvm_prefix
PATH
BSTEST_JWT_SECRET
PIPENV_DEFAULT_PYTHON_VERSION
PWD
JAVA_HOME
DBUS_LAUNCHD_SESSION_BUS_SOCKET
EDITOR
LANG
SERVER_MODE
ITERM_PROFILE
_system_arch
XPC_FLAGS
ITERM_ORIG_PS1
CEKEEPER_HOME
PS1
_system_version
HISTCONTROL
XPC_SERVICE_NAME
rvm_version
SHLVL
HOME
COLORFGBG
ITERM_PREV_PS1
ITERM_SESSION_ID
LOGNAME
BSTEST_ARANGO_USER
GEM_PATH
GITHUB_AUTH_CLIENT_SECRET
GOPATH
EC2_PRIVATE_KEY
BSTEST_ARANGO_PASSWD
GIT_AUTHOR_EMAIL
AWS_ACCESS_KEY
RUBY_VERSION
SECURITYSESSIONID
_system_name
AWS_SECRET_KEY
EC2_CERT
COLORTERM
_
PYTHONDONTWRITEBYTECODE
PIP_PYTHON_PATH
Pipenv–specific environment variables:
PIPENV_DEFAULT_PYTHON_VERSION
:3.6
Debug–specific environment variables:
PATH
:/Users/william/.rvm/gems/ruby-2.3.0/bin:/Users/william/.rvm/gems/ruby-2.3.0@global/bin:/Users/william/.rvm/rubies/ruby-2.3.0/bin:/opt/local/sbin:/opt/local/bin:/Users/william/work/bin:/Users/william/bin:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/go/bin:/usr/local/share/dotnet:~/.dotnet/tools:/Library/Frameworks/Mono.framework/Versions/Current/Commands:/opt/local/Library/Frameworks/Python.framework/Versions/3.6/bin:/opt/local/Library/Frameworks/Python.framework/Versions/2.7/bin:.:/opt/local/lib/postgresql95/bin:node_modules/.bin:/Users/william/.rvm/bin
SHELL
:/bin/bash
EDITOR
:vim
LANG
:en_US.UTF-8
PWD
:/Users/william/studio/dev/belapi
Contents of
Pipfile
('/Users/william/studio/dev/belapi/Pipfile'):Contents of
Pipfile.lock
('/Users/william/studio/dev/belapi/Pipfile.lock'):The text was updated successfully, but these errors were encountered: