Commits on May 9, 2022

1. Do not vendorize third-party packages …

   - Vendorizing your dependencies forces the consumers of your API to
     include these dependencies as well (or to fork your project), which is
     not good practice in case they have a more sane/programmatic/automated
     way of handling runtime dependencies (eg: conda, rez, etc.).
     Good common practice is to have a "recipe" of your dependencies (eg: a
     requirements.txt, an environment.yaml, a pyproject.toml) etc. so that
     your consumers can easily integrate these dependencies into their own
     workflow for dependency management, instead of forcing them to use
     whatever version you chose. Even if they don't end up in their
     PYTHONPATH, consumers of the API still have to deal with breaking
     changes in these dependecies. For example, I (as a vfx studio) need to
     update our tk-core to a version that has merged
     shotgunsoftware#818  in order to have
     pyaml run fine in python3. A problem that I wouldn't have to deal with
     at all f youd didn't vendorize it in the first place.
   - Some interesting ideas: https://gist.github.com/datagrok/8577287
   - Shameless plug: https://valerioviperino.me/conda/for-pipeline-tds

   Valerio Viperino committed May 9, 2022
   Configuration menu

   • View commit details
   • Copy full SHA for 1df7f16
   • Browse repository at this point

   Copy the full SHA

   1df7f16 View commit details

   Browse the repository at this point in the history