Seeking feedback on my first pip /u/mikosullivan Python Education

I’ve written my first pip. Currently it’s on TestPyPI, not the main index. I would value any feedback on it, whether it’s about how I packaged and published the package, or the intent of the package.

The pip is available at https://test.pypi.org/project/uns-mikosullivan-001/ . The github project is at https://github.com/mikosullivan/uns .

From the readme:

UNS (Universal NameSpace) is a simple format for assigning a unique, universal namespace to any object using an abbreviated URI.

The concept of using URIs to create namespaces has been around for years. For example, Java uses a format for package names consist of domain names in reverse order: com.example.foo. Other namespace conventions use fully qualified URIs such as https://www.example.com/foo/bar.

The problem with using fully qualified domain names is that they have a lot of clutter. In particular, the scheme (e.g. https://) often seems unnecessary.

UNS provides a standard format for assigning namespaces using just the domain name and path of a URI. Those namespaces can be used in hash keys, file names, and other settings.

Consider, for example: idocs.com/color. That’s a simple, readable string. It’s clear that it’s within the idocs.com domain, and presumably has something to do with color. It’s easily distinguished from, say, github.com/foo/color, which might be a similar but distinct resource.

I’ve written my first pip. Currently it’s on TestPyPI, not the main index. I would value any feedback on it, whether it’s about how I packaged and published the package, or the intent of the package.

The pip is available at https://test.pypi.org/project/uns-mikosullivan-001/ . The github project is at https://github.com/mikosullivan/uns .

From the readme:

UNS (Universal NameSpace) is a simple format for assigning a unique, universal namespace to any object using an abbreviated URI.

The concept of using URIs to create namespaces has been around for years. For example, Java uses a format for package names consist of domain names in reverse order: com.example.foo. Other namespace conventions use fully qualified URIs such as https://www.example.com/foo/bar.

The problem with using fully qualified domain names is that they have a lot of clutter. In particular, the scheme (e.g. https://) often seems unnecessary.

UNS provides a standard format for assigning namespaces using just the domain name and path of a URI. Those namespaces can be used in hash keys, file names, and other settings.

Consider, for example: idocs.com/color. That’s a simple, readable string. It’s clear that it’s within the idocs.com domain, and presumably has something to do with color. It’s easily distinguished from, say, github.com/foo/color, which might be a similar but distinct resource.