Skip to content

Documentation paths are ambiguous on case insensitive file systems #12712

@jnothman

Description

@jnothman

Master's documentation build produces files including:

modules/generated/sklearn.cluster.dbscan.html
modules/generated/sklearn.cluster.DBSCAN.html
modules/generated/sklearn.cluster.optics.html
modules/generated/sklearn.cluster.OPTICS.html

These paths will not work well on file systems that are case insensitive. Does anyone know of a way to make the sphinx autogen functionality generate alternative names in this case? Ideally we would do so in a way that keeps sklearn.cluster.DBSCAN.html which has existed in previous releases, while sklearn.cluster.dbscan.html did not.

We could also do post-processing so that documentation packages can be shared with case insensitive platforms, even if they cannot be generated on case-insensitive platforms.

Discovered in the context of Kapeli/Dash-User-Contributions#2143

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions