search

dmarx / not-a-package-manager

utilities to facilitate working with codebases that don't ascribe to normal package management paradigms, e.g. ML research code that can be cloned but not installed.
MIT License
12 stars 0 forks source link

use a saved file or something to eliminate ambiguity about what needs to be added to PYTHON_PATH by warmup #5

Closed dmarx closed 2 years ago

dmarx commented 2 years ago

when add_install_dir_to_path is activated, we need to document this path somewhere and read from that location during the warmup step

dmarx commented 2 years ago

here's a simple way this could work:

  1. (separate feature) separately specify "envs" as subfolders we load content into
  2. at the top of the env, add a dotfile or config of some kind that carries env specific info
  3. make one of the sections of this file an enumeration of absolute paths to add to the pythonpath
    • should probably keep some kind of mapping between paths and packages for #6
dmarx commented 2 years ago

added in d1fb6ee88553822690d7ac3da0ed72366478015e