You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: _posts/2024-12-03-pycharm-projects-envs.md
+2-1Lines changed: 2 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -64,14 +64,15 @@ Ah...
64
64
Modularity.
65
65
🧘
66
66
>[!NOTE]
67
+
>
67
68
>If you have multiple _small_ repos this may not be an issue.
68
69
>But I still advise considering this approach as it's helped me keep code separate.
69
70
70
71
# Environments
71
72
I wrote a [blog post](https://medium.com/@ianiat11/we-recommend-creating-an-environment-da38af0cecbb) a couple years ago
72
73
that briefly covers two kinds of virtual environments:
73
74
[`conda`](https://docs.conda.io/projects/conda/en/latest/user-guide/tasks/manage-environments.html) and [`venv`](https://docs.python.org/3/library/venv.html).
74
-
If you read it you may notice that I'm not a big fan of `conda`, so we're not going to talk about here.
75
+
If you read it you may notice that I'm not a big fan of `conda`, so we're not going to talk about it here.
75
76
Instead we'll use old faithful—`venv`
76
77
77
78
Managing repos as separate projects is great for modularity.
0 commit comments