happy-kitchen-89482
06/12/2023, 2:51 PMbuild-support/bin/
is getting unwieldy: it started as a place for some shell scripts, but it now contains Python code that imports other Python code from the same dir, which is not namespaced under anything Pants-specific. I want to move that python code under the regular src/python
root. The bikeshed question is, should this go under:
1) src/python/pants/release
(from pants.release.common import die
)
2) a new top-level package src/python/pants_release
(from pants_release.common import die
)
In either case we would have visibility rules to prevent the Pants client from depending on this release code. Same as how we prevent test code from ending up in the distribution.happy-kitchen-89482
06/12/2023, 2:51 PMcurved-television-6568
06/12/2023, 3:15 PMbuild-support/bin/pants/..
? from pants import ..
curved-television-6568
06/12/2023, 3:17 PMsrc/python/pants
proud-dentist-22844
06/12/2023, 3:35 PMsrc/python/pants
to understand how to use something in a repo that uses pants or to see what is possible. With 1️⃣ would pants.release
be included in the distributed artifact(s)?happy-kitchen-89482
06/12/2023, 3:43 PMhappy-kitchen-89482
06/12/2023, 3:43 PMcurved-television-6568
06/12/2023, 3:43 PMhappy-kitchen-89482
06/12/2023, 3:43 PMcurved-television-6568
06/12/2023, 3:45 PMproud-dentist-22844
06/12/2023, 3:48 PMsrc/python/pants
so it doesn’t mess with my habit of searching src/python/pants
. 🙂
src/python/pants_build_support
happy-kitchen-89482
06/12/2023, 4:03 PMsrc/python/pants
aren't available at runtime, e.g., testshappy-kitchen-89482
06/12/2023, 4:03 PMhappy-kitchen-89482
06/12/2023, 4:03 PMhappy-kitchen-89482
06/12/2023, 4:03 PMproud-dentist-22844
06/12/2023, 4:03 PMcurved-television-6568
06/12/2023, 4:04 PMcurved-television-6568
06/12/2023, 4:06 PMproud-dentist-22844
06/12/2023, 4:07 PMcurved-television-6568
06/12/2023, 4:08 PMhappy-kitchen-89482
06/12/2023, 5:01 PM