aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorGravatar Chris <[email protected]>2021-01-19 20:31:01 +0000
committerGravatar Chris <[email protected]>2021-01-19 20:31:01 +0000
commit7f920229e0d8245b2778833f5089997d3d46432a (patch)
treeadbf23a112e8c9aee47e5c268bf0e4c6de3768ee
parentMerge branch 'new-env-tag' of github.com:ChrisLovering/bot into new-env-tag (diff)
grammar and spelling fixes
-rw-r--r--bot/resources/tags/enviroments.md18
-rw-r--r--bot/resources/tags/environments.md18
2 files changed, 18 insertions, 18 deletions
diff --git a/bot/resources/tags/enviroments.md b/bot/resources/tags/enviroments.md
deleted file mode 100644
index 5b2914cd9..000000000
--- a/bot/resources/tags/enviroments.md
+++ /dev/null
@@ -1,18 +0,0 @@
-**Python Enviroments**
-
-The main purpose of Python [virtual environments](https://docs.python.org/3/library/venv.html#venv-def) is to create an isolated environment for Python projects. This means that each project can have its own dependencies, such as third party packages installed using `pip`, regardless of what dependencies every other project has.
-
-To see the current enviroment in use by python you can run:
-```py
->>> import sys
->>> print(sys.executable)
-/usr/bin/python3
-```
-
-To see the enviroment in use by `pip` you can do `pip debug`, or `pip3 debug` for linux/macOS. The 3rd line of the output will contain the path in use. I.E. `sys.executable: /usr/bin/python3`
-
-If the python's `sys.executable` doesn't match pip's then they are currently using different enviroments! This may cause python to raise a `ModuleNotFoundError` when you try to use a package you just installed with pip, as it was installed to a different enviroment.
-
-Further reading:
-• [Real Python's primer on Python Virtual Environments](https://realpython.com/python-virtual-environments-a-primer)
-• [pyenv: Simple Python Version Management](https://github.com/pyenv/pyenv)
diff --git a/bot/resources/tags/environments.md b/bot/resources/tags/environments.md
new file mode 100644
index 000000000..f8825f0dd
--- /dev/null
+++ b/bot/resources/tags/environments.md
@@ -0,0 +1,18 @@
+**Python Environments**
+
+The main purpose of Python [virtual environments](https://docs.Python.org/3/library/venv.html#venv-def) is to create an isolated environment for Python projects. This means that each project can have its own dependencies, such as third party packages installed using pip, regardless of what dependencies every other project has.
+
+To see the current environment in use by Python, you can run:
+```py
+>>> import sys
+>>> print(sys.executable)
+/usr/bin/Python3
+```
+
+To see the environment in use by pip, you can do `pip debug` (`pip3 debug` for Linux/macOS). The 3rd line of the output will contain the path in use. e.g. `sys.executable: /usr/bin/Python3`.
+
+If Python's `sys.executable` doesn't match pip's then they are currently using different environments! This may cause Python to raise a `ModuleNotFoundError` when you try to use a package you just installed with pip, as it was installed to a different environment.
+
+Further reading:
+• [Python Virtual Environments: A Primer](https://realPython.com/Python-virtual-environments-a-primer)
+• [pyenv: Simple Python Version Management](https://github.com/pyenv/pyenv)