Ergonomic, hermetic, user-friendly software build system for Python, Go, Java, Kotlin, Protobuf, Scala, Shell. Pants lets you fearlessly scale up your codebase!

Pants

so that doesn’t necessarily mean its a fork.

we do the same thing for the non-ipython repl

<https://github.com/pantsbuild/pants/blob/master/src/python/pants/backend/python/tasks/python_repl.py#L52>

I’d have to dig through it but I’m 80% sure that we have some code somewhere that the version of python used to run pants impacts the user on their targets.

obviously we would have to isolate that to make migrating to py3 viable.

that being said there are some really nice features in py3 with exception handling, unpacking, type annotations, etc.

so it would be nice if we started moving that direction.

the plumbing is all there afaict - if you know of cases where it doesn’t line up it’d be good to file bugs.

we are semi-slowly moving our codebase to py3 but we won't be any help diagnosing pex issues

<@U054MQUPL>: with `--enable-v2-engine`, is the build graph still constructed in a fork but the stacktraces are brought back to main process?

the engine only surfaces exceptions right now

in the engine those are surfaced as `Throw` type

which just wraps the string exception now

looks like <https://github.com/pantsbuild/pants/issues/3506> is still happening for `python_tests` targets in source - but not OSS. I wonder if one of our plugins or CAOF/TargetMacro things is mucking this up.

<@U054MQUPL>: hm... all of them, or just some?

just the ones with `resources=*globs(…)`

`./pants --enable-v2-engine list managed-development-environment::`