Hi, not very experienced here. Trying to setup a python monorepo. I'm starting from the example-python repo, and a virtualenv. I want to be able to

import helloworld

from anywhere (as long as my virtualenv is sourced). Any ideas what command to run? (I'm on ubuntu/linux if that matters) In general in my project, I'm hoping I'd have many packages like

helloworld

, and I could "build" all of them into my virtualenv with one command.

Hi, can you explain a bit further what you mean by "from anywhere"?

Thanks for responding! • "from anywhere" means e.g I can run

ipython

anywhere (in any directory) on my machine, and run the line

import helloworld

in the interpreter, and it will know I'm talking about the helloworld package in the example-python repo. ◦ the same way I could, if I did

pip install fire

in my virtualenv,

import fire

in an

ipython

session, and it would use the version of

fire

in my virtualenv • I'm using virutalenv to isolate my python environment for each thing I'm working on. So for the monorepo I'm trying to build, when I'm working on it, I would be in a virtualenv.

It's a package, it's just not built into a publishable distribution, like a wheel

if I make a new file

example-python/temp/temp.py

with a single line:

import helloworld

and run

python temp.py

from

example-python/temp/

, I'll get the error

ModuleNotFoundError: No module named 'helloworld'

Well, yes, since example-python/helloworld isn't on your sys.path in that case

ah ok, thanks! This makes sense. I think I misunderstood what pants is.

Well, yes, since example-python/helloworld isn't on your sys.path in that case

exactly, I was looking for something that would automatically add all our internal packages with a single command. E.g. for now I can make a

setup.py

file in each internal package, and manually

pip install -e PKG_PATH

to add that internal package to my virtualenv. I was just looking for a single command to automagically find our internal packages (and maybe even create the

setup.py

files for me 😂 ). but I think I know now that is not what pants is for. Still excited to use pants for linting and testing! Thanks!

Ah yes, idiomatic use of Pants means you don't need those multiple setup.py files

makes sense! I think losing

python ..

might be too much for my team right now 😂 . But the

./pants test

and

./pants lint

could be good starting points for us 😄

Editable installs (i.e., pip -e) don't play nicely with Pants because they violate assumptions about caching and hermeticity