Python 3.11 vs from inspect import getargspec

[Christian-B]

Use getfullargspec() for an updated API that is usually a drop-in replacement, but also correctly handles function annotations and keyword-only parameters.

Note: not critical as we have now removed all dependencies for rig in our project

[mossblaser]

Thanks very much for sending this in! Out of curiosity how did you happen across this -- I dimly recall rig only used the various introspection things for some of its own API idiosyncrasies? Is someone still dutifully running the rig test suite against new Pythons or are you doing some of the same tricks?

(Separately, how is the world of SpiNNaker software these days? Is there somewhere I can read to catch up on what's been going on over the last <many> years? :))

[Christian-B]

We continuously test all spinnaker repositories using github actions against a list of python versions. Until recently spalloc still had rig listed as a test requirement. The install went boom.

…

________________________________ From: Jonathan Heathcote ***@***.***> Sent: 07 December 2022 12:54 To: project-rig/rig ***@***.***> Cc: Christian Brenninkmeijer ***@***.***>; Author ***@***.***> Subject: Re: [project-rig/rig] Python 3.11 vs from inspect import getargspec (Issue #271) Thanks very much for sending this in! Out of curiosity how did you happen across this -- I dimly recall rig only used the various introspection things for some of its own API idiosyncrasies? Is someone still dutifully running the rig test suite against new Pythons or are you doing some of the same tricks? (Separately, how is the world of SpiNNaker software these days? Is there somewhere I can read to catch up on what's been going on over the last <many> years? :)) — Reply to this email directly, view it on GitHub<#271 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AAEF4ZNVO4U5OAAXW2NGWELWMCCJPANCNFSM6AAAAAASQNUTY4>. You are receiving this because you authored the thread.Message ID: ***@***.***>