Bryan,
Let me take a step backwards. I accept that documentation may be out of date,
wrong, misleading, etc. Maybe I've been barking up the wrong tree because the
out-of-date documentation led me astray. These things happen as systems evolve.
So, what I want to do is develop and run web
> On Oct 7, 2020, at 7:28 PM, Bryan Davis wrote:
>
> This may actually be the root of some of your frustrations. Toolforge
> is not meant to be a replacement for a development environment on your
> local laptop or other server.
Hmmm. That's not the impression I got from reading what's
On Wed, Oct 7, 2020 at 4:16 PM Roy Smith wrote:
>
> > On Oct 7, 2020, at 4:04 PM, Bryan Davis wrote:
> >
> > Use a `webservice python3.7 shell` session as your dev/test
> > environment and you will a) get the same python version as the
> > "production" container, and b) move your dev/test
It would be really good if the bastions could be updated to something more
modern, so we could have a uniform python infrastructure everywhere. I think I
once opened a phab ticket for this, which was closed as some variation on
infeasible.
I ran into exactly the issue described below myself.
On Wed, Oct 7, 2020 at 9:15 AM maxime delzenne
wrote:
>
> Hello,
>
> First of all, thank you to Chico Venancio for the explanation about "kubectl
> describe". However it still did not start...
>
> It seems to me that there is a problem with python3.7. When I install the
> venv for python3.7
Hello,
First of all, thank you to Chico Venancio for the explanation about
"kubectl describe". However it still did not start...
It seems to me that there is a problem with python3.7. When I install the
venv for python3.7 (web and base, same problem) and I do a command "hello
Kubernetes!", it
