Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Allow custom python versions and environments #451

Merged
merged 5 commits into from
Feb 19, 2019

Conversation

jradmacher
Copy link
Contributor

Pull Request (PR) description

This pull request allows to install all python versions and create pyenv or virtualenv environments
with those versions.
This also adds the missing venv module in newer Debian based distributions and addresses the deprecation of pyenv in 3.6 with an expected removal of it in Python 3.8.

This Pull Request (PR) fixes the following issues

Fixes #448
Fixes the first part of #430 "pip3 missing in the virtualenv ?"

@jradmacher jradmacher force-pushed the allow_custom_versions branch 3 times, most recently from a433a6c to 0de1e57 Compare December 6, 2018 18:25
@bastelfreak
Copy link
Member

Hi @jradmacher, could you please squash the commits down a bit? Otherwise this looks good!

@bastelfreak bastelfreak added enhancement New feature or request needs-squash labels Dec 15, 2018
@bastelfreak bastelfreak added the needs-work not ready to merge just yet label Dec 25, 2018
@bastelfreak
Copy link
Member

Please also have a look at the used email address in the commits. It isn't associated with your github account.

@jradmacher jradmacher force-pushed the allow_custom_versions branch from 6af4cb8 to 827f573 Compare January 2, 2019 10:31
@jradmacher
Copy link
Contributor Author

Squashed to 4 commits. I don't want create fewer commits, as each commit introduces a non trivial behavior change.

Could you rerun the TravisCI build? It failed with an unrelated VM error.

manifests/init.pp Outdated Show resolved Hide resolved
@bastelfreak bastelfreak added needs-feedback Further information is requested and removed needs-squash needs-work not ready to merge just yet labels Jan 2, 2019
@jradmacher jradmacher force-pushed the allow_custom_versions branch from 827f573 to 5c5ac01 Compare January 3, 2019 15:44
jradmacher and others added 5 commits February 12, 2019 18:58
"python3 -m venv" is the recommended replacement since 3.6
pyvenv will be removed in 3.8

Debian (+Ubuntu) need an extra package for the script and the
_not deprecated_ python module
This should fix the first part of issue voxpupuli#430 "pip3 missing in the virtualenv ?"

using a proxy for download is not addressed here
Fixes issue voxpupuli#448, "Impossible to use version number in Ubuntu 16.04"

1) It does not make sense to restrict the allowed python versions per
distribution. Newer distribution releases add new python versions and
you can add repositories containing backports.
2) The List was outdated.

Note:
python version is needed for spec test
to create two or more venvs without duplicate declaration error
@jradmacher jradmacher force-pushed the allow_custom_versions branch from e70b9a6 to 5ea5621 Compare February 12, 2019 18:06
@jradmacher
Copy link
Contributor Author

Updates:

  • rebased to current master
    Our internal test runs were successful as were your Travis CI checks.

@bastelfreak bastelfreak removed the needs-feedback Further information is requested label Feb 19, 2019
@bastelfreak
Copy link
Member

thanks!

@bastelfreak bastelfreak merged commit af0cfe1 into voxpupuli:master Feb 19, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Impossible to use version number in Ubuntu 16.04
3 participants