https://pantsbuild.org/ logo
Powered by
#general
  • r

    rough-minister-58256

    09/27/2017, 6:58 PM
    guessing it would probably be a pretty easy PR if you’re up for a fix.
  • b

    best-intern-74122

    09/28/2017, 9:03 AM
    @rough-minister-58256 how would I do that (specify on a target level)?
  • b

    best-intern-74122

    09/28/2017, 9:08 AM
    yeah I suspect it won't be overly complex to fix, it's just baffling why it's happening when I have tried to specify python3 where I can. I do know the functools32 setup.py checks for py3 and then throws an exception
  • b

    best-intern-74122

    09/28/2017, 9:09 AM
    another issue we're running into: trying to use nbconvert inside a pex created by pants, and it times out attempting to find ipykernel_launcher processes (same conditions as above, py3.5 specified)
  • c

    crooked-telephone-38431

    09/28/2017, 4:31 PM
    It seems like 
    --changed-parent=
    is ignored on pants 1.3.0 when 
    enable_v2_engine: False
    . Known behavior? Should I submit a PR to 1.3.x to silence the `test-changed`/`compile-changed` deprecations when using legacy engine?
  • d

    dry-analyst-73584

    09/28/2017, 4:45 PM
    I believe this https://github.com/pantsbuild/pants/pull/4907 is ready to land. Can a committer hit the big green button for me?
  • s

    strong-garage-46607

    09/29/2017, 12:27 AM
    ^ piggyback off of tansy, https://github.com/pantsbuild/pants/pull/4785 is ready to land as well. Pretty please 🙂
    w
    w
    • 3
    • 3
  • b

    bright-apartment-76721

    10/02/2017, 2:39 PM
    I have a python_binary in my BUILD file and when I try to pants run it, it seems to ignore the python in my PATH and be hitting /usr/bin/python. How can I ask it to look in my PATH?
  • b

    bright-apartment-76721

    10/02/2017, 3:35 PM
    trying to trace through how it decides on which python interpreter to use at all and it's hard to follow
  • b

    bright-apartment-76721

    10/02/2017, 3:40 PM
    it definitely seems to use the right interpreter to run my BUILD files
  • b

    bright-apartment-76721

    10/02/2017, 3:40 PM
    but seems to somehow forget that when running the 
    run
    command
  • b

    bright-apartment-76721

    10/02/2017, 3:42 PM
    I see a promising select_interpreter.py
  • b

    bright-apartment-76721

    10/02/2017, 3:43 PM
    I also seem to have a 
    .pants.d/pyprep/interpreter/no_targets/interpreter.path
    , which points to /usr/bin/python
  • b

    bright-apartment-76721

    10/02/2017, 3:43 PM
    so I'm guessing that's it
  • b

    bright-apartment-76721

    10/02/2017, 3:48 PM
    looks like all the logic for that is coming from the pex library. pulls out a bigger yak razor
  • b

    bright-apartment-76721

    10/02/2017, 3:57 PM
    ah, pex seems to pick a version seemingly at random in https://github.com/pantsbuild/pex/blob/master/pex/interpreter.py#L298
  • b

    bright-apartment-76721

    10/02/2017, 3:57 PM
    by putting the versions into a set, I think it relies on the hash order which can vary
  • b

    bright-apartment-76721

    10/02/2017, 4:11 PM
    okay I guess I can control it a bit by just putting a tight version constraint on --interpreter
  • b

    bright-apartment-76721

    10/02/2017, 4:11 PM
    would be nice to be able to specify it more directly though, not sure if that's possible in some other way
  • b

    bright-apartment-76721

    10/02/2017, 4:12 PM
    I guess my next question is how to pass in --interpreter via pants.ini
  • b

    bright-apartment-76721

    10/02/2017, 4:19 PM
    got it 🙂
  • b

    bright-apartment-76721

    10/02/2017, 4:19 PM
    GLOBAL
    section
  • r

    rough-minister-58256

    10/02/2017, 4:33 PM
    we use PEX_PYTHON for that, but the approach needs work and first class elevation into pants
  • b

    bright-apartment-76721

    10/02/2017, 4:33 PM
    oh, that will override all --interpreter constraints and such? that sounds perfect
  • r

    rough-minister-58256

    10/02/2017, 4:33 PM
    we have a new Python Language Ownership team spinning up at Twitter this week and that task is on their roadmap since it blocks python3 support
  • b

    bright-apartment-76721

    10/02/2017, 4:34 PM
    oh nice
  • r

    rough-minister-58256

    10/02/2017, 4:34 PM
    PEX_PYTHON
    basically ensures that any pex execution happens against a specific interpreter by way of a re-exec in the pex runtime
  • b

    bright-apartment-76721

    10/02/2017, 4:35 PM
    ah, I'm not sure how much the pex runtime is involved here. All I see is the interpreter_cache.py in pants importing pex.interpreter and using PythonInterpreter.all()
  • b

    bright-apartment-76721

    10/02/2017, 4:35 PM
    I'll give it a go though
  • r

    rough-minister-58256

    10/02/2017, 4:35 PM
    barring first class support in pants, it’s sort of a two-piece hack today
1...182318241825...2420Latest