Honestly, probably not (although anything is possible). One, I've never used it myself, although that might change in the future. You can accomplish much the same end (perhaps a bit less elegantly) using virtual environments, so until someone is game for learning pyenv, they'll be just peachy. ;)
Two, I'm having to write these articles from as OS-agnostic standpoint, and I don't always have Windows or Mac systems to test on. (I rely on docs and my existing knowledge of those operating systems for that. Since this works with system paths, that gets especially tricky. (I'm deliberately avoiding the entire topic of system paths for reason of OS availability on this end.)
Three, it's something of a can of worms diving into many tools: if I cover pyenv, undoubtedly someone will ask me to cover pythonbrew, pythonz, pipenv (actually, already had four requests for that), and so forth. So, while pyenv looks like a thoroughly awesome tool, it seems a bit beyond the very specific knowledge level I'm aiming for. As it is, the Testing article is going to be a trick, because I need to cover all three of the main testing frameworks for Python, lest someone comment that I left out an important one.
Anyway, all that to say - probably no. However, if you wrote an article on it, I'd happily add a link to it at the bottom of the Virtual Environments article. :)
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Honestly, probably not (although anything is possible). One, I've never used it myself, although that might change in the future. You can accomplish much the same end (perhaps a bit less elegantly) using virtual environments, so until someone is game for learning
pyenv, they'll be just peachy. ;)Two, I'm having to write these articles from as OS-agnostic standpoint, and I don't always have Windows or Mac systems to test on. (I rely on docs and my existing knowledge of those operating systems for that. Since this works with system paths, that gets especially tricky. (I'm deliberately avoiding the entire topic of system paths for reason of OS availability on this end.)
Three, it's something of a can of worms diving into many tools: if I cover
pyenv, undoubtedly someone will ask me to coverpythonbrew,pythonz,pipenv(actually, already had four requests for that), and so forth. So, whilepyenvlooks like a thoroughly awesome tool, it seems a bit beyond the very specific knowledge level I'm aiming for. As it is, the Testing article is going to be a trick, because I need to cover all three of the main testing frameworks for Python, lest someone comment that I left out an important one.Anyway, all that to say - probably no. However, if you wrote an article on it, I'd happily add a link to it at the bottom of the Virtual Environments article. :)