Answer below :


-----Message d'origine-----

De : Christoph Groth <christoph.gr...@cea.fr<mailto:christoph.gr...@cea.fr>> 
Envoyé : mercredi 25 novembre 2020 20:21 À : Olivier Leblanc 
<o.lebl...@uclouvain.be<mailto:o.lebl...@uclouvain.be>> Cc : 
kwant-disc...@kwant-project.org<mailto:kwant-disc...@kwant-project.org> Objet : 
Re: [Kwant] tkwant issue solved



Hello Olivier,



We are aware that tkwant is not available for Python 3.8 on conda-forge.

Unfortunately, as far as I understand, the underlying problem is beyond our 
control.



Olivier Leblanc wrote:



> My problem was that even when activating the virtual environment in

> cmd, launching "jupyter notebook" did not use the virtual environment

> because jupyter notebook was not part of it.



So, in other words, you installed tkwant in Python environment A and then you 
were surprised not to find it in Python environment B.  Perhaps this can be 
seen as a design issue of Python virtual environments, or of Jupyter, but it's 
certainly not a problem specific to Tkwant or Kwant.



               No, I installed tkwant in Python environment B, and launching 
jupyter notebook with environment B activated did not really use environment B 
but was keeping the environment A.

Thus tkwant was not found.

This is indeed a problem from python, but adding the last line I suggest 
wouldn't change anything for users that don't obtain the issue, and would solve 
the one I had because of Python and Jupyter notebook.



> Hoping this will be added on your website.



In my opinion listing possible generic problems that one may encounter when 
using Tkwant is beyond the scope of our web site.  I think that this would 
render the instructions less useful by overloading them.



               This means I do not ask you to make a generic problems listing, 
but simply add a command line in your installation tutorial.



Cheers

Christoph



               Thank you,



               Olivier

Reply via email to