From: "Urs Schütz" <u.schutz@bluewin.ch>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] jupyter notebook 500 : Internal Server Error
Date: Thu, 25 Jun 2020 22:30:52 +0200 [thread overview]
Message-ID: <ccf96a21-43f9-5ccc-082e-44fb660a87e9@bluewin.ch> (raw)
In-Reply-To: <CACSNh6OD7TuijaAzjBXzJAGb9XWeUbNiYa=MfWD7whje=L36eA@mail.gmail.com>
On 2020-06-25 21:44, Andrés Becerra Sandoval wrote:
>
>
> El jue., 25 de jun. de 2020 a la(s) 14:14, Valmor de Almeida
> (val.gentoo@gmail.com <mailto:val.gentoo@gmail.com>) escribió:
>
> Hello,
> I had to enable ~amd64 to emerge jupyter so I know this is bound for
> problems. However, anyone there able to use jupyter notebooks in
> gentoo?
> No matter what notebook I try to open, I get the internal server error.
> Thank you.
> --
> Valmor
>
>
> Not much help, but I have not had problems with jupyter for years, with
> ~amd64 profile.
>
> --
> Andrés Becerra Sandoval
>
I isolate jupyter (actually jupyterlab) in an separate python
environment. I do use pipenv to manage the python environment. It boils
down to three commands:
$> cd projectfolder
projectfolder $> pipenv install
projectfolder $> pipenv shell
projectfolder $> pipenv install jupyter-lab
pipenv itself can be installed with emerge. pipenv resolves the
dependencies within the virtual python environment.
This way of working with python solved most of my troubles with ~amd64
python packages. python packages for system and for programming purposes
stay separate this way.
--
Urs Schütz
next prev parent reply other threads:[~2020-06-25 20:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-25 20:13 [gentoo-user] jupyter notebook 500 : Internal Server Error Valmor de Almeida
2020-06-25 19:44 ` Andrés Becerra Sandoval
2020-06-25 20:30 ` Urs Schütz [this message]
2020-06-25 20:32 ` Amlesh Sivanantham
2020-06-26 15:08 ` Andreas K. Huettel
2020-06-28 6:33 ` [SOLVED] " Valmor F. de Almeida
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ccf96a21-43f9-5ccc-082e-44fb660a87e9@bluewin.ch \
--to=u.schutz@bluewin.ch \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox