[10:26] <bthomas> myawning
[10:26] <bthomas> I am pingable just in case :-)
[10:26] <Chipaca> bthomas: shoo
[12:39] <Chipaca> JoseMasson: ｇｏｏｏｏｏｏｏｏｏｏｏｏｏｏｏｏｏｏｏｏｏｏｏｏｏｏｏｏｏｏｏｄ  ｍｏｒｎｉｎｇ！
[12:40] <JoseMasson> Good morning!!!
[12:41] <Chipaca> i'm about to go out for a run
[12:41] <Chipaca> JoseMasson: anything i can do for you before i do?
[12:42] <JoseMasson> Chipaca: Thank you! go for a run
[12:42] <Chipaca> JoseMasson: ok. If something is on fire, mattermost will reach me
[12:43] <JoseMasson> Chipaca: ;-)
[12:44] <Chipaca> (i'll be leaving on the hour)
[13:06] <bthomas> JoseMasson: https://github.com/jorgenschaefer/elpy/issues/1164
[13:12] <JoseMasson> bthomas: I saw it, I think the problem I am having is that flycheck it is not using the virtualenv
[13:14] <bthomas> JoseMasson: C-c C-c should launch a python interpreter that can load modules that were installed within the python environment. But this does not seem to happen. Makes me suspect that there is some underlying issue. One possibility is that the virtual enviroment interpreter is just a link to the host provided one.
[13:25] <JoseMasson> bthomas: I think it's working ok, but flycheck....It's not a big deal
[13:26] <bthomas> JoseMasson: What are your steps to create and activate venv and does C-c C-c bring up a shell in the venv ?
[13:32] <JoseMasson> In console: $ virtualenv -p python3 venv  && source venv/bin/activate && pip install -r requirements-dev.txt
[13:33] <JoseMasson> M-x: pyvenv-activate venv/
[13:34] <JoseMasson> That's all
[13:34] <JoseMasson> It is working
[13:35] <bthomas> Let me try that. Only difference with what I was doing was the way in which I created venv. I my case I was doing "python3 -m venv ."
[13:38] <bthomas> Nope. Does not work for me. You may have some additional config which I don't. Anyway I will dig.
[18:00] <Chipaca> I think I'm going to EOW right here
[18:14] <JoseMasson> Nice weekend!