See https://www.pantsbuild.org/docs/upgrade-tips#ignore-deprecation-messages-with-ignore_pants_warnings for an example. There’s also a known issue that the Pants daemon doesn’t respect the flag. What Pants version are you using? That changes if the daemon is on or off by default.

im using a pretty old version, 1.16

and struggling to get groovy and jenkins to escape the *

oh no! i'm super sorry about that

WRT to https://github.com/pantsbuild/pants/pull/10412/files/370eb1d6ecc6e14b56dd0486c6f998a107c6cff1#diff-d9186603649fd9af3af07a4c6f523c4f

Hi friends! been having a hell of a time with the pex resolver in 1.29.0 and an apache-airflow dependency. This might be a pex bug so let me know if i should take it elsewhere

This message was deleted.

sorry posted in wrong org 🤦

np!!

I’ve got a pretty big monorepo and I need to update one of it’s 3rd party dependency which most of the services rely on. Is there any way to only update the dependency for a single service via shading?

which language are we talking about?

scala

@melodic-optician-41260: there isn’t a built in facility for doing it, but you can do it manually either with

jarjar

, or in pants 1.x you can do build the shaded as a one-off by creating a

jvm_binary

with a shading config

got a great suggestion from kelsey blair who works on python at twitter to: - if a dependency spec in a BUILD file or on the command line matches case-insensitively (and/or by levenshtein/edit distance?), - raise an error that points to the correct file or target spec @hundreds-father-404 and anyone else: do you have thoughts on this proposed feature? we're not planning to try to backport this, it would just be a new pants feature.

Hello all! I just downloaded Pants for the first time today and I'm struggle to get a simple example to work.

For context, I'm looking to switch over from Please.build, and I have a little previous experience with Bazel.

Screen Shot 2020-07-24 at 9.41.02 PM.png

Does anyone know if there is a way to run multiple goals in loop mode at the same time? I'd like to have a loop running for test, lint, and typecheck against all targets, all the time. (Pants 2.0)

Thoughts on getting rid of

Optionable

as a separate thing and merging it into

Subsystem

(now that the latter is the only

Optionable

) Vs. keeping those as separate concepts? Would require moving

subsystem.py

to

src/python/pants/option

.

This is probably a bit of a nebulous question, but was there any parallelization added to unit test running between pants 1.8 and 1.26? For some context, I have a few transient unit test failures that are occurring, but only when I run our entire test suite from scratch. Trying to pin down what might be causing these issues.

Evaluating Pants and really like it. One final step that would make me really happy with development setup would be IDE integration. Is there a way, one can export a virtual environment with all 3rd party deps and python_library rules defined? In version 1.30.0, tried using setup-py goal to do it, but its just stuck after "[INFO] Completed: Find all code to be published in the distribution". Thought using setup-py will be able to deploy all python_library in develop mode in virtualenv and make it available to IDE's python interpreter. Any help would be appreciated.

Which IDE are you working with?

we have a script inside of twitter to create a virtualenv from a pex file and we're planning to develop in the next year or earlier an LSP server that consumes a PEX file to serve completions

would love to sync up any efforts on that if it would be useful

looks like eric already got me: https://pantsbuild.slack.com/archives/C046T6T9U/p1596046544322600?thread_ts=1596046452.319900&cid=C046T6T9U

Oh, hah, I forgot we already had some info on this

Yes, I went through it. Isn't it for 3rdparty deps only? I wanted to get python_library rules included as well and tried the setup-py way and that hangs in 1.30 version. Just now found the issue #10291. Its status is closed, but I assume it is part of 2.0.0 and not part of 1.30.0 yet

In the process of upgrading to 2.0 to try it out

Is there a way to get a version number into a `BUILD`'s target? We are evaluating different ways of adding metadata to our projects and debating if it is worth adding other files.