Skip to content

Bug: If you enter dashes in the Python package name, things are bad #13

@DeflateAwning

Description

@DeflateAwning

I wasn't thinking too hard as I was filling out the prompts. Would be nice if it warned when you enter a senseless package name with dashes in it.

It results in code like:

from .polars-row-collector import *  # noqa: F403

I think a standard construction is that the project name has dashes, and the package name is the same but with dashes turned to underscores. I can't be the only person who's messed up the distinction in the prompts.

To see an example of what it looks like when it goes wrong: DeflateAwning/polars-row-collector@068fbc6

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