different resolves & interpreter constraints are doing my noggin in. previously, both my (embedded) runtime and pants were running python3.9, which was convenient. But now my runtime has upgraded to 3.10, and pants 3.11. which made having in-repo plugins a bit ... painful. I ended up with a macro

pants_plugin_sources

that sets the resolve & interpreter constraints to the right one for pants. and a

runtime_sources

that sets the resolve & interpreter for my runtime. everything seems to work. Until you add a

match/case

statement, and then it's a bit ... weird. i.e. today

black

failed with "Invalid syntax <unknown>, line <match statement>... blablabla older Python version." when doing

fmt ::

Then doing

pants fmt a/b/c/file.py

on that same file worked fine. and then subsequent calls to

fmt ::

work fine. It's like, pants is picking an old 3.9 version of Python to use sometimes. Despite not having 3.9 as a resolve or interpreter any more

For black specficially, are you setting the target version? https://black.readthedocs.io/en/stable/usage_and_configuration/the_basics.html#t-target-version

I use

__defaults__

to set pants-plugins to a different interpreter constraint than the rest of the repo. I keep the pants-plugins code isolated from the rest of the code in the repo - so the pants-plugins code does not import the rest of the app code. It can run specific targets (say a script) that is in the default resolve, but it does not import that script. You can see that here: https://github.com/StackStorm/st2/blob/master/pants-plugins/BUILD And these two blocks are how I run a script from the other resolve within one of the pants plugins: • https://github.com/StackStorm/st2/blob/master/pants-plugins/sample_conf/subsystem.py#L37-L43 • https://github.com/StackStorm/st2/blob/master/pants-plugins/sample_conf/rules.py#L61-L72

this might, yes