wide-midnight-7859808/02/2022, 3:02 AM
witty-crayon-2278608/02/2022, 3:12 PM
`rc`: does anyone have anything they’d like to get in?
fresh-cat-9082708/02/2022, 5:00 PM
ancient-vegetable-1055608/02/2022, 9:32 PM
internally, because it’s not supported by PEP 304-style pluggable importers (PyOx…r uses one). The problem is that the replacement,
, cannot currently load resources from namespace packages, and the very first thing that Pants does on startup is load the
file from the
namespace package using
. There’s a backport library that fixes this issue, but that would require users install an external requirement into their python environment. One option is to vendor the code in (it looks relatively small). Easier would be if I could move the
file into a non-namespace package. It appears, though, that our installer script depends on the location of the
file. I could leave the current version of the file as a symlink (or the importable version, for that matter). Do we have a preference here?
hundreds-father-40408/03/2022, 3:14 PM
wide-midnight-7859808/04/2022, 1:49 PM
flat-zoo-3195208/04/2022, 4:09 PM
is broken? It seems to be outputting
no matter what, even for trivial dep paths like direct dependencies
sh-5.1$ ./pants dependees //tests/sorted_components.py:../testlib //:testlib //tests/local/components.py:../../testlib sh-5.1$ ./pants paths --paths-from=//tests/sorted_components.py:../testlib --paths-to=//tests/local/components.py:../../testlib sh-5.1$
hundreds-father-40408/04/2022, 7:57 PM
hundreds-father-40408/04/2022, 8:17 PM
until we have landed local requirement support for Pex?
ancient-vegetable-1055608/04/2022, 8:20 PM
hundreds-father-40408/05/2022, 2:21 AM
should be a global option vs. per-resolve for local requirements?
wide-midnight-7859808/05/2022, 4:55 PM
? Does pants auto lower-case extensions when matching?
happy-kitchen-8948208/05/2022, 9:28 PM
average-vr-5679508/06/2022, 5:47 PM
When I run
Installed version of Pants (2.14.0.dev4+git165bb828) did not match requested version (2.14.0.dev4)!
PANTS_PEX_RELEASE=STABLE ./build-support/bin/release.sh build-universal-pex
These seem... Conflicting? That one is stripping the git-sha where it shouldn't, and the other is requiring it where it doesn't see it?
ERROR: Could not find a version that satisfies the requirement pantsbuild.pants==2.14.0.dev4+git165bb828 (from versions: none) ERROR: No matching distribution found for pantsbuild.pants==2.14.0.dev4+git165bb828
happy-kitchen-8948208/08/2022, 4:41 PM
hundreds-father-40408/08/2022, 5:57 PM
to let you hook up constraints files when generating a lockfile. Unlike before, this option lets you specify tool "resolves" like
option. Whereas our conventional modeling would be
and so on. Thoughts on what is preferable? This decision will apply to migrating
bitter-ability-3219008/08/2022, 6:28 PM
bitter-ability-3219008/08/2022, 8:37 PM
, where should the plugin be located?
? (We have global options which use the term "build_file") We might able to do something a la: •
happy-kitchen-8948208/09/2022, 1:33 PM
bitter-ability-3219008/09/2022, 2:54 PM
hundreds-father-40408/09/2022, 10:41 PM
don't currently give any mechanism to set a lockfile 🧵
hundreds-father-40408/10/2022, 5:16 PM
wide-midnight-7859808/10/2022, 8:43 PM
# In order for check to pass, we need some special compile options cc_sources( name="foo", compile_options=["magicoption1", "magicoption2"] ) cc_sources( name="bar", compile_options=["magicoption2", "magicoption3"] ) // In order for this library to be built, it requires a certain compile option in all deps cc_library( dependencies=[":foo", ":bar"], compile_options??? overrides? )