Hi,
Got the toolflow working again. :) Thank you very much for your help.
Yes, the old jasper_library/platform.pyc file was the cause. Removed it and
everything compiles correctly now.
Many thanks.
Best regards,
Nitish
On Wed, Nov 20, 2019 at 9:33 PM Jack Hickish wrote:
> Hi Nitish,
>
> I
Hi Nitish,
I think this is related to
https://github.com/casper-astro/mlib_devel/commit/6e02a6ff98a9394c6b0acac570547d7841630dc9
Could you check if you have a lingering "platform.pyc" file in
mlib_devel/jasper_library and if so, delete it. Can you also check whether
this pyc file is in your
Thanks for the detailed report Nitish. I have a vague recollection that
this is something simple which might have to do with a previous install of
the title not being overwritten properly.
I'll dig through my notes and get back to you asap
Jack
On Wed, 20 Nov 2019, 12:02 am Nitish Ragoomundun,
Re virtual environments -- your simplest work around is probably to use the
`CASPER_PYTHON_VENV_ON_START` variable described at
https://casper-toolflow.readthedocs.io/en/latest/src/Configuring-the-Toolflow.html
Alternatively, if "just" changing the shebang line to point to "python3"
works, that
Hi Nitish
This is a python 2/3 issue. The toolflow has been upgraded to use python 3.
Most people are running it in a virtual environment and install the
requirements.txt in the root of mlib_devel. Assuming you are using the
latest version of mlib_devel in casper-astro.
Hope this helps.
Regards
5 matches
Mail list logo
