wooden-ability-49079
11/01/2023, 7:07 PMcurved-television-6568
11/01/2023, 8:17 PMpython_requirement
target, so no, you can not override that on the python_distribution
.
What’s the motivation to override it?wooden-ability-49079
11/01/2023, 8:20 PMcurved-television-6568
11/01/2023, 8:24 PMwooden-ability-49079
11/01/2023, 8:25 PMcurved-television-6568
11/01/2023, 8:26 PMcurved-television-6568
11/01/2023, 8:27 PMwooden-ability-49079
11/01/2023, 8:31 PMwooden-ability-49079
11/01/2023, 8:32 PMcurved-television-6568
11/01/2023, 8:34 PM!!target-address
in the dependencies field of any of your targets.. but you can’t exclude transitive dependencies that go beyond the targets you have declared, if that makes sense.curved-television-6568
11/01/2023, 8:36 PMcurved-television-6568
11/01/2023, 8:36 PMpants list ::
wooden-ability-49079
11/01/2023, 8:36 PMlittle-pilot-11155
11/03/2023, 11:06 AMpython_distribution
will only add your direct dependencies to METADATA file (for wheel), leaving dependency resolution to pip when you install your distribution. You can add your transitive dependency to the distribution as Andreas suggested (so you create python_requirement
for it and then you add it to python_distribution
under either dependencies
or inside one of your sources). But that would increase the size of your package.
One of the options that I am considering is to use pip's constraints file. If you ship it alongside your Python distribution file, you can then install it with pip install --constraint constraint.txt your_distribution_file
.