- Drop pytest-tap
- Update azure pipelines config
- Borrow ramdisk configuration from pip
- Fix pyinstaller ref for python 2
- Add 0-minute timeout and add github workflow
- Add skip for pywin32
- Scale down to `-n auto` to reduce race conditions on windows
- Skip pywin32 on python 3.8 as the relevant dependencies aren't
compatible
- Use default pip exists action = ignore to work around VCS race
condition
- Create local temp directory to avoid crossing drive letter boundary on
azure during CI runs
- Monkeypatch click windows console detection to return False in CI
Signed-off-by: Dan Ryan <dan.ryan@canonical.com>
- Verbose logs will now write gracefully to the terminal even while the
spinner is running (i.e. during locking)
- This PR also cuts over to Devpi for a backing cache rather than a
hacked httpbin instance
- Inclues a refactor of `pip_install` to deduplicate logic
- Attempts to switch back to relying on native editable installs in pip
as the current implementation is broken on master (i.e. nothing is
installed in the virtualenv)
- Fixes#3809
Signed-off-by: Dan Ryan <dan@danryan.co>
- Fix comparisons between post-release and non-post-release versions
- Update `pip_shims` to accommodate new pip versions
- Implement syntax changes in `environment.py` to account for new pip
syntax
- Add `required` version output to `pipenv update --outdated`
- Add pipfile version pin information as well, if available
Signed-off-by: Dan Ryan <dan@danryan.co>
- Resolve all VCS and non-piptools-resolveable deps in venv
- Implement pep517 for resolution of non-setuptools builds
- Add full support for the new dependency link format
- Fix breakages from pip 19* rollout and subsequent setuptools breakage
Signed-off-by: Dan Ryan <dan.ryan@xyleminc.com>
This regression was recently introduced, and only affects non-vcs
packages. The effect of the race is that installations of multiple
editable non-VCS sourced packages at once may cause some of them to be
un-importable.
The fix is to make editable package installs Blocking just like VCS
installs are.
- the rest of the to-do items are at https://github.com/pypa/pipenv/projects/2
- We just need to review the items in the 'needs tests' column to ensure
that they either have tests, or don't need to have tests
- If they need tests, and they don't yet have tests, we need to write
them and make sure they pass
- Then we can release. No more features/bugfixes, this is now how it's
going out.
Signed-off-by: Dan Ryan <dan@danryan.co>
Frost Ming
kennethreitz