whitequark[cis] changed the topic of #amaranth-lang to: Amaranth hardware definition language · weekly meetings: Amaranth each Mon 1700 UTC, Amaranth SoC each Fri 1700 UTC · play https://amaranth-lang.org/play/ · code https://github.com/amaranth-lang · logs https://libera.irclog.whitequark.org/amaranth-lang · Matrix #amaranth-lang:matrix.org
Degi_ has joined #amaranth-lang
Degi has quit [Ping timeout: 248 seconds]
Degi_ is now known as Degi
<_whitenotifier-4> [amaranth] jfng closed pull request #1533: rpc: add support for `wiring.Component`. [0.5 backport] - https://github.com/amaranth-lang/amaranth/pull/1533
<_whitenotifier-4> [amaranth] jfng reopened pull request #1533: rpc: add support for `wiring.Component`. [0.5 backport] - https://github.com/amaranth-lang/amaranth/pull/1533
frgo_ has joined #amaranth-lang
frgo has quit [Read error: Connection reset by peer]
tpw_rules has quit [Excess Flood]
cyrozap has quit [Remote host closed the connection]
tpw_rules has joined #amaranth-lang
cyrozap has joined #amaranth-lang
jfng[m] has joined #amaranth-lang
<jfng[m]> not sure why this CI run fails
<jfng[m]> could it be because amaranth main (which requires ~=3.9) runs the amaranth-boards CI (which requires ~=3.9), but the amaranth-boards CI matrix includes amaranth 0.4 (which requires ~=3.8) ?
whitequark[cis] has joined #amaranth-lang
<whitequark[cis]> yeah, something like that
<whitequark[cis]> it's really unfortunate
<jfng[m]> ok, let's try removing 0.4 from the -boards matrix
<jfng[m]> ah, but idk if dropping -boards support for amaranth 0.4 is fine
<jfng[m]> codebases that depend on 0.4 won
<jfng[m]> 't be able to fallback on a previous -boards release, as they aren't any
<jfng[m]> otoh, that's already the case for amaranth-soc (>=0.5,<0.6)
<whitequark[cis]> yeah
<_whitenotifier-4> [amaranth-boards] jfng opened pull request #251: Drop compatibility with Amaranth 0.4. - https://github.com/amaranth-lang/amaranth-boards/pull/251
<_whitenotifier-4> [amaranth-boards] jfng edited pull request #251: Drop compatibility with Amaranth 0.4. - https://github.com/amaranth-lang/amaranth-boards/pull/251
<jfng[m]> done, hopefully
<_whitenotifier-4> [amaranth-boards] whitequark closed pull request #251: Drop compatibility with Amaranth 0.4. - https://github.com/amaranth-lang/amaranth-boards/pull/251
<_whitenotifier-4> [amaranth-lang/amaranth-boards] whitequark pushed 1 commit to main [+0/-0/±3] https://github.com/amaranth-lang/amaranth-boards/compare/d2caa61a1ceb...23c66d680458
<_whitenotifier-4> [amaranth-lang/amaranth-boards] jfng 23c66d6 - Drop compatibility with Amaranth 0.4.
<_whitenotifier-4> [amaranth] jfng closed pull request #1533: rpc: add support for `wiring.Component`. [0.5 backport] - https://github.com/amaranth-lang/amaranth/pull/1533
<_whitenotifier-4> [amaranth] jfng reopened pull request #1533: rpc: add support for `wiring.Component`. [0.5 backport] - https://github.com/amaranth-lang/amaranth/pull/1533
<jfng[m]> oh well..
frgo_ is now known as frgo
<whitequark[cis]> I think you might have to pin amaranth-boards in that branch to an earlier git release
<jfng[m]> so i guess -soc and -stdio should be pinned too ?
<whitequark[cis]> I think so
<jfng[m]> ok this worked! auto-merge needs to be re-enabled
<jfng[m]> then 0.5.3 can be released o/
<_whitenotifier-4> [amaranth] whitequark closed pull request #1533: rpc: add support for `wiring.Component`. [0.5 backport] - https://github.com/amaranth-lang/amaranth/pull/1533
<_whitenotifier-4> [amaranth-lang/amaranth] whitequark tagged 3857822 as v0.5.3 https://github.com/amaranth-lang/amaranth/commit/3857822b714b9a1e2efee62d7c19841c0818aa79
<_whitenotifier-4> [amaranth] whitequark created tag v0.5.3 - https://github.com/amaranth-lang/amaranth
<_whitenotifier-4> [amaranth-lang/amaranth-lang.github.io] whitequark pushed 1 commit to main [+160/-0/±0] https://github.com/amaranth-lang/amaranth-lang.github.io/compare/d0a47a9c3a15...672201b07f96
<_whitenotifier-4> [amaranth-lang/amaranth-lang.github.io] whitequark 672201b - Deploying to main from @ amaranth-lang/amaranth@3857822b714b9a1e2efee62d7c19841c0818aa79 🚀
<_whitenotifier-4> [amaranth] github-actions[bot] published v0.5.3 | 0.5.3 - https://github.com/amaranth-lang/amaranth/releases/tag/v0.5.3
Wanda[cis] has quit [Quit: Idle timeout reached: 172800s]
eigenform[m] has joined #amaranth-lang
<eigenform[m]> i don't know if this is an amaranth question or a general python question but: can I programmatically generate an `enum.Enum` that has a shape, instead of using `class Foo(enum.Enum, shape=)`
<eigenform[m]> * an `amaranth.lib.enum.Enum` that
<whitequark[cis]> note that you can use class: statement inside functions
<whitequark[cis]> ```
<whitequark[cis]> def foo(shape):
<whitequark[cis]> class Foo(enum.Enum, shape=shape):
<whitequark[cis]> this is allowed
<eigenform[m]> Ooooo I see, thank you!!
<eigenform[m]> mmm, I think what I'm trying to do is generate an enum with dynamic members and a dynamic shape. I thought I might be able to do some incantation of `EnumType.__new__`, but maybe not?
<vup> I guess you are running into https://github.com/amaranth-lang/amaranth/issues/1535 then? That includes a workaround.
<eigenform[m]> mm, looks like it! weird that i didnt notice that issue when I was looking, thank you!