Skip to content

Multi-Line Comments #8

@seanlaw

Description

@seanlaw

This conda-forge workflow is failing and appears to be related to the presence of multi-line comments in the pyproject.toml file. This seems to be perfectly fine when running pixi locally with the pyproject.toml.

This is fine:

[tool.pixi.activation]
# Always execute ./setup.sh when activating the default environment
scripts = ["setup.sh"]

This fails:

[tool.pixi.activation]
# Always execute ./setup.sh when activating the default environment
# Note that `stumpy` will only be listed via `pip list | grep stumpy`
# and not via `pixi list | grep stumpy` since `pip install .` is used!
scripts = ["setup.sh"]

and, replacing the backtick with a single quote also fails

[tool.pixi.activation]
# Always execute ./setup.sh when activating the default environment
# Note that 'stumpy' will only be listed via 'pip list | grep stumpy'
# and not via 'pixi list | grep stumpy' since 'pip install .' is used!
scripts = ["setup.sh"]

with a GA error:

Run prefix-dev/setup-pixi@v0.9.4
Downloading Pixi
pixi info
pixi install
  /home/runner/.pixi/bin/pixi install --manifest-path /home/runner/work/automate/automate/pyproject.toml --color always
  Error:   × expected a string or a table, found array
       ╭─[/home/runner/work/automate/automate/pyproject.toml:109:11]
   108 │ # and not via 'pixi list | grep stumpy' since 'pip install .' is used!
   109 │ scripts = ["setup.sh"]
       ·           ────────────
   110 │ 
       ╰────

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions