ChanServ changed the topic of #mlpack to: "mlpack: a fast, flexible machine learning library :: We don't always respond instantly, but we will respond; please be patient :: Logs at http://www.mlpack.org/irc/
ib07 has quit [Quit: https://quassel-irc.org - Chat comfortably. Anywhere.]
felicien[m] has left #mlpack []
ImQ009 has joined #mlpack
< ggalan87[m]> <AlexNguyenGitter "@zoq Hi, I'm experiemnting on th"> assuming you don't run it inside a virtual env, a common reason for this is a pip executable pointing to python2 installation, while python executable pointing to python3 installation or vice versa. another reason (even if you are inside a venv) is that during installation some nasty error may have arised and you didn't spot them in the installation log. you can try
< ggalan87[m]> re-installing with --no-cache-dir flag. I have come up with both issues with other packages. I don't have any hands on experience with gym
< zoq> AlexNguyenGitter: When you install gym with pip is that using python3? I think right now Gym supports Python3+.
yashwants19[m] has quit [Quit: Idle for 30+ days]
< AyushSingh[m]> I have been stuck with this issue since few weeks - <https://github.com/mlpack/mlpack/issues/2840>. Can someone please help out?
< AyushSingh[m]> Thanks.
Shooter23 has joined #mlpack
ImQ009 has quit [Quit: Leaving]
< AlexNguyenGitter> @zoq @gglan87 hi, I have fixed the library problem by using the virtual environment, now it has errors that is related to the video generator, which also means that the code catch an error on the line where the cpp file call env.render(). Have you encountered this before?
RyanStoutGitter[ has left #mlpack []
< zoq> AlexNguyenGitter: Can you print the exact error message?
Shooter23 has quit [Quit: Leaving]