The Conda Python Version Mess: A Frustrating Experience

As a developer working with scientific software, especially in Python, I'm sure you've encountered your fair share of frustrating experiences. One such experience that I'd like to share is my encounter with the conda slowness and version management mess.

I recently tried to use Anaconda without much fuss, only to find myself stuck by the slowness of conda. The whole point of a virtual environment is that packages are installed there and not globally. But, as I soon discovered, this was not the case. My rasa version kept changing, and I found it challenging to manage different versions.

I tried to create a new virtual environment and install rasa 3.0.6 using pip. But, to my surprise, an existing rasa-version was found and replaced with the new one. This led me to think that maybe there was another way to manage different conda environments with different rasa versions. So, I created a new directory for my rasa projects and activated it.

However, things didn't go as planned. I couldn't find a good explanation on how to create multiple conda environments with different rasa versions. It seemed like a basic question, but one that left me stumped. Luckily, the community came together to help me find the solution.

After some digging, I discovered that creating new conda environments and installing rasa in each environment was the key. By doing so, I could have multiple environments with different rasa versions. This allowed me to test which version worked best with sanic.

In addition to this issue, I also faced some challenges connecting my rasa 3.0.4 bot with my WordPress website using Botfront's Webchat and ngrok. But, thanks to the help of others, I was able to find a solution to that problem as well.

Overall, my experience with conda slowness and version management was frustrating, but it taught me an important lesson about persistence and seeking help when needed.

Conda python version mess