Open abhijeetSaroha opened 7 months ago
@xmnlab , It gives error that conda
or mamba
should be init
before activate/deactivate command. But I tried to init the shell but it still give same error.
Have you any suggestion?
Hi @abhijeetSaroha ! To be honest I had this issue before in different situations, but I don't know why. I am going to check with a friend from conda-forge to see if I can have some clues about that.
Thanks for working on that.
I will try to investigate it a bit tomorrow.
update: I will take a look into this tomorrow. I have more stuff in my backlog XD
@abhijeetSaroha , sorry .. I didn't have time to take a look into that yet, really sorry ... some bunch of problems are popping-up at work .. really sorry :(
but I would like to share some thoughts here:
have you tested running the conda init for xonsh outside first? maybe also for sh as well .. to see if that would work. of course, after that, it is necessary to restart the console session
@abhijeetSaroha , when you have time, could you add a test for that?
@abhijeetSaroha , although this PR is a bit blocked, but just for the record, maybe another approach would be using pixi: https://prefix.dev/blog/introducing_multi_env_pixi
this is a very old PR .. but just to bring some ideas about this topic .. maybe we could use nox to intermediate this. in another words, I think we should create something like a plugin to nox and if the user wants to play with virtual environments, maybe the way to go would be via nox
Solves #52