Skip to content

on 3.13: investigate why this 3.13 doesn't work. Can we pin later Jupiter without pipes if necessary? Is 3.13 on open-autonomy  #642

@8ball030

Description

@8ball030

on 3.13:

❯ autonomy packages init 
Traceback (most recent call last):
  File "/home/zarathustra/.cache/pypoetry/virtualenvs/autonomy-dev-IM6WInhx-py3.13/bin/autonomy", line 5, in <module>
    from autonomy.cli import cli
  File "/home/zarathustra/.cache/pypoetry/virtualenvs/autonomy-dev-IM6WInhx-py3.13/lib/python3.13/site-packages/autonomy/cli/__init__.py", line 21, in <module>
    from autonomy.cli.core import cli
  File "/home/zarathustra/.cache/pypoetry/virtualenvs/autonomy-dev-IM6WInhx-py3.13/lib/python3.13/site-packages/autonomy/cli/core.py", line 31, in <module>
    from autonomy.cli.deploy import deploy_group
  File "/home/zarathustra/.cache/pypoetry/virtualenvs/autonomy-dev-IM6WInhx-py3.13/lib/python3.13/site-packages/autonomy/cli/deploy.py", line 41, in <module>
    from autonomy.cli.helpers.deployment import (
    ...<5 lines>...
    )
  File "/home/zarathustra/.cache/pypoetry/virtualenvs/autonomy-dev-IM6WInhx-py3.13/lib/python3.13/site-packages/autonomy/cli/helpers/deployment.py", line 35, in <module>
    from compose.cli import main as docker_compose
  File "/home/zarathustra/.cache/pypoetry/virtualenvs/autonomy-dev-IM6WInhx-py3.13/lib/python3.13/site-packages/compose/cli/main.py", line 5, in <module>
    import pipes
ModuleNotFoundError: No module named 'pipes'

related issue on jupyter for more info, but since it originates from autonomy we cannot support 3.13 yet. Shall I open an issue on this in order to keep track of it?

Originally posted by @Karrenbelt in #618 (comment)

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions