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

Pants

related: this is probably exactly why google implemented skylark.

oh. in the sense that it's not a "real" python interpreter?

(nevermind, wasn't the unicode/str thing... something else)

```80026370616e74732e6275696c645f67726170682e616464726573730a416464726573730a7101298171027d71032855055f686173687104492d383938363631383632323932353831383834370a550c5f7461726765745f6e616d657105580600000073696d706c65         550a5f737065635f70617468710 6 58190000007372632f7468726966742f636f646567656e2f73696d706c6575622e
80026370616e74732e6275696c645f67726170682e616464726573730a416464726573730a7101298171027d71032855055f686173687104492d383938363631383632323932353831383834370a550c5f7461726765745f6e616d657105580600000073696d706c65  7106   550a5f737065635f70617468710 7 58190000007372632f7468726966742f636f646567656e2f73696d706c6575622e```

and unfortunately doesn't show up with the ascii pickle protocol

so, either of the binary pickle protocols show a mismatch here. ascii doesn't

Sorry I've only been following this very loosely

But are we trying to use pickle as a byte-consistent serializer?

yea, not planning on using pickle in the long term. but was hoping it would be saneish in the short term

i don't want to get into schema'd data anytime soon, but it seems like a bit of an inevitability

<@U054MQUPL>: assigned you <https://github.com/pantsbuild/pants/issues/2965> ...

...but two things: 1) try not to think about serialization yet, unless it's obvious that we want to be using a particular rpc framework, 2) definitely don't think about membership

re: (1): pickle will not be a long term solution. but it'll do for the next month at least.

some of that is to do with communication protocols, some is probably to do with fs/scm

<@U06A03HV1>: <https://pythonhosted.org/six/#six.binary_type>

literal strings in python are all memoized