Hi all, I’ve already got a question! How do I get my pyproject.toml file section for pylint to use an existing .pylintrc file?

[tool.pylint]
rcfile = ?

Is there a way to control the order packages are installed? I've got a PEX that uses GDAL, which needs to be installed after numpy to avoid a known issue (see here for details). I tried reordering my

requirements.txt

and regenerating the lockfile, but it seems to put things in alphabetical order. I've got them ordered "correctly" in my

dependencies

too. How can I make sure that Numpy is installing first?

do

__defaults__

apply before or after target generation? i.e. can I get away with only listing defaults for

python_source

and

python_test

, or do I need to use

(python_sources, python_source)

and

(python_tests, python_test)

to be sure I cover everything?

Is there a way to ignore parsing

BUILD

files that aren't relevant for a command? Or to ignore errors when parsing?!

How would I generate docs with mkdocs and pants? Some mkdocs plugins that auto-generate reference pages for code need to know where the code resides, and I don't think that's possible without some pants plugin. Is that correct?

I am having the same issue as this thread: https://pantsbuild.slack.com/archives/C046T6T9U/p1662132665071129 and this issue https://github.com/pantsbuild/pants/issues/16760. Just wondering if there’s any progress on this, or anyone found a workaround?

Using PyOxidizer for the first time:

ERROR: Package 'pkglocker' requires a different Python: 3.9.7 not in '==3.8.*'

Coming from:

python_sources()

pex_binary(
    name="pkglocker-binary",
    entry_point="pkglocker.py",
    layout="packed",
)

python_distribution(
    name="pkglocker-dist",
    dependencies=["./pkglocker.py"],
    provides=python_artifact(name="pkglocker", version="0.0.1"),
)

pyoxidizer_binary(
    name="pkglocker-pyox",
    dependencies=[":pkglocker-dist"],
    entry_point="pkglocker.py",
)

pants.toml

has:

[python]
interpreter_constraints = ["CPython==3.8.*"]

But Pants itself is using

3.9

I think. So I'm guessing we are running something in Pants' env instead of a materialized one? Or I'm missing something 🙂

is it well known/documented that if you have a flag

--env

on a subsystem that there’s some hidden default which is all environment variables ? — if i add with a string default, the current value seems to be the full dump of my environment 😂 …

PANTS_MY_SUBSYSTEM_ENV
  env
      default: my-default
      current value: namespace(__CFBundleI ..... continues with a full dump of my environment)

Hi! I have not used pants in a while and not sure how to formulate the vocabulary exactly. I'm working with a managed service (AWS Managed Airflow) that expects me to upload some python files (conceptually a tarball) and a

requirements.txt

file. I think I can gather my python files together by having pants make a tarball or sdist. But I'm not sure how to generate a

requirements.txt

style file to go along with them. (I know about

/pants dependencies

but now how to make it output in requirements.txt style nor include it with the tarball/sdist)

Hi everyone, I’m a pants noob. Based on the documentation, and trying things out with Pants, it looks like I don’t need to install tools like pylint, black, mypy, etc in my Poetry pyproject.toml file section

[tool.poetry.group.dev.dependencies]

because Pants will pull them in as necessary. Is this correct?

I'm building a

pex_binary

whose

resolve

is set to

B

, but none of my `python_source`s support resolve

B

. Surprisingly it builds and just fails to find the

entry_point

. Seems like a very weird behavior 😕

@witty-crayon-22786 Staring a new thread here for deprecation moving from 2.13 to 2.14

Hi all, should the

BUILD

files scattered about my project be included in my git repository?

I upgraded my project Python 3.10.7 to 3.10.8 and now I’m getting this:

./pants fmt :: 
Bootstrapping Pants using /opt/homebrew/bin/python3.8
Installing pantsbuild.pants==2.14.0 into a virtual environment at /Users/dfarrell/.cache/pants/setup/bootstrap-Darwin-arm64/2.14.0_py38
ERROR: Could not find a version that satisfies the requirement pantsbuild.pants==2.14.0 (from versions: 0.0.17, 0.0.18, 0.0.20, 0.0.21, 0.0.22, 0.0.23, 0.0.24, 0.0.25, 0.0.26, 0.0.27, 0.0.28, 0.0.29, 0.0.30, 0.0.31, 0.0.32, 0.0.33, 0.0.34, 0.0.35, 0.0.36, 0.0.37, 0.0.38, 0.0.39, 0.0.40, 0.0.41, 0.0.42, 0.0.43, 0.0.44, 0.0.45, 0.0.46, 0.0.47, 0.0.48, 0.0.49, 0.0.50, 0.0.51, 0.0.52, 0.0.53, 0.0.54, 0.0.55, 0.0.56, 0.0.57, 0.0.58, 0.0.59, 0.0.60, 0.0.61, 0.0.62, 0.0.63, 0.0.64, 0.0.65, 0.0.66, 0.0.67, 0.0.68, 0.0.69, 0.0.70, 0.0.71, 0.0.72, 0.0.73, 0.0.74, 0.0.75, 0.0.76, 0.0.77, 0.0.79, 0.0.80, 0.0.81, 0.0.82, 1.0.0, 1.0.1, 1.1.0, 1.2.0, 1.2.1, 1.3.0, 1.4.0, 1.5.0, 1.6.0, 1.7.0)
ERROR: No matching distribution found for pantsbuild.pants==2.14.0

Is 3.10.8 not supported, or am I missing something?

Hi all. Okay, I’m confused. I’m trying to address or eliminate this error

No name 'BaseModel' in module 'pydantic' (no-name-in-module)

from pylint in my project, but I’m having no luck. No change to my pyproject.toml or pants.toml or .pylintrc file seems to make any difference. Got any suggestions where to look? To be honest I’m not sure pylint is using my .pylintrc file… 😞

Hi there! I’m trying to apply pants to the existing project. The project so far uses pyproject.toml for building. But the pyproject.toml uses setuptools, not poetry. Is there a way to tell Pants, to use dependenices from such file while inferring 3rdpaty dependencies?

[build-system]
requires = ["setuptools", "setuptools-scm"]
build-backend = "setuptools.build_meta"

[project]
name = "tool"
readme = "README.md"
requires-python = ">=3.7"
dynamic = ["version"]
dependencies = [
    "boto3",
    "requests",
]
...

UPD: in fact is was a typo in the requirements file. After fixing it it works as expected. Initial question: Another question: I have a directory structure like:

├── README.md
├── pants
├── pants.toml
└── projectdir
    ├── BUILD
    ├── requirements.txt
    └── tool
        ├── BUILD
        ├── __main__.py
        └── backend.py

projectdir/requirements.txt

specify dependenceis, used in

projectdir/tool/backend.py

The

projectbuild/BUILD

has

python_requirements(
    name="reqs",
)

That should parse requireements.txt. But if query the dependencies from

projectdir/tool/backend.py

it’s nothing there.

./pants dependencies --transitive projectdir/tool/backend.py

I’ve create very simple repo that demonstrates it. https://github.com/golovasteek/pants_sample_project How do I ensure that dependencies in the

projectdir/tool

are properly inferred with respect to

projectdir/requirements.txt

?

So there's a nice

# pants: no-infer-dep

directive. Is there something like

# pants: allow-missing-dep

?

is there a good way to, in a test with a RuleRunner, to read a file output by

.run_goal_rule

?

Just landed! How can I help?

Is there an example using

pyproject.toml

with pants to build wheels? - I want to see an example, not the docs 👀

Hi all, I can understand how I don’t need to install black, isort, and pylint locally as they are static file checkers, and Pants will grab them as needed to run them. I’m not sure what to do about pytest. I want to run pytest in the Docker container for the project/application so the tests run in the same environment that the application will run in when in production. Is there a post anywhere about how to go about doing this?

I'm doing something wrong... What am I doing wrong that I can't make a

uvicorn_trailers

with

main.py

and

__init__.py

folder appear on the wheel?

I think it's because I'm using hatchiling... Anyone has tried it before?

Launching Jupyter Notebooks in an easy way: https://github.com/da-tubi/jupyter-notebook-best-practice

After upgrading Pants 2.14.0, I'm seeing warnings like the attachment. I've fixed all other occurrences of similar warnings, but this particular set of warnings is from Pants plugins inside the mon-repo, where I don't explicitly add Pants itself to the unified

requirements.txt

.... What is the proper way to fix these?

never heard of.. 😲

Hey folks, is there a way to profile a pex_binary with, eg, scalene? It wants to be run as

scalene your_prog.py

. I tried creating a new pex_binary and setting

script

or

entry_point

to "scalene", but I can't seem to pass arguments to it?

all relevant python projects around are migrating to it 👀

Hello. I’m trying to use a Python dependency (grpcio) that requires its own build step, and I’d like to specify an environment variable to influence this build. Is this possible to do in Pants? I checked the

python_requirement

documentation, but don’t see any obvious way to influence the build for an individual dependency (or all dependencies, which would also work).