00:00 <adamgreig[m]> conceivably https://github.com/python-poetry/poetry/issues/6154#issuecomment-1312725247

00:00 <whitequark> hm, I actually get: No module named 'virtualenv.activation.xonsh'

00:01 <whitequark> https://github.com/python-poetry/poetry/issues/6154#issuecomment-1218496008 oh I see

00:01 <whitequark> does it build dependencies in non-pep517 fashion too, I wonder?

00:02 <whitequark> removed virtualenv, now it's 'PosixPath' object has no attribute 'is_relative_to'

00:07 <whitequark> it looks like both of those are debian-specific

00:12 <whitequark> well, I can't get poetry to work, at all, even with pipx

00:14 <whitequark> oh, nevermind, it doesn't run poetry install if you just poetry run if your existing venv matches the python requirement

00:24 <whitequark> adamgreig: yes this is a poetry bug

00:25 <whitequark> take a look here: https://github.com/python-poetry/poetry/blob/71b3d6e030c879f0b4b8e3a08eac2b38a402b6bd/src/poetry/inspection/info.py#L599

00:27 <whitequark> poetry runs (through a few layers of indirection) the get_requires_for_build_wheel hook, which for setuptools involves running setup.py, which fails because there's no setuptools_scm, and then the same thing happens again when it tries to run setup.py directly

00:30 <whitequark> if you look at https://peps.python.org/pep-0517/#build-environment it says: "The get_requires_for_build_wheel and get_requires_for_build_sdist hooks are executed in an environment which contains the bootstrap requirements specified in the pyproject.toml file.

00:30 <whitequark> "

00:30 <whitequark> so hardcoding just pyproject-hooks and build isn't sufficient

00:30 <adamgreig[m]> sigh, that explains it

00:30 <adamgreig[m]> thanks for investigating

00:31 <whitequark> I wonder what pypa/build does

00:32 <whitequark> it reads pyproject.toml https://github.com/pypa/build/blob/bb434e3e08ddd41b2b096501513cf79942bb737b/src/build/__init__.py#L209

00:35 <whitequark> I think this works

00:37 <whitequark> yep, installs fine for me. you'll need to remove the source checkout of amaranth, since it will have an empty nmigen directory git won't remove, and that confuses setuptools

00:37 <whitequark> I might actually just fix that

00:37 <adamgreig[m]> i put together a minimal reproducing example in https://github.com/adamgreig/poetry_build_requires_bug

00:38 <adamgreig[m]> do you plan to report this to poetry?

00:40 <whitequark> I was hoping someone else would submit a poetry bug to be honest

00:41 <adamgreig[m]> will do

00:41 <whitequark> thank you!

00:54 <adamgreig[m]> done, https://github.com/python-poetry/poetry/issues/7702

02:08 <whitequark> thank you!

02:10 <_whitenotifier-9> [amaranth-lang/amaranth] whitequark pushed 1 commit to main [+0/-0/±1] https://github.com/amaranth-lang/amaranth/compare/5f094a23eb1a...46e0a00a0860

02:10 <_whitenotifier-9> [amaranth-lang/amaranth] whitequark 46e0a00 - Add a workaround for setuptools erroring out on stale git checkouts.

02:10 <_whitenotifier-9> [amaranth-lang/amaranth-lang.github.io] whitequark pushed 1 commit to main [+0/-0/±27] https://github.com/amaranth-lang/amaranth-lang.github.io/compare/8a9257f40cd6...3345920e685e

02:10 <_whitenotifier-9> [amaranth-lang/amaranth-lang.github.io] whitequark 3345920 - Deploying to main from @ amaranth-lang/amaranth@46e0a00a08607ad50d6ff9326b471b136ea86960 🚀

02:46 <FFY00> I don't understand what they're doing there

02:48 <FFY00> they're installing pypa/build in a venv, to then run a script that uses pypa/build to build a new virtual environment and get the metadata for the project

02:55 <whitequark> yeah I'm not sure either

02:55 <whitequark> I'd expect poetry would just need to depend on pypa/build?

02:57 <FFY00> they already do

02:57 <FFY00> so I am very confused

02:58 <whitequark> yeah I have no idea ^^; I just fiddled with it until it built

02:58 <whitequark> I'm not very invested in poetry, this is why Amaranth uses bare setuptools for now

04:12 <FFY00> I opened a PR rewriting that whole code 😅

04:17 <whitequark> got a link?

04:33 <FFY00> https://github.com/python-poetry/poetry/pull/7703

04:33 <FFY00> I'm fixing mypy rn

06:41 <DeVector[m]> Is there any way to add print statements in elaborate method like we use $display in verilog in simulation?

06:42 <kivikakk[m]> you can print values in a simulation process, which sounds like it might be what you want?

06:45 <DeVector[m]> Got it, so there is no other way of adding print statements in module itself, right?

06:47 <kivikakk[m]> not AFAIK

07:10 <d1b2> <jer_emy> @adamgreig can I make a suggestion for another example to add to your repo? Adding a verilog file into your build: https://lab.ktemkin.com/post/nmigen-instance/

07:22 <whitequark> kivikakk: or not yet, anyway; I have a few PRs implementing this functionality across the board (from Amaranth to Yosys) but unfortunately chronic illness happened so they've been sitting there since 2021 or something

10:37 <_whitenotifier-9> [amaranth-lang/amaranth] whitequark pushed 1 commit to main [+0/-0/±1] https://github.com/amaranth-lang/amaranth/compare/46e0a00a0860...5f6b36e91f44

10:37 <_whitenotifier-9> [amaranth-lang/amaranth] whitequark 5f6b36e - Add a workaround for python-poetry/poetry#7702.

10:38 <_whitenotifier-9> [amaranth-lang/amaranth-lang.github.io] whitequark pushed 1 commit to main [+0/-0/±27] https://github.com/amaranth-lang/amaranth-lang.github.io/compare/3345920e685e...2d69340183d1

10:38 <_whitenotifier-9> [amaranth-lang/amaranth-lang.github.io] whitequark 2d69340 - Deploying to main from @ amaranth-lang/amaranth@5f6b36e91f44c43bd7073fc94be239e795a12128 🚀

10:56 <_whitenotifier-9> [amaranth-lang/amaranth-boards] whitequark pushed 1 commit to main [+0/-0/±1] https://github.com/amaranth-lang/amaranth-boards/compare/ce26e35b5c07...42152283d98e

10:56 <_whitenotifier-9> [amaranth-lang/amaranth-boards] whitequark 4215228 - Add a workaround for setuptools erroring out on stale git checkouts.