Hey, how ready is Pants to package and distribute as a pex targeting Python 3.7? We are going to try to land an upgrade to Python 3.7 in our monorepo, but we'd have to keep any Pants plugin-related targets behind on 3.6 until Pants can internally can run with 3.7

and to be clear, you mean "pants itself", rather than targets that pants is building

right

Ready! But it means our CI is going to be slowed down quite a bit by adding two bootstrap shards and one wheel building shard. If we could drop Centos6, it would be less painful by being able to use the same shard to do both Py36 and Py37. We’re just waiting on Twitter to drop Centos6

@hundreds-father-404: producing a 3.7 whl doesn't require the bootstrap shards, does it? So wouldn't this just be the one extra shard?

Oh good point!

Awesome!

@strong-crayon-70379: if you have time to help with that, it would be appreciated. Eric's time is pretty limited

sgtm

I could get it to it this weekend! Don’t think it will be a big diff. You’ll change generate_travis_yml.py and it will mostly be the same as the Py36 version, but need to use Centos7

We're running pants itself on 3.7 internally with no issues, just fyi. I guess we're bootstrapping the 36 wheel successfully on 3.7?

Oh hm realized the challenging / tedious part of this is adding Py37 to

release.sh

. We need to not only add the wheel building shards, but also new deploy shards to actually deploy the Py37 pex Edit: actually, I think we can just release a Pex that works with Py36 and Py37.

My guess is we already are, since we're running it on py37 with no issues?

are you consuming the pex, or via virtualenv/pip?

pip+venv