( )⚙ D11296 pyoxidized: disable part of `test-install.t` related to pip and virtualenv

This is an archive of the discontinued Mercurial Phabricator instance.

Differential D11296

pyoxidized: disable part of `test-install.t` related to pip and virtualenv
ClosedPublic

Authored by marmoute on Aug 18 2021, 9:24 AM.

Details

Reviewers
None
Group Reviewers
hg-reviewers
Commits
rHGfa50f208de73: pyoxidized: disable part of `test-install.t` related to pip and virtualenv
Summary

This part are testing manual installation of Mercurial, this is not relevant
for the pyoxidizer variant.

Diff Detail

Repository
rHG Mercurial
Branch
stable
Lint
No Linters Available
Unit
No Unit Test Coverage

Event Timeline

marmoute created this revision.Aug 18 2021, 9:24 AM
marmoute added a commit: rHGfa50f208de73: pyoxidized: disable part of `test-install.t` related to pip and virtualenv.Aug 18 2021, 9:19 PM
This revision was not accepted when it landed; it landed in state Needs Review.
Closed by commit rHGfa50f208de73: pyoxidized: disable part of `test-install.t` related to pip and virtualenv (authored by marmoute). · Explain Why
This revision was automatically updated to reflect the committed changes.

Revision Contents
Changeset List

PathPackages
Mtests/test-install.t (4 lines)

Diff 29917

tests/test-install.t

But some Linux distros strip out this module's functionality involving pip, But some Linux distros strip out this module's functionality involving pip,
so we have to look for the ensurepip module, which these distros strip out so we have to look for the ensurepip module, which these distros strip out
completely. completely.
On Python 2, we use the 3rd party virtualenv module, if available. On Python 2, we use the 3rd party virtualenv module, if available.
$ cd $TESTTMP $ cd $TESTTMP
$ unset PYTHONPATH $ unset PYTHONPATH
#if py3 ensurepip network-io #if py3 ensurepip network-io no-pyoxidizer
$ "$PYTHON" -m venv installenv >> pip.log $ "$PYTHON" -m venv installenv >> pip.log
Hack: Debian does something a bit different in ensurepip.bootstrap. This makes Hack: Debian does something a bit different in ensurepip.bootstrap. This makes
it so that pip thinks the 'wheel' wheel is installed so it can build wheels; it so that pip thinks the 'wheel' wheel is installed so it can build wheels;
when it goes to try, however, it shells out to run `python3 -u <setup.py>`, when it goes to try, however, it shells out to run `python3 -u <setup.py>`,
that *doesn't* get the 'wheel' wheel, and it fails with an invalid command that *doesn't* get the 'wheel' wheel, and it fails with an invalid command
'bdist_wheel'. To fix this, we just delete the wheel from where Debian put it in 'bdist_wheel'. To fix this, we just delete the wheel from where Debian put it in
our virtual env. Then pip doesn't think it's installed and doesn't try to build. our virtual env. Then pip doesn't think it's installed and doesn't try to build.
checking "re2" regexp engine \((available|missing)\) (re) checking "re2" regexp engine \((available|missing)\) (re)
checking templates ($TESTTMP/installenv/*/site-packages/mercurial/templates)... (glob) checking templates ($TESTTMP/installenv/*/site-packages/mercurial/templates)... (glob)
checking default template ($TESTTMP/installenv/*/site-packages/mercurial/templates/map-cmdline.default) (glob) checking default template ($TESTTMP/installenv/*/site-packages/mercurial/templates/map-cmdline.default) (glob)
checking commit editor... (*) (glob) checking commit editor... (*) (glob)
checking username (test) checking username (test)
no problems detected no problems detected
#endif #endif
#if virtualenv no-py3 network-io #if virtualenv no-py3 network-io no-pyoxidizer
Note: --no-site-packages is the default for all versions enabled by hghave Note: --no-site-packages is the default for all versions enabled by hghave
$ "$PYTHON" -m virtualenv installenv >> pip.log $ "$PYTHON" -m virtualenv installenv >> pip.log
DEPRECATION: Python 2.7 will reach the end of its life on January 1st, 2020. Please upgrade your Python as Python 2.7 won't be maintained after that date. A future version of pip will drop support for Python 2.7. (?) DEPRECATION: Python 2.7 will reach the end of its life on January 1st, 2020. Please upgrade your Python as Python 2.7 won't be maintained after that date. A future version of pip will drop support for Python 2.7. (?)
DEPRECATION: Python 2.7 will reach the end of its life on January 1st, 2020. Please upgrade your Python as Python 2.7 won't be maintained after that date. A future version of pip will drop support for Python 2.7. More details about Python 2 support in pip, can be found at https://pip.pypa.io/en/latest/development/release-process/#python-2-support (?) DEPRECATION: Python 2.7 will reach the end of its life on January 1st, 2020. Please upgrade your Python as Python 2.7 won't be maintained after that date. A future version of pip will drop support for Python 2.7. More details about Python 2 support in pip, can be found at https://pip.pypa.io/en/latest/development/release-process/#python-2-support (?)
Note: we use this weird path to run pip and hg to avoid platform differences, Note: we use this weird path to run pip and hg to avoid platform differences,