Skip to content

Don't hard-code references to pytorch 2.4 in docs and error messages #235

@NicolasHug

Description

@NicolasHug

In #223 and https://github.com/pytorch/torchcodec/pull/224/files we added various explicit mentions of "pytorch 2.4" in the docs and in user-facing error messages.

That can be problematic because the "pinned" version of pytorch that torchcodec relies on changes with each new pytorch version. Which means when 2.5 is out, we need to update all those instances. It adds complexity to the release process, and there's a chance we'll miss it.

It would be more manageable to not make any reference to a specific pytorch version, and instead point the user to a reference table in our README, similar to that of torchvision https://github.com/pytorch/vision#installation

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