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

    red-jackal-13334

    04/23/2020, 10:33 AM
    ok, this was an easy fix 
    pex azure-cli setuptools -m azure.cli -o az
    👍 1
    h
    • 2
    • 1
  • r

    red-jackal-13334

    04/23/2020, 10:33 AM
    but this time it complains
  • r

    red-jackal-13334

    04/23/2020, 10:33 AM
    ModuleNotFoundError: No module named 'azure.common'
  • r

    red-jackal-13334

    04/23/2020, 10:33 AM
    which is definitly in the zip file
  • r

    red-jackal-13334

    04/23/2020, 10:35 AM
    i even tried with venv, pip install azure-cli, pip freeze >reqs, pex setuptools -r reqs -m azure.cli -o az, still azure.common not found
    h
    e
    • 3
    • 18
  • h

    happy-kitchen-89482

    04/23/2020, 3:52 PM
    Thanks for the detailed repro steps, let me try and follow them to repro myself. Is this on a Mac or a Linux machine?
  • r

    red-jackal-13334

    04/24/2020, 11:01 AM
    @happy-kitchen-89482 it's a linux machine
  • h

    happy-kitchen-89482

    04/24/2020, 4:32 PM
    I'll give it a try
  • w

    wide-energy-11069

    05/02/2020, 12:41 AM
    just heads up ^ is not the most important issue anymore. pex 2 (with pip) are carrying resolve differences, so we’ve landed it twice and reverted twice.
    👀 1
    w
    • 2
    • 5
  • c

    calm-artist-46894

    05/04/2020, 4:59 PM
    For packages like 
    libcurl
    that depends on shared library wich is not part of the Python package itself, what’s the recommended way to include them in a pex? Currently I try:
    Copy code
    pex --python=python3 pycurl -o testpycurl.pex
    Then in a fresh Python3 container, I tried to use the pex:
    Copy code
    root@41161a1cada4:~# ./testpycurl.pex
Python 3.6.8 (default, Jun 11 2019, 01:21:42)
[GCC 6.3.0 20170516] on linux
Type "help", "copyright", "credits" or "license" for more information.
(InteractiveConsole)
>>> import pycurl
Traceback (most recent call last):
  File "<console>", line 1, in <module>
ImportError: libcurl.so.4: cannot open shared object file: No such file or directory
>>>
    I understand this is beyond Python, i.e., 
    pip install pycurl
    itself would fail if 
    libcurl
    is not installed prior to install 
    pycurl
    , but would like to check if there any support from 
    pex
    , or this is believed to be solved by another layer of tools (e.g. docker)
    a
    w
    e
    • 4
    • 18
  • a

    aloof-angle-91616

    05/06/2020, 4:40 PM
    what is the expected behavior of (1) executing a pex file directly vs (2) invoking it as the second argument of a command line starting with 
    python
    ?
  • w

    wide-energy-11069

    05/06/2020, 4:41 PM
    it will decide which interpreter pex will be bootstrapped
  • w

    wide-energy-11069

    05/06/2020, 4:41 PM
    Copy code
    $ head dist/stressdash.pex 
#!/usr/bin/env python2.7
P!ootstrap/_pex/__init__.pyP!?y????.bootstrap/pex/__i
  • a

    aloof-angle-91616

    05/06/2020, 4:41 PM
    with pex 1.6.12 (i can test on pex 2) the 
    python
    is needed to correctly select the interpreter and i don’t understand why that’s necessary
  • a

    aloof-angle-91616

    05/06/2020, 4:41 PM
    oh
  • a

    aloof-angle-91616

    05/06/2020, 4:41 PM
    also, the pex files im using have explicit shebang lines. forgot about that
  • a

    aloof-angle-91616

    05/06/2020, 4:42 PM
    that is the answer then
  • w

    wide-energy-11069

    05/06/2020, 4:42 PM
    essentially the shebang is ignored if you run 
    python some.pex
    👍 1
  • w

    witty-crayon-22786

    05/06/2020, 11:08 PM
    re: shebangs: i wonder if it’s possible to give pex an insanely permissive shebang that would bootstrap under ~anything it can find, so that we can avoid the 
    python ./pex
     in favor of 
    #!/env/please/just/any python*
    a
    h
    +2
    • 5
    • 66
  • a

    aloof-angle-91616

    05/06/2020, 11:16 PM
    @witty-crayon-22786 basically in response to an issue that, randomly, li haoyi happened to be seeing (and he very kindly did not publicly mention pex), john created this issue (https://github.com/pantsbuild/pex/issues/962) which links to the underlying problem in https://github.com/pantsbuild/pex/issues/331. john's solution (unzipping every pex file before running) was really interesting to me because it opened the door for reducing ipex deploy time by another whopping percentage: https://github.com/pantsbuild/pex/issues/962#issuecomment-624512069
    w
    • 2
    • 3
  • e

    enough-analyst-54434

    05/12/2020, 12:53 AM
  • h

    hundreds-father-404

    05/13/2020, 2:07 AM
    I started getting this today:
    Copy code
    stderr:
                                WARNING: pip is configured with locations that require TLS/SSL, however the ssl module in Python is not available.
                WARNING: Retrying (Retry(total=4, connect=None, read=None, redirect=None, status=None)) after connection broken by 'SSLError("Can't connect to HTTPS URL because the SSL module is not available.")': /simple/ipdb/
                WARNING: Retrying (Retry(total=3, connect=None, read=None, redirect=None, status=None)) after connection broken by 'SSLError("Can't connect to HTTPS URL because the SSL module is not available.")': /simple/ipdb/
                WARNING: Retrying (Retry(total=2, connect=None, read=None, redirect=None, status=None)) after connection broken by 'SSLError("Can't connect to HTTPS URL because the SSL module is not available.")': /simple/ipdb/
                WARNING: Retrying (Retry(total=1, connect=None, read=None, redirect=None, status=None)) after connection broken by 'SSLError("Can't connect to HTTPS URL because the SSL module is not available.")': /simple/ipdb/
                WARNING: Retrying (Retry(total=0, connect=None, read=None, redirect=None, status=None)) after connection broken by 'SSLError("Can't connect to HTTPS URL because the SSL module is not available.")': /simple/ipdb/
                ERROR: Could not find a version that satisfies the requirement ipdb (from versions: none)
                ERROR: No matching distribution found for ipdb
                pid: 67628 -> /Users/eric/.pyenv/versions/3.7.6/bin/python3.7 /private/var/folders/sx/pdpbqz4x5cscn9hhfpbsbqvm0000gn/T/process-execution7rY2tk/pex_root/pip.pex/d3323a933395f1fea4b421b92e99bd2c3d524e6c --disable-pip-version-check --isolated --no-python-version-warning -q --cache-dir /private/var/folders/sx/pdpbqz4x5cscn9hhfpbsbqvm0000gn/T/process-execution7rY2tk/pex_root download --dest /tmp/tmpfydwjkux/cp37-cp37m --index-url <https://pypi.org/simple/> --header Cache-Control:max-age=3600 --retries 5 --timeout 15 ipdb pygments pytest-cov>=2.8.1,<2.9 pytest-icdiff pytest-timeout>=1.3.4,<1.4 pytest>=5.3.5,<5.4 setuptools==44.0.0 zipp==2.1.0 raised Executing /Users/eric/.pyenv/versions/3.7.6/bin/python3.7 /private/var/folders/sx/pdpbqz4x5cscn9hhfpbsbqvm0000gn/T/process-execution7rY2tk/pex_root/pip.pex/d3323a933395f1fea4b421b92e99bd2c3d524e6c --disable-pip-version-check --isolated --no-python-version-warning -q --cache-dir /private/var/folders/sx/pdpbqz4x5cscn9hhfpbsbqvm0000gn/T/process-execution7rY2tk/pex_root download --dest /tmp/tmpfydwjkux/cp37-cp37m --index-url <https://pypi.org/simple/> --header Cache-Control:max-age=3600 --retries 5 --timeout 15 ipdb pygments pytest-cov>=2.8.1,<2.9 pytest-icdiff pytest-timeout>=1.3.4,<1.4 pytest>=5.3.5,<5.4 setuptools==44.0.0 zipp==2.1.0 failed with 1
    I did a brew upgrade today, so it’s possibly related. Does anyone recognize this? I wonder if the issue is SSL or ipdb
  • h

    hundreds-father-404

    05/13/2020, 2:39 AM
    I think my Python is botched. I have the same SSL issue with the example repo when resolving protobuf. Sigh
  • a

    aloof-angle-91616

    05/13/2020, 2:48 AM
    have you tried different python versions on the same machine? worst case git clone cpython and pointing it to an SSL means you get to use :=
  • a

    aloof-angle-91616

    05/13/2020, 2:48 AM
    also maybe try updating homebrew if you have or haven’t recently
  • a

    aloof-angle-91616

    05/13/2020, 2:49 AM
    these are guesses though i’ve seen that message but i don’t remember if it corresponded with failure
  • j

    jolly-midnight-72759

    05/13/2020, 3:00 AM
    The 
    Can’t connect..
    error is a python related error. I have not nailed down the cause, but reinstalling my 
    pyenv
    python versions and blowing away my pants caches is how I solve it. It has happened twice to me in the past 6 months.
    ☝️ 2
    a
    • 2
    • 1
  • h

    hundreds-father-404

    05/13/2020, 3:01 AM
    Huh, you’re right. That did do the trick. Thank you @jolly-midnight-72759!
    👍 1
  • j

    jolly-midnight-72759

    05/13/2020, 3:03 AM
    I think it happens when either pyenv or OpenSSL update, but the work around is easier then tracking down the cause. 😊
  • h

    hundreds-father-404

    05/13/2020, 3:03 AM
    I think today it was from 
    brew upgrade
    upgrading my Pyenv
1...697071...74Latest