<_whitenotifier-6>
[YoWASP/runtime] whitequark c2da605 - [autorelease] Update wasmtime version requirement from <11 to <12.
GenTooMan has quit [Ping timeout: 246 seconds]
Degi_ has joined #amaranth-lang
Degi has quit [Ping timeout: 245 seconds]
Degi_ is now known as Degi
GenTooMan has joined #amaranth-lang
jjsuperpower has quit [Ping timeout: 240 seconds]
<d1b2>
<chuckmcm> Okay, after figuring out I needed to downgrade MarkupSafe to 2.0.1 I get this: (quarterhorse) cmcmanis@quarterhorse:test-amaranth$ python -m amaranth_boards.icebreaker Traceback (most recent call last): File "<frozen runpy>", line 198, in _run_module_as_main File "<frozen runpy>", line 88, in _run_code File
<d1b2>
"/freenas/home/cmcmanis/arm-experiments/projects/amaranth/quarterhorse/lib/python3.11/site-packages/amaranth_boards-0.0.0-py3.11.egg/amaranth_boards/icebreaker.py", line 6, in <module> ModuleNotFoundError: No module named 'amaranth_boards.resources' (quarterhorse) cmcmanis@quarterhorse:test-amaranth$
<whitequark[cis]>
you need to install amaranth-boards
<d1b2>
<chuckmcm> was trying to do that from a copy of the repo that I had pulled locally.
<d1b2>
<chuckmcm> I did manage to get it to install when I used the --editable flag ? Without that it would install amaranth-0.3 but not amaranth_boards. Very odd. Anyway, once I got that to work, it complained that it couldn't find iceprog.
<d1b2>
<chuckmcm> oh wait, not exactly right. It wasn't able to successfully program
elle has quit [Remote host closed the connection]
<d1b2>
<chuckmcm> Basically not getting it into program mode.
<d1b2>
<chuckmcm> So the old hold the button while you power cycle thing did its thing and it seems to blink So there is that.
<d1b2>
<chuckmcm> I think I'm finally through all the steps to validate the workflow.
<d1b2>
<chuckmcm> So is there an update to jinja2 to support the more current MarkupSafe?
<whitequark[cis]>
it's been updated a while ago; it sounds like your installation doesn't quite go right
<d1b2>
<chuckmcm> The default, out of the box, install of the amaranth stuff appears to use 2.0.1 of MarkupSafe which is, I believe, a dependency of Jinja2. But the current MarkupSafe is 2.1.x which changed soft_unicode to soft_str() as a result when you run a build with the new MarkupSafe it can't find soft_unicode.
<whitequark[cis]>
Amaranth does not depend on any version of MarkupSafe; the git version depends on Jinja2>=3.0,<4, which should work fine
<d1b2>
<chuckmcm> FWIW this was a clean install from nothing (as a documentation test and to develop better understanding prior to embarking on glasgow stuff)
<whitequark[cis]>
it seems like for whichever reason you end up installing Amaranth 0.3
<d1b2>
<chuckmcm> That is what pip seems to pull. I've now got two versions installed (one in sitepackages as amaranth/ and one as amaranth_0.3_xxxx/ (basically version stuff)
<whitequark[cis]>
that seems like a bad idea
<whitequark[cis]>
you should post the pip invocation and output if you are encountering an issue of the kind "pip installs something wrong"
<d1b2>
<chuckmcm> My process was build a local copy of python3, create a virtual environment, pip install amaranth while sitting in the git repo for amaranth. (this may be incorrect of course)
<d1b2>
<chuckmcm> pip install --editable amaranth from the amaranth directory.
<whitequark[cis]>
what is the exact command you are using?
<whitequark[cis]>
okay, that's the wrong one
<whitequark[cis]>
pip install --editable . if you are in the amaranth directory
<whitequark[cis]>
you're not typing the correct command
<whitequark[cis]>
it ends with a sole dot
<whitequark[cis]>
(perhaps it's too small to see?)
<d1b2>
<chuckmcm> Yeah. That was not clear. So that installed 0.4
<d1b2>
<chuckmcm> What is the fix for the .egg deprecation?
<whitequark[cis]>
you need to post more context; I do not have a way to know which exact complaint pip has shown you to prompt this question
<d1b2>
<chuckmcm> (quarterhorse) cmcmanis@quarterhorse:amaranth_boards$ pip install --editable . DEPRECATION: Loading egg at /freenas/home/cmcmanis/arm-experiments/projects/amaranth/quarterhorse/lib/python3.11/site-packages/amaranth-0.0.0-py3.11.egg is deprecated. pip 23.3 will enforce this behaviour change. A possible replacement is to use pip for package installation.. DEPRECATION: Loading egg at
<d1b2>
/freenas/home/cmcmanis/arm-experiments/projects/amaranth/quarterhorse/lib/python3.11/site-packages/Jinja2-3.1.2-py3.11.egg is deprecated. pip 23.3 will enforce this behaviour change. A possible replacement is to use pip for package installation..
* whitequark[cis]
sighs
<whitequark[cis]>
I have no idea
<whitequark[cis]>
that's the first time I hit this specific deprecation message, I think
<whitequark[cis]>
it seems like something went wrong in your installation process, but it's also possible I'm missing something more important
<whitequark[cis]>
I can say that it is safe to ignore that for now
<d1b2>
<chuckmcm> Okay, here is another weird bit. If I used pip install --editable . from the amaranth_boards directory it installs amaranth_0.3 as a dependency and knocks back jinja2 as well. So I think part of this is something about that install.
<whitequark[cis]>
hmmm
<d1b2>
<chuckmcm> git pull says it is up to date
<whitequark[cis]>
amaranth-boards depends on amaranth>=0.3,<0.5
<whitequark[cis]>
what does pip print when you run that command? please post pip output when reporting any issue, it is always necessary to understand what is happening
<d1b2>
<chuckmcm> From installing from amaranth_boards:
<d1b2>
<chuckmcm> Weird that it is using the cached version of 0.3
<whitequark[cis]>
it seems like it thinks amaranth is not already installed
<whitequark[cis]>
are you sure you are using the same virtualenv when installing amaranth-boards?
<whitequark[cis]>
do you happen to use some sort of virtualenv manager, or a different shell?
<d1b2>
<chuckmcm> different shell
<whitequark[cis]>
did you activate the virtualenv in it?
<d1b2>
<chuckmcm> yes that is the (quarterhorse) as opposed to (venv) because I have one for my 22.04 host and one for my 18.04 host
<whitequark[cis]>
sorry, I don't understand; can you rephrase?
<d1b2>
<chuckmcm> I am doing this process twice, once on a Ubuntu 18.04 host (quarterhorse) and once on a Ubuntu 22.04 host (morgan). Trying to capture the differences and problems for people on older releases vs. more current releases. My first step is doing the 18.04 host (quarterhorse).
<d1b2>
<chuckmcm> Both hosts share a filessytem via NFS.
<d1b2>
<chuckmcm> But they have their own root drives where home directories are stored so they each have a host specific copy of my .local/bin tree.
<whitequark[cis]>
alright. if you intend to use virtualenvs you need to create a single virtualenv and activate it before installing amaranth and amaranth-boards
<whitequark[cis]>
this is actually something I'm working on simplifying right now
<_whitenotifier-6>
[amaranth-lang/amaranth] github-merge-queue[bot] pushed 2 commits to gh-readonly-queue/main/pr-845-1d200f1e4f1bad2f2938956feb416637ab5ab70d [+0/-0/±2] https://github.com/amaranth-lang/amaranth/compare/4627d8d3c8ab^...7a9dbc8c118f
<_whitenotifier-6>
[amaranth-lang/amaranth] whitequark 4627d8d - pyproject: depend on `setuptools>=67.0` instead of `~=67.0`.
<_whitenotifier-6>
[amaranth-lang/amaranth] whitequark 7a9dbc8 - Add PDM-related files to gitignore.
<_whitenotifier-6>
[amaranth] github-merge-queue[bot] created branch gh-readonly-queue/main/pr-845-1d200f1e4f1bad2f2938956feb416637ab5ab70d - https://github.com/amaranth-lang/amaranth
<d1b2>
<chuckmcm> Yes, this is known. Steps are #1 python -m venv <hostname> followed by #2 source <hostname>/bin/activate, followed by #3 pip install amaranth -editable .
<whitequark[cis]>
okay, what happens next?
<d1b2>
<chuckmcm> Do the tuturial, create counter, then the sim hosted version, then build a blinker for the board.
<d1b2>
<chuckmcm> Follow ons to that are build a more complex component, evaluate it with sim/Pulseview (or wavegtk), and then run it on the icebreaker.
<whitequark[cis]>
where is amaranth-boards being updated?
<whitequark[cis]>
s/updated/installed/
<d1b2>
<chuckmcm> Good catch, right after #3, so #4 would be 'pip install --editable .` from the amaranth_boards directory.
<whitequark[cis]>
that seems right. can you redo steps #1-#4 and post the complete terminal log here?
<_whitenotifier-6>
[amaranth-lang/amaranth-lang.github.io] github-merge-queue[bot] b509bd7 - Deploying to main from @ amaranth-lang/amaranth@7a9dbc8c118ffc70142ebcba7ca1cc55e36d88c9 🚀
<d1b2>
<chuckmcm> I wonder if I could filter the screen transcript to remove all of the escape codes, sigh.
<whitequark[cis]>
yes, not surprised; it felt like an error you have made somewhere in the process
<d1b2>
<chuckmcm> It is a combination of not knowing what I don't know and trying things when things don't work. Glad to have gotten through to the point where it works correctly. Now to blow away the bogus environment and re-create it.
kmehall has quit [Remote host closed the connection]
antoinevg[m] has quit [Remote host closed the connection]
<josuah>
@chuckmcm by running cat over the captured text then copy-pasting everything with the mice
<josuah>
Or this as a compromise to use in scripts: r=$(printf '\x0D') e=$(printf '\x1B'); sed -r "s/.*$r(.)/\1/; s/$e[^a-zA-Z]*[a-zA-Z]//g" amaranth-from-zero-to-blink.txt
<d1b2>
<josuah_dem> This template project is a great idea! Permits to summarize all the evolution made to Amaranth so that people new to the language can always start from it.