I also wonder about moving the scripts/generate_constraints.sh logic into a pants plugin so that ./pants is the entry point for all development tasks.

Is there a way to configure the mypy typecheck particular to modules/apps?

https://twitter.com/pantsbuild/status/1392868540538134536 Did you know Pants has a YouTube channel? Thanks to @EArellanoAZ, we’ve been filling it with concise tutorials, core concepts, and tips on things like how to use Pants to make Python 3 migrations easier. More vids coming. Smash that subscribe button… ;-) https://t.co/MiNVwhjEr3 https://t.co/XHgcbFBtt0 Twitter

I am using pants 1.30 and having issues with the following:

16:27:19 [ERROR] Failed to resolve compatible distributions:
1: uvicorn==0.13.3 requires click==7.* but click 8.0.0 was resolved

This is when i run a

test.pytest

goal with

::

specified as the target. We have hundreds of build files so this is not easy to find where the culprit is. I know i can fix this with constraints.txt but I need to know what specific BUILD file is causing this. Is there a way to know? I tried

--print-exception-stacktrace

but did not see anything in there that would lead me to the problem BUILD file. Any ideas?

https://twitter.com/benjy/status/1392886707368824834 Pants Build retweeted: At #PyConUS? Come hang out and ask us questions about speeding up #Python builds: https://e4284.hubilo.com/community/#/lounge/exhibitor Twitter

FYI pants.build now redirects to pantsbuild.org

Hey there, is there any example on building and deploying PEX to AWS EC2 for execution?

Hello folks! I have a question about using coverage.py through pants. We recently noticed that pants doesn’t generate test coverage report for files that are not encountered in the transitive closure of the test run which seems to match what the documentation says here -

Coverage will not report on unencountered files

Coverage will only report on files encountered during the tests’ run. This means that your coverage score may be misleading; even with a score of 100%, you may have files without any tests.

This is a shortcoming of Coverage itself.

https://www.pantsbuild.org/docs/python-test-goal#coverage However, it would be good to get some sense of which files are missing documentation in our monorepo. As the repo gets larger, it becomes more difficult to track where the coverage is lacking. So, my question is - Are there any known workarounds to generate coverage for files that are not covered by unit tests?

https://twitter.com/ThePSF/status/1392948320193204228 Pants Build retweeted: The 2021 Python Language Summit https://ift.tt/2SN9Oma Twitter

is there a way to signal to pants' dependency inference that an import is happening that it's not otherwise picking up on?

https://twitter.com/pantsbuild/status/1393234795690225667 Hi #PyCon attendees! Come hear Pants contributor @benjy speak about how we leveraged Python features in innovative ways to build the Pants plugin API. Starts soon! Twitter My #PyConUS2021 talk starts soon (9:15 Pacific)! Come and learn how we used Python in some unconventional ways to… https://twitter.com/i/web/status/1393234039419523078 Twitter

Hi all - I just ran into some trouble with requirements I'm getting an ABI error with Greenlet - which seems pretty common when platform differs from the target platform for some reason, and the obvious solution is to build it yourself I can do this normally with:

<http://requirements.in|requirements.in>

...
gevent>=21.1.0 --no-binary greenlet
...

Then:

pip-compile -o requirements.txt <http://requirements.in|requirements.in>

generates something like

# this file is generated blah blah blah
--no-binary greenlet
...
gevent==21.1.2
...

if you

pip install -r requirements.txt

it will correctly build greenlet for you when i'm going through the

PythonRequirementLibrary

s that are generated for my project however I can't find anything referencing that I can't rely on the greenlet wheel does that all make sense?

https://twitter.com/pantsbuild/status/1393320020047015943 What the heck is a build system, anyway..? @pantsbuild maintainer @benjy explains in less than 3 minutes the key features and wins of using a build system for your codebase. https://t.co/LxZ8OVClim Twitter

https://twitter.com/brettsky/status/1393243193462845440 Pants Build retweeted: Watching the @pantsbuild session at #PyConUS2021 and it looks like they are using type annotations the way I was ho… https://twitter.com/i/web/status/1393243193462845440 Twitter

Hi there, I need help with a dependency mapping problem. I am building a PEX that requires a dependency "airflow-common" which is listed in requirements.txt. "airflow_common" imports "airflow" as its dependency. Since the module name for airflow is "apache-airflow", I added a mapping "module_mapping={"apache-airflow": ["airflow"]," in the BUILD script at the source root. However, when I build my PEX file and runs it, I still see the error " File "/Users/mingshiwang/code/pynest/dist/libs.src.python.airflow_cli/airflow_cli.pex/airflow_cli/main.py", line 15, in <module> File "/Users/mingshiwang/code/pynest/dist/libs.src.python.airflow_cli/airflow_cli.pex/airflow_cli/main.py", line 12, in main File "/Users/mingshiwang/.pex/installed_wheels/4edcadb09e1093c6ef2fedd4cfc4d40e68f835e2/airflow_common-35.10.3-py3-none-any.whl/airflow_common/cli.py", line 55, in main from airflow.bin.cli import CLIFactory ModuleNotFoundError: No module named 'airflow'". Does anyone know how to resolve this? Thanks!

https://twitter.com/ToolchainLabs/status/1393589660555882499 Pants Build retweeted: Yay @pycon! Ask us about @pantsbuild and remote caching at Toolchain sponsor table in the Lounge from now to 3pm Pa… https://twitter.com/i/web/status/1393589660555882499 Twitter

https://twitter.com/pantsbuild/status/1393591859390341128 Pants Build retweeted: Maintainers from Pants Build system open source project will be there. 👍 Twitter I'm hosting open space at @pycon today on build tools, build systems, and build APIs such as REAPI. Let's talk abou… https://twitter.com/i/web/status/1393591406590050306 Twitter

https://twitter.com/chrisjrn/status/1393625080962289670 Pants Build retweeted: About to host the @ToolchainLabs booth at #pyconus. Come along to see the power of @pantsbuild and ask some core ma… https://twitter.com/i/web/status/1393625080962289670 Twitter

Does anyone with data science experience know much about https://github.com/mwouts/jupytext ?

It came up in conversation at PyCon, curious if there's interesting support we can add for it

https://twitter.com/tannewt/status/1393648071532113920 Pants Build retweeted: @NoelFB Pants build system looks neat for those comfortable with python. @pantsbuild Twitter

I'm hoping to find a simple way to download a file from the internet and cache it for future runs. Specifically this file is an executable that runs a DB emulator used in some tests. I know I can create an

ExternalTool

and then a custom rule that uses that tool but that seems like a fair amount of work. What I was hoping for is a

target

type like

download_file

that is similar to

ExternalTool

but I can then just use that as a dependency in tests that require the tool. That seems much easier as I'd pretty much just have to specify a URL and be done while

ExternalTool

requires creating a class and a custom rule and then tests that require it can't do a simple

pants test some/thing/needing/emulator/::

because the custom rule wouldn't be

test

- so I think I'd need to create a new target type too and then connect the rule to the target, etc.

What's the best way to separate different kinds of tests? eg unit vs integration I think I read something about tags, or do I need to change the target name from

tests

to

unit-tests

or similar? ie for

python_tests()

is adjusting

name=

or

tags=

preferable for distinguishing unit/integration tests? If

tags=

is the better option, then what is the purpose of

name=

?

Hi pants experts, I'd like your suggestion on how to store environment variables and their values when building a PEX file. I guess I can do "my_env=somevalue my_pex" when running the pex file, but this doesn't scale in my case where I need to set tons of env variables. I see a relevant open issue https://github.com/pantsbuild/pants/issues/10352, so I assume this is not yet supported? Thanks

I have a python package whose sole purpose is to provide resources for tests in other packages. There is some helper python in that package that loads the resources for things that depend on it. An interesting side effect is that in those other packages, pants only needs to know about the python imports to get access to those resources. But, within the tests package (named

st2tests

), can I tell pants that python file X depends on resources Y so that pants knows when to invalidate due to resources changes? ie I can use

python_library(dependencies=[... list of resources targets ...])

within

st2tests

. But then all of the python files in that directory will depend on all of the resources. How do I tell pants that only one file depends on one set of resources targets and a different file depends on a different set of resources?

@enough-analyst-54434 I am trying to create a constraints file using pip-compile (instead of using pip freeze) this is following what is now considered best practice(https://github.com/pypa/warehouse/blob/dffce426d48d779f5495c01547234993e3a3e523/Makefile#L124), however that seems to be incompatible w/ pex this is an attempt to lock down the constraints file (I want to add hashes) that will help protect some forms of supply chain attacks. see: https://pyconus2021.hubilo.com/community/#/session-stream/57619 https://github.com/di/talks/blob/master/2021/pyconus_2021/talk.pdf pex doesn't allow this: https://github.com/pantsbuild/pex/blob/6720d4c64fb033e8418b2e14535512baa01b9a2d/pex/vendor/_vendored/pip/pip/_internal/req/req_install.py#L878

Is there a way to get pants to ignore .swp files (or any other temp files created by vim)? I open a file to read it while pants is going (say running

./pants test ::

, and it detects a "change" and restarts the rule.

https://twitter.com/pyconil/status/1394594342581460993 Pants Build retweeted: "Python monorepos: what, why and how" by Benjy Weinberger from @pyconil 2021 #monorepo #pyconil #python Twitter

Hey guys, we are currently writing some new pants plugins for pants 1.30.x. Inside those plugins we would like to use 3rdparty libraries. How can we install these? We added a BUILD file into the plugin root directory, but it doesnt seem to load the dependency

python_library(
  name = 'plugin',
  dependencies=[
    '3rdparty/python:pyhocon',
  ]
)

Hey! I have a question on pip/requirements.txt dependency resolution. We have a (primarily Python) monorepo with several modules, all with their own requirements.txt and constrained by a top-level constraints.txt. These modules are both intended to be self-contained so some degree, but also get imported from other modules. We're running into problems specifically when doing a top-level

./pants test ::

(or other goals) where it attempts to resolve all requirements from the requirements.txt, but because some modules have common dependencies, it errors out with:

AssertionError: More than one direct requirement is satisfied by cbor2 5.3.0:
0. cbor2
1. cbor2<6.0,>=5.0.1
This should never happen since Pip fails when more than one requirement for a given project name key is supplied and applies for a given target interpreter environment.

We can get it to work if all requirements.txt exactly match, however when using a constraints file, this shouldn't be necessary