@hundreds-father-404 is there a way to tell the flake8 linter to ignore whole directories (i.e. pants targets), configuring excludes in the flake8 config file pants uses has no effect since in v2, pants passed a list of .py files for flake8 to process.

https://github.com/pantsbuild/pants/pull/9403 some minor junit runner cleanup

the thing I’m working towards is https://github.com/pantsbuild/pants/pull/6203

Hi all! 👋 Our CI jobs that test Pants with Metals (Scala language server) started failing with the following error

/usr/bin/python3.6: can't open file '/home/runner/.cache/pants/setup/bootstrap-Linux-x86_64/virtualenv-16.4.3/virtualenv.py': [Errno 2] No such file or directory

Any idea what might cause this issue? I think it was working OK a week ago

Hey everyone 😄 Hope ya'll are doing okay I've hit an issue that is causing pantsbuild to not be able to run the goal [conan-prep]. So after running a pants clean-all and wiping the caches, configparser upgraded it's version to 5.0.0 which is only python 3 compatible; however, we're on pants 1.14.0 and using python 2. Is there a way we can pin the version of configparser 4.0.2 somewhere -- possibly in the pants.ini file? This started failing the day configparser 5.0.0 came out.

Package SourcePackage(u'file:///Users/<name>/.cache/pants/python_cache/requirements/CPython-2.7.16/configparser-5.0.0.tar.gz') is not translateable by ChainedTranslator(WheelTranslator, EggTranslator, SourceTranslator)

Any idea for any actions I can do to patch this? Thanks ahead of time for any help!!

found a subtle ordering bug in

BlockJUnit4ClassRunnerWithRetry

that explains some weird behavior Ive been frustrated with

pants version:

pants_version = "1.27.0.dev1"

With V2 engine, is there a way to config my pants.toml so that it will default

ipython

instead of

python

for Python

repl

? Also, I saw that there was a lot discussion about having a single

repl

goal V.S. one goal per implementation. However, with the version I am having right now, I still only see a single

repl

goal from

./pants gals

. Is this settled? Or still subject to change.

Hey, I'm trying to add

pytest.ini

to my test folder. When I run

pants test

i get an error from pytest: "ERROR: not found <path to pytest.ini> (no name <path to pytest.ini> in any of [])"

how do I suppose to add pytest.ini?

here is my BUILD file for test

python_tests(
    name="my-tests",
    sources=["a/b/tests/*"],
    dependencies=[":lib"]
)

pytest.ini

is located in "a/b/tests/pytest.ini"

@hundreds-father-404 another question,

pants_version = "1.27.0.dev1"

default

zip_safe

to

true

for python_binary? (Used to be

false

for earlier version). Is it configurable for a given target? Or a global overwrite in

pants.toml

?

Hey, I'm trying to upgrade pants from 1.17.0 to 1.25.0, I have updated the

pants_version

, migrated my pants.ini to pants.toml. Now none of my custom plugins are working

name 'docker_python_image' is not defined

, where docker_python_image is supplied by a pants plugin

would recommend moving version by version so that you see deprecation warnings.

looking through my register.py I see nothing broken and it doesn't even seem to be evaluated

@witty-crayon-22786, ok, will try that, thanks!

for what it’s worth I noticed the same thing when switching to the

pants.toml

my custom plugins were not getting used with the change that the automated converter did, but because I was upgrading to 1.25.0 and it seems like 1.26 is when toml is supposed to go live(?) I just reverted to using .ini and didn’t say anything

Huh, interesting, I’m sorry you both ran into these issues with the

pants.toml

migration! Thank you for reporting it. My first instinct would be if you are using string interpolation like

%(my_interpolated_string)s

, perhaps? TOML is supposed to work with that, but perhaps there is an edge case we missed.

Oh, also, are you all using

pants.toml

in 1.25.0 or 1.26.0?

pants.toml

only works from 1.26.0+

my backend packages post migration looked like

backend_packages: [ 'package1', 'package2' ]

, didn't look right, moved it to

backend_packages = [...]

that didn't help though I was testing it in pants 1.24 and 1.25

Trying to remember why I went for the migration, I saw a warning message somewhere that prodded me towards migrating to pants.toml

but basically what you are saying is I was running without a pants configuration and that is why I got no backend packages 🙂

We sent an email in pants-devel encouraging people to migrate in 1.26.0 but not requiring it. We should have done a better job highlighting that this requires 1.26.0+

but basically what you are saying is I was running without a pants configuration and that is why I got no backend packages 🙂

Exactly what the issue is. Pants won’t complain about

pants.toml

in 1.25.0 because it’s just another random file in your repository. Whereas in 1.26.0, Pants knows how to read it.

I'll just stay with pants.ini until 1.26 is out, thanks for your help @hundreds-father-404, @lively-france-2777 and @witty-crayon-22786 ❤️

Sounds good! I hope you do end up using

pants.toml

in 1.26 - while it’s not required, we’ve found it makes several improvements and removes a lot of gotchas that even us Pants developers would get caught by. Thanks for reporting this and I’m glad we got it working!

Mypy question: I have the following code:

if isinstance(current_target, JvmTarget):
            # Some code...
            if isinstance(current_target, RuntimePlatformMixin):
                info["runtime_platform"] = current_target.runtime_platform.name

In CI, mypy complains that:

src/python/pants/backend/project_info/tasks/export_dep_as_jar.py: note: In member "_process_target" of class "ExportDepAsJar":
src/python/pants/backend/project_info/tasks/export_dep_as_jar.py:319:17: error:
Statement is unreachable  [misc]
                    info["runtime_platform"] = current_target.runtime_plat...
                    ^

Which is apparently a thing in the presence of multiple inheritance https://github.com/python/mypy/issues/3603 Is it okay to skip typechecking in this line, with a reference to the issue (or one of the follow ups, since that one is closed)? cc\ @hundreds-father-404

Is there a way to verbose when building python library/binary the "building" command with pex? or does pants uses pex python API and not using directly pex tool?