@brandjon Can you take a look? I think this patch is an important fix.

@brandjon @lberki any thoughts at all? I realize my fix may not be the preferred way to address this, but I'd love to see this addressed one way or another, so that we can get rid of our local fork of rules_python.

Hi @brandjon. Please let us know if this project is maintained, or we should move to something else. There are multiple PRs and issues that are not answered for months.

Importing pip packages doesn't work, using python3 is even in a worst state.

Any updates on this pull request? Using Bazel in conjunction with python3/pip seems pretty painful without this. @brandjon

I second @cgordoncarroll. Is there a way we could help to push this PR forward?

Would be very interested in this being merged as well. Trying to use Bazel with Python3 deps.

@smamessier

Have you tried any of these?

• https://github.com/dillon-giacoppo/rules_python_external
• https://github.com/soniaai/rules_poetry
• https://github.com/ali5h/rules_pip

They all support Python 3. We are using the 1st with Python 3.6 at work. It was created after bazelbuild/rules_python just wouldn't work for us.

@thundergolfer Thanks I ended up using https://github.com/dillon-giacoppo/rules_python_external and it works perfectly.

We found a Contributor License Agreement for you (the sender of this pull request), but were unable to find agreements for all the commit author(s) or Co-authors. If you authored these, maybe you used a different email address in the git commits than was used to sign the CLA (login here to double check)? If these were authored by someone else, then they will need to sign a CLA as well, and confirm that they're okay with these being contributed to Google.
In order to pass this check, please resolve this problem and then comment @googlebot I fixed it.. If the bot doesn't comment, it means it doesn't think anything has changed.

ℹ️ Googlers: Go here for more info.

@googlebot I fixed it.

CLAs look good, thanks!

ℹ️ Googlers: Go here for more info.

👋 1-year anniversary for this PR is coming up. Any chance we could get it merged?

/cc @thundergolfer @andyscott

Thanks a lot @andyscott! Would you like me to do anything else here? (The build of your merge failed because of an unrelated issue already fixed at head, afaict).

We found a Contributor License Agreement for you (the sender of this pull request), but were unable to find agreements for all the commit author(s) or Co-authors. If you authored these, maybe you used a different email address in the git commits than was used to sign the CLA (login here to double check)? If these were authored by someone else, then they will need to sign a CLA as well, and confirm that they're okay with these being contributed to Google.
In order to pass this check, please resolve this problem and then comment @googlebot I fixed it.. If the bot doesn't comment, it means it doesn't think anything has changed.

ℹ️ Googlers: Go here for more info.

CLAs look good, thanks!

ℹ️ Googlers: Go here for more info.

Hi! @thundergolfer @andyscott I removed the .par files from the PR, and squashed the commits. Is there anything else I should do here? Thank you!

Hi rules_python folks. Is there any chance this gets merged?