Reminder about our developer survey: https://toolcha.in/survey2021b . If you haven't filled it out yet (👋 new folks!) please consider doing so, as the data will be really helpful in guiding the project priorities over the next several months.

Responded in thread above already

removed an integration from this channel: Travis CI

Welp, I guess that makes it official, even though it already happened. End of an era. Bye, Travis CI.

Is it possible to manually define additional dependencies for a third-party dependency somehow? I have a third-party dependency (

mongomock

) that requires

setuptools

to work, but it isn't defined as a requirement and thus not added to the pex by Pants. Right now I work around it by explicitly adding

setuptools

as a dependency to all the

python_library()

with code that uses

mongomock

, but it would be nice if I somehow could tell Pants to always pull in

setuptools

when something wants

mongomock

.

As you may know: A) a target with no name defaults to the name of the dir it's in, and B)

path/to/dir

on the cmd line or in BUILD target

dependencies

is currently shorthand for

path/to/dir:dir

. These are legacies from v1. However in v2's file-centric world, we want

path/to/dir

on the cmd line to mean "all the files under `path/to/dir`" (this is what it means for pretty much every underlying tool). And, in that proposed future, we're pondering what

path/to/dir

should mean in BUILD target

dependencies

. Basically, we're wondering about how to get from here to there, and how much deprecation to do. This affects existing users, so we welcome your opinions: https://github.com/pantsbuild/pants/issues/12286

Is there a way to specify pytest plugins below the root level? I'm working in a codebase with a lot of django code, but also plenty non django code. If I put

[pytest]
pytest_plugins.add = [
     "pytest-django",

in my

pants.toml

all the non django tests complain about not finding django settings

https://twitter.com/pantsbuild/status/1429902637906997254 We truly do ❤️ when you do this. Twitter The real heroes are the folks who go back to the GitHub issue they filed and post the solution Twitter

https://twitter.com/pantsbuild/status/1429934825864056836 We value all contributions to Pants project, code or not. In fact, some of the most valued contributions we get are from early adopters of any new feature. You give us crucial feedback, uncover bugs, and help us ensure Pants stays focused on the real-world challenges you work on. Twitter

hmmm is there a way to specify that some dependencies shouldn’t regularly be inferred? I would kind of not like to include everything that is being used for type checking

We're working on outreach in communities where future Pants fans hang out. You can help us to identify where to find people who share your interests and concerns. What are your favorite-- • podcasts • websites • subreddits • meetups • conferences • newsletters • forums/Slacks/Discords • etc Technical ones of course, but also non-technical ones are welcome. Thanks for helping grow the Pants community and spread developer joy!

hey folks! if you’re using Pants and are comfortable having your company/organization added to a users page that we’re kicking off, please go to https://pantsbuild.org/register, which will help you to open a github issue! only two required fields.

https://twitter.com/ElJefeDSecurIT/status/1429921704948600845 Pants Build retweeted: wow. that's just my technical phone screen. Twitter Companies- Why can’t we find anyone to hire? Their interview process- Twitter

hey everyone, happy wednesday! i’m not sure if this is where we ask questions, but I was hoping somebody could help me with this issue.. I’m trying to import a project into Intellij and I see errors like this — would ANYBODY possible know how to resolve this? thank you so muchh

Hello all, thanks to all for previous help. Have a monorepo. Have finally given up trying to fit Pants with PEP420 implied namespace pacakges. I'm using the pkgutil namespace package with the magic init.py under each '*hankai*' namespace that contains:

__path__ = __import__("pkgutil").extend_path(__path__, __name__)  # type: ignore

However, in a simplified pants-test setup I cannot pants to do what I think it ought too. It's been a very frustrating and quite time consuming attempt to adopt Pants. I feel like I'm so close to a working setup and then no matter what I do it seems to work as expected in many ways and then falls over in others. (And vice versa when I setup with PEP420; mypy works in all and pylint fails - opposite to the pkgutil namespace setup). The Pants docs, while referencing namespace packages, wasn't enough for me to glean the best way. Maybe another monorepo user might have some wisdom on the matter? (TY) . ├── mypy.ini ├── pants ├── pants.toml ├── pylintrc ├── pyproject.toml └── src └── python ├── hankai-dep (depends hankai-util) │ ├── BUILD │ ├── hankai │ │ ├── init.py │ │ └── dep │ │ ├── init.py │ │ └── dep.py │ ├── poetry.lock │ ├── poetry.toml │ ├── pyproject.toml │ └── requirements.txt └── hankai-util (independent) ├── BUILD ├── hankai │ ├── init.py │ └── util │ ├── init.py │ └── util.py ├── poetry.lock ├── poetry.toml ├── pyproject.toml └── requirements.txt hankai-util is independent, hankak-dep is dependent on hankai-util src/python/hankai-util/BUILD python_requirements() python_library( name="lib", dependencies=[ ":loguru", ":pydantic", ], sources=[ "hankai/**/*.py", ] ) src/python/hankai-dep/BUILD python_requirements() python_library( name="lib", dependencies=[ ":loguru", ":pydantic", "src/python/hankai-util:lib", ], sources=[ "hankai/**/*.py", ] ) ---------------------- LIST ./pants list :: src/python/hankai-dep:colorama src/python/hankai-dep:dist src/python/hankai-dep:lib src/python/hankai-dep:loguru src/python/hankai-dep:pydantic src/python/hankai-dep:requirements.txt src/python/hankai-dep:typing-extensions src/python/hankai-dep:win32-setctime src/python/hankai-util:colorama src/python/hankai-util:dist src/python/hankai-util:lib src/python/hankai-util:loguru src/python/hankai-util:pydantic src/python/hankai-util:requirements.txt src/python/hankai-util:tqdm src/python/hankai-util:typing-extensions src/python/hankai-util:win32-setctime ---------------------- DEPENDENCIES/DEPENDEES ./pants dependencies :: src/python/hankai-dep/hankai/__init__.py:../lib src/python/hankai-dep/hankai/dep/__init__.py:../../lib src/python/hankai-dep/hankai/dep/dep.py:../../lib src/python/hankai-dep:loguru src/python/hankai-dep:pydantic src/python/hankai-dep:requirements.txt src/python/hankai-util/hankai/__init__.py:../lib src/python/hankai-util/hankai/util/__init__.py:../../lib src/python/hankai-util/hankai/util/util.py:../../lib src/python/hankai-util:dist src/python/hankai-util:loguru src/python/hankai-util:pydantic src/python/hankai-util:requirements.txt ./pants dependencies src/python/hankai-_dep_:lib src/python/hankai-dep/hankai/__init__.py:../lib src/python/hankai-dep/hankai/dep/__init__.py:../../lib src/python/hankai-dep/hankai/dep/dep.py:../../lib src/python/hankai-dep:loguru src/python/hankai-dep:pydantic src/python/hankai-util/hankai/__init__.py:../lib src/python/hankai-util/hankai/util/__init__.py:../../lib src/python/hankai-util/hankai/util/util.py:../../lib ./pants dependencies src/python/hankai-util:lib src/python/hankai-util/hankai/__init__.py:../lib src/python/hankai-util/hankai/util/__init__.py:../../lib src/python/hankai-util/hankai/util/util.py:../../lib src/python/hankai-util:loguru src/python/hankai-util:pydantic ./pants dependees src/python/hankai-util:lib src/python/hankai-dep:lib src/python/hankai-dep/hankai/__init__.py:../lib src/python/hankai-dep/hankai/dep/__init__.py:../../lib src/python/hankai-dep/hankai/dep/dep.py:../../lib src/python/hankai-util:dist ---------------------- LINT *./pants lint :: (*Successful) ./pants lint src/python/hankai-util:lib (Successful) ./pants lint src/python/hankai-dep:lib (FAILS) - Expected that the hankai-util deps would be referenced since ./pants knows about them as shown above. src/python/hankai-dep/hankai/dep/dep.py20: E0611: No name 'util' in module 'hankai' (no-name-in-module) src/python/hankai-dep/hankai/dep/dep.py20: E0401: Unable to import 'hankai.util' (import-error) src/python/hankai-dep/hankai/dep/dep.py158: E1101: Module 'hankai' has no 'util' member (no-member) ./pants lint src/python/hankai-dep:lib src/python/hankai-util:lib (Successful) - But I expected the explicit dependency to be used and to not have to directly reference it. ---------------------- TYPECHECK ./pants typecheck :: (FAILS) - I'm not doing PEP420. Using pkgutil namespace packaging. How am I supposed to use pants with any form of namespace package support?? src/python/hankai-util/hankai/__init__.py: error: Duplicate module named "hankai" (also at "src/python/hankai-dep/hankai/__init__.py") src/python/hankai-util/hankai/__init__.py: note: Are you missing an init.py? Alternatively, consider using --exclude to avoid checking one of them. Found 1 error in 1 file (errors prevented further checking) ./pants typecheck src/python/hankai-util:lib (Successful) ./pants typecheck src/python/hankai-dep:lib (FAILS) - Expected the hankai-util deps would be referenced since ./pants knows about them as shown above. src/python/hankai-dep/hankai/dep/dep.py21: error: Cannot find implementation or library stub for module named "hankai.util" [import] import hankai.util ^ src/python/hankai-dep/hankai/dep/dep.py21: note: See https://mypy.readthedocs.io/en/stable/running_mypy.html#missing-imports Found 1 error in 1 file (checked 3 source files) ./pants typecheck src/python/hankai-dep:lib src/python/hankai-util:lib (FAILS) as before with :: src/python/hankai-util/hankai/__init__.py: error: Duplicate module named "hankai" (also at "src/python/hankai-dep/hankai/__init__.py") src/python/hankai-util/hankai/__init__.py: note: Are you missing an init.py? Alternatively, consider using --exclude to avoid checking one of them. Found 1 error in 1 file (errors prevented further checking) ============================================ I feel like I'm so close to a working but am just not getting there. Maybe another monorepo user might have some wisdom on the matter? Thank you all for your consideration and help.

https://twitter.com/pantsbuild/status/1430565742915768324 Pants 2.5.2 is available pypi.org/project/pantsb… Twitter

Anyone else see pants inconsistently print failed test output?

[test]
output = "failed"

./pants test src/clr_commands/tests/test_data.py -- -v
09:19:08.63 [INFO] Initializing scheduler...
09:19:08.96 [INFO] Scheduler initialized.

𐄂 src/clr_commands/tests/test_data.py failed.

Without changing anything, just repeating the command:

./pants test src/clr_commands/tests/test_data.py -- -v
09:19:52.63 [INFO] Initializing scheduler...
09:19:52.92 [INFO] Scheduler initialized.
09:20:23.48 [WARN] Completed: test - src/clr_commands/tests/test_data.py failed (exit code 2).
============================= test session starts ==============================
platform linux -- Python 3.6.14, pytest-6.2.4, py-1.10.0, pluggy-0.13.1 -- /home/mpcusack/.cache/pants/named_caches/pex_root/venvs/short/c0a2e079/bin/python3.6
cachedir: .pytest_cache
rootdir: /tmp/process-execution1bzNig, configfile: pyproject.toml
plugins: circleci-parallelized-0.0.4, profiling-1.7.0, celery-4.4.7, cov-2.11.0, ddtrace-0.48.0
collecting ... collected 0 items / 1 error


==================================== ERRORS ====================================
_____________ ERROR collecting src/clr_commands/tests/test_data.py _____________
...truncated...
𐄂 src/clr_commands/tests/test_data.py failed.

re-bumping https://pantsbuild.slack.com/archives/C046T6T9U/p1629839552346400! (we got some excellent highly detailed questions which pushed it out of view!)

Bumping this https://pantsbuild.slack.com/archives/C046T6T9U/p1629837509344900

https://twitter.com/pantsbuild/status/1430640919083196425 Does your build give you headaches? Try Pants, the fast, flexible, scalable build system. pantsbuild.org/docs Pants is OSS & the team pays close attention to community feedback. So as you explore, know you're always invited to offer suggestions, make requests, & open PRs. ❤️ https://t.co/ob3J8MfGhL Twitter

https://twitter.com/pantsbuild/status/1430665783311572999 Love to see exciting new projects emerge! Twitter Big project, first public release! 📢 ✨ SQLModel ✨ ...the biggest thing I've built since FastAPI & Typer. 🤓 SQL D… twitter.com/i/web/status/1… Twitter

https://twitter.com/pantsbuild/status/1430673250334486539 🤣🤣🤣 Twitter OH: "Do you have microservices or do you have a monolith spread over hundreds of git repos?" Twitter

Hey is this a known issue with

./pants run

. I'm trying to run a command that has an argument that has spaces in it, e.g

./pants run someting:script -- --message 'add new Column'

and it will fail when running since it assumes

new Column

aren't part of the same string. It says that there are no commands

new or Column

. My assumption is that it's related to shell string parsing so there might not be a good solution. Works correctly when doing

./pants package someting:script && ./dist/script.pex --message 'add new Column'

https://twitter.com/cczona/status/1430665360882159623 Pants Build retweeted: 💯. User feedback is crucial, so we at @pantsbuild appreciate the generosity of every person who takes the time to h… twitter.com/i/web/status/1… Twitter I became a better technologist when I learned to think about what I do from the eyes of my users first. When I star… twitter.com/i/web/status/1… Twitter

weird, maybe a little OT, but two weeks ago (when I last worked on migrating to pants) my builds worked fine. Now, pip fails trying to build

pyzmq

(presumably before, it was using binaries) Have a constraints file, no other changes. kinda baffled

poetry is weird, or? Using

poetry export

I get strange ICs.

https://twitter.com/djangoproject/status/1430870140384546818 Pants Build retweeted: If you use #Django, please consider taking part in our survey here surveys.jetbrains.com/s3/t-django-de… Twitter

Trying to map all targets in a directory to a target dependencies. Following the docs here: https://www.pantsbuild.org/docs/targets#dependencies-and-dependency-inference Is there any way we can describe all targets in a directory instead of listed them out individually (something like

app/example::

)?

bump! https://pantsbuild.slack.com/archives/C046T6T9U/p1629839552346400

🧵 about naming things for the lockfile project, "lockfile" vs "resolve":