Skip to content

Conversation

discdiver
Copy link
Contributor

Recommend use venv instead of virtualenv

From the Python docs:
"Changed in version 3.5: The use of venv is now recommended for creating virtual environments."
-https://docs.python.org/3/library/venv.html

From the Python docs:
"Changed in version 3.5: The use of venv is now recommended for creating virtual environments."
-https://docs.python.org/3/library/venv.html
update links for virtualenv -> venv
-------------------------------------------------

For development, we recommend to use virtualenv_ environments and pip_
For development, we recommend you use venv_ for virtual environments and pip_
Copy link
Member

@nicoddemus nicoddemus Feb 20, 2019

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks @Bjwebb!

Good suggestion, but because we still support Python 2.7 and 3.4, I believe we should mention both, perhaps like this:

we recommend you use venv[link] for virtual environments (or virtualenv[link] for Python 2.7 and 3.4) and pip ...

What do you think?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good thought!

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Updated PR to mention virtualenv for Python 2.7.

Python 3.4 comes with venv, so I just mentioned 2.7 needing virtualenv. Source.

Copy link
Member

@nicoddemus nicoddemus left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Great, thanks @discdiver!

`venv` is already available in Python 3.4, my mistake
@codecov
Copy link

codecov bot commented Feb 21, 2019

Codecov Report

Merging #4813 into master will decrease coverage by 1.85%.
The diff coverage is n/a.

Impacted file tree graph

@@            Coverage Diff             @@
##           master    #4813      +/-   ##
==========================================
- Coverage   95.77%   93.91%   -1.86%     
==========================================
  Files         113      113              
  Lines       25652    25145     -507     
  Branches     2505     2495      -10     
==========================================
- Hits        24567    23616     -951     
- Misses        769     1186     +417     
- Partials      316      343      +27
Flag Coverage Δ
#docs ?
#doctesting ?
#linting ?
#linux 91.83% <ø> (-3.77%) ⬇️
#nobyte ?
#numpy ?
#pexpect ?
#pluggymaster 91.83% <ø> (-1.83%) ⬇️
#py27 90.46% <ø> (-3.23%) ⬇️
#py34 ?
#py35 ?
#py36 ?
#py37 92.22% <ø> (-1.58%) ⬇️
#py38 ?
#trial ?
#windows 92.97% <ø> (-0.72%) ⬇️
#xdist 92.97% <ø> (-0.88%) ⬇️
Impacted Files Coverage Δ
testing/test_pdb.py 47.68% <0%> (-51.41%) ⬇️
testing/python/approx.py 80.45% <0%> (-19.18%) ⬇️
src/_pytest/unittest.py 76.19% <0%> (-18.09%) ⬇️
src/_pytest/debugging.py 60.37% <0%> (-18.02%) ⬇️
testing/test_unittest.py 85.58% <0%> (-13.55%) ⬇️
src/_pytest/python_api.py 87.44% <0%> (-10.06%) ⬇️
src/_pytest/assertion/util.py 93.3% <0%> (-4.34%) ⬇️
src/_pytest/doctest.py 93.47% <0%> (-2.93%) ⬇️
src/_pytest/compat.py 93.96% <0%> (-2.57%) ⬇️
testing/python/integration.py 89.36% <0%> (-2.37%) ⬇️
... and 74 more

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update c8a87e4...e75915b. Read the comment docs.

@nicoddemus
Copy link
Member

Merging as docs have passed already. 👍

@nicoddemus nicoddemus merged commit 4ee10d2 into pytest-dev:master Feb 21, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants