Trying to run pants 1.29.0 on Mac OS X Big Sur #11305
Comments
|
@sentenza : Can you confirm that you are using the most recent version of the |
|
Hi! PS: I did take the opportunity to upgrade us to the latest launch script, didn't help. |
|
Same question for you @Xaelias - are you using the latest pants script from: https://pantsbuild.github.io/setup/pants ? The latest |
Yes sorry. I edited my comment after the fact but I did try to use an older version of the script which is our current default and the latest version of it. |
|
Erm - the OP shows pip is upgraded to 20.3.1 ..., thinking of more useful debugging questions to ask here. |
|
Ar right, its the plugin resolution that fails, not the pantsbuild.pants install. Unfortunately the plugin resolution is performed by Pex which is just now upgrading to latest Pip: pex-tool/pex#1133 |
|
I'm going to move up the Pex release schedule here so that we can un-break Big Sur users. |
|
Thanks! Yeah the diagnostic sounds about right. |
|
@Xaelias unfortunately, no. Pex vendors Pip into itself: https://github.com/pantsbuild/pex/tree/master/pex/vendor |
|
Yup that's what I was afraid of... Well thanks for the quick update :-) |
|
If you really need to hack around this now, you should be able to remove your plugins list from pants.toml (or comment it out), and add that same list into your checked-in |
|
Thanks I might give this a try. Otherwise, the only reason I need to run pants locally right now is really for a functionality that one of our internal apps should have either way. So I might just update the code of our app, let the pipeline build the pex that will then work on my machine, and go from there :-D |
So the problem was related to an outdated version of Pex shipped with pants. So far I tried using the latest version of pants with Python 3.7.9, 3.9., 3.8..
I'm going to try it out immediately. 🤞 |
So, I removed these plugins from pants.toml: plugins = [
'pantsbuild.pants.contrib.scrooge==%(pants_version)s',
'pantsbuild.pants.contrib.node==%(pants_version)s',
]I moved them into pants executable but I don't know how to pass this configuration anymore: [gen.scrooge]
service_deps = """{
'scala': [
'3rdparty/org/apache/thrift:libthrift',
'3rdparty/com/twitter:finagle-thrift',
'3rdparty/com/twitter:scrooge-core'
]
}"""
structs_deps = """{
'scala': [
'3rdparty/org/apache/thrift:libthrift',
'3rdparty/com/twitter:scrooge-core'
]
}"""@jsirois do you know how to keep using those scrroge config settings? |
|
@sentenza you should be able to keep the [gen.scrooge] settings as-is. You will need to replace the backend_packages.add = [
"pants.contrib.node",
"pants.contrib.scrooge",
] |
This pulls in support for macOS BigSur, the latest manylinux PEP (1) and Python 3.10. For the inital commit we do not expose the new pip-2020-resolver option and instead keep the status quo using the legacy resolver. 1) https://www.python.org/dev/peps/pep-0600/ Fixes pantsbuild#11305 [ci skip-rust] [ci skip-build-wheels]
This pulls in support for macOS BigSur, the latest manylinux PEP (1) and Python 3.10. For the inital commit we do not expose the new pip-2020-resolver option and instead keep the status quo using the legacy resolver. 1) https://www.python.org/dev/peps/pep-0600/ Fixes #11305 [ci skip-rust] [ci skip-build-wheels]
This pulls in support for macOS BigSur, the latest manylinux PEP (1) and Python 3.10. For the inital commit we do not expose the new pip-2020-resolver option and instead keep the status quo using the legacy resolver. 1) https://www.python.org/dev/peps/pep-0600/ Fixes pantsbuild#11305 [ci skip-rust] [ci skip-build-wheels]
This pulls in support for macOS BigSur, the latest manylinux PEP (1) and Python 3.10. For the inital commit we do not expose the new pip-2020-resolver option and instead keep the status quo using the legacy resolver. 1) https://www.python.org/dev/peps/pep-0600/ Fixes pantsbuild#11305 [ci skip-rust] [ci skip-build-wheels]
This pulls in support for macOS BigSur, the latest manylinux PEP (1) and Python 3.10. For the inital commit we do not expose the new pip-2020-resolver option and instead keep the status quo using the legacy resolver. 1) https://www.python.org/dev/peps/pep-0600/ Fixes #11305
This pulls in support for macOS BigSur, the latest manylinux PEP (1) and Python 3.10. For the inital commit we do not expose the new pip-2020-resolver option and instead keep the status quo using the legacy resolver. 1) https://www.python.org/dev/peps/pep-0600/ Fixes #11305
This pulls in support for macOS BigSur, the latest manylinux PEP (1) and Python 3.10. For the inital commit we do not expose the new pip-2020-resolver option and instead keep the status quo using the legacy resolver. 1) https://www.python.org/dev/peps/pep-0600/ Fixes pantsbuild#11305 [ci skip-jvm-tests]
This pulls in support for macOS BigSur, the latest manylinux PEP (1) and Python 3.10. For the inital commit we do not expose the new pip-2020-resolver option and instead keep the status quo using the legacy resolver. 1) https://www.python.org/dev/peps/pep-0600/ Fixes pantsbuild#11305 [ci skip-jvm-tests]
This pulls in support for macOS BigSur, the latest manylinux PEP (1) and Python 3.10. For the inital commit we do not expose the new pip-2020-resolver option and instead keep the status quo using the legacy resolver. 1) https://www.python.org/dev/peps/pep-0600/ Fixes #11305
Work towards pantsbuild#11305 # Rust tests and lints will be skipped. Delete if not intended. [ci skip-rust]
Work towards #11305# Delete this line to force CI to run Clippy and the Rust tests. [ci skip-rust-tests] # Delete this line to force CI to run the JVM tests. [ci skip-jvm-tests]
|
Alright @sentenza and @Xaelias, Pants 1.30.2rc3 is released with the Pex upgrade backport that includes Pip 20.3.3: https://pypi.org/project/pantsbuild.pants/1.30.2rc3/ The 1.30.x series is the last in the 1.x line so if you could try that release out and report back, I'd be grateful. I'm going to close this issue but as soon as I see some ACKs that that release works for one or both of you, I'll get a 1.30.2 final release cut. |
@jsirois |
|
Ah, sorry about that @sentenza. That looks like it's being emitted by Pex. You can silence by adding the following to your pants.toml: [GLOBAL]
ignore_pants_warnings = [
"Creating a LegacyVersion "
] |
|
@jsirois upgrading pants to v1.30.2: |
|
Alright, 1.30.2 is now released with the Pip upgrade at https://pypi.org/project/pantsbuild.pants/1.30.2/ so I'm going to close this out. |
|
@jsirois but I can still see: |
|
@sentenza yes, we released no fix for that. Instead you need to add the following to pants.toml: [GLOBAL]
ignore_pants_warnings = [
"Creating a LegacyVersion "
] |
I don't think that'd be necessary. It looked to me like that warning only happens when you install Pants for the first time. Try removing the snippet and running |
|
It happens every time you build a PEX (the warning is from the Pex resolver code: pex-tool/pex@a4a90ca). That is exposed in v1: https://travis-ci.com/github/pantsbuild/pants/jobs/463281661#L518 |
I'm on Mac OSX 11.0.1 using Python 3.8.2. I don't know how to solve this error:
Using
pipI can install pants 1.29.0 without any issueThe text was updated successfully, but these errors were encountered: