feat(import): `pixi import` roadmap

[lucascolley]

Issues to potentially be closed:

• Import conda-based environment with pip (requirements.txt) dependencies #1993
• Use existing conda environment #2421
• Add support for pixi add -f requirements.txt #2206
• pixi init --import environment-dev.yml can't parse pip -e . #2384
• Command to create new Pixi environments from requirements.txt or environment.yml files #1410
• feat(import): support extra index urls in --format conda-env #4464

Related:

• init: Allow '--import <ENV_FILE>' and '--format <FORMAT>' together #2523 and feat(init): support --import with --format pyproject #4134

Planned PRs (in some order):

• pixi import new formats:
  • PyPI requirements.txt
    • note that we also want to support recursive -r entries here, like https://github.com/nasa-fornax/fornax-demo-notebooks/blob/main/light_curves/requirements_scale_up.txt
  • Conda requirements.txt
  • conda-lock.yml
• Conda environment.yml improvements:
  • support pip dependencies (should piggy-back on the PyPI requirements.txt format implementation)
  • support variables section (parsing to activation.env): feat(import): WIP support variables for conda-env format #4103
• pixi init --import improvements:
  • feature parity with pixi import, including PyPI requirements.txt format
• pixi import general improvements:
  • document default behaviour when --format is not provided
  • include in relevant tutorials

Notes:

• PyPI -c constraint files and unnamed (url only) dependencies left unsupported for now

[lucascolley]

please shout if anything else would fit into this roadmap!

[KGrewal1]

Pylock.toml support perhaps? https://packaging.python.org/en/latest/specifications/pylock-toml/