https://pantsbuild.org/ logo
#general
Title
# general
c

cuddly-window-48195

10/21/2019, 3:46 PM
I think this is supposed to be working; I'm using the same setup as everyone else in my org, and pip is installed in my system environment?
e

enough-analyst-54434

10/22/2019, 9:33 AM
It shouldn't be working. Danny is right. The alooma setup.py:
Copy code
sr/bin/env python
from distutils.core import setup
try:
      from pip.req import parse_requirements
except ImportError:
      from pip._internal.req import parse_requirements

install_reqs = parse_requirements("requirements.txt", session=False)

reqs = [str(ir.req) for ir in install_reqs]

setup(
    name='alooma',
    version='0.4.15',
    description='Alooma python API',
    author='Alooma',
    author_email='<mailto:support@alooma.io|support@alooma.io>',
    packages=['alooma'],
    install_requires=reqs,
    keywords=['alooma', 'api']
)
The fact that PEX sees pip on you machine and allows it to leek in to the environment while executing this setup.py is unintended and a bug.
To be clear, that's a bogus setup.py that is designed to only work with pip. The pip dependency is un-declared.
Danny is also right about https://github.com/pantsbuild/pex/issues/781, but even then if this worked it would be by luck.
c

cuddly-window-48195

10/22/2019, 3:03 PM
Ah, thanks for your reply. That makes sense. Is it possible for me to patch the alooma target and attach the pip dependency?
Also, it might be interesting for your purposes that I only see this error on Linux (container) but not on MacOS.
3 Views