Python Versions and Dependencies Made Easy
Formal Metadata
| Title | Python Versions and Dependencies Made Easy |
|
| Title of Series | |
| Number of Parts | 115 |
| Author | |
| License | You are free to use, adapt and copy, distribute and transmit the work or content in adapted or unchanged form for any legal and non-commercial purpose as long as the work is attributed to the author in the manner specified by the author or licensor and the work or content is shared also in adapted form only under the conditions of this license. |
| Identifiers | |
| Publisher | |
| Release Date | |
| Language | |
Content Metadata
| Subject Area | |
| Genre | |
| Abstract | Managing Python versions and dependencies can be painful. JavaScript developers have their "node_modules" folders, but we don't have "python_modules" (yet!) in Python. Instead, we have those mysterious virtual environments. And if you also want to switch between different Python versions, it can quickly turn into a mess.
It doesn't have to be that way. With a few simple tools and practices, you can easily tame Python and its dependencies. In this talk, I'm going to show you how to do this.
I will talk about:
* How to manage Python versions with pyenv and set different versions for a folder or a shell session?
* What are virtual environments, what's the difference between different tools (venv, virtualenvwrapper, conda, etc.), and how to use them?
* How to separate global packages with pipx (and why you should do this) |
|
