Select a name for the Glean Python package
Categories
(Data Platform and Tools :: Glean: SDK, defect, P3)
Tracking
(Not tracked)
People
(Reporter: mdroettboom, Unassigned)
References
Details
(Whiteboard: [telemetry:glean-rs:m13][glean-py] )
It is already taken on PyPI: https://pypi.org/project/glean/
Options:
- glean-telemetry
- mozilla-glean
- glean-telemetry-sdk
Thoughts?
Reporter | ||
Updated•5 years ago
|
Comment 1•5 years ago
|
||
Hi Mike, hi Alessio!
Since we have glean-parser, I think the following could work:
- glean-telemetry
- glean-metrics
- glean-pings
I like glean-telemetry best!
FWIW, I created pytest-pings for Firefox Telemetry related fixtures at the Whistler All-Hands:
https://pypi.org/project/pytest-pings/
Comment 2•5 years ago
|
||
(In reply to Michael Droettboom [:mdroettboom] from comment #0)
It is already taken on PyPI: https://pypi.org/project/glean/
Options:
- glean-telemetry
- mozilla-glean
- glean-telemetry-sdk
Thoughts?
I'd vote for mozilla-glean
or moz-glean
(we went for that naming scheme for this).
If the naming scheme of crates.io allows it, we should probably make it consistent across the two platforms (and other ones as well).
Mike, thoughts? Jan-Erik?
Comment 3•5 years ago
|
||
Everything flies on crates.io. I have glean and glean-ffi reserved there already. IMO it makes sense to use glean
there for the nice API (then we just have to find a name for the current crate, but that's already names glean-core
so we could stay with it?).
For the Python version I don't have too many opinions. Given that Glean is in theory not bound to Mozilla, I'd say glean-telemetry might be a sensible name there.
Comment 4•5 years ago
|
||
(In reply to Jan-Erik Rediger [:janerik] from comment #3)
Everything flies on crates.io. I have glean and glean-ffi reserved there already. IMO it makes sense to use
glean
there for the nice API (then we just have to find a name for the current crate, but that's already namesglean-core
so we could stay with it?).For the Python version I don't have too many opinions. Given that Glean is in theory not bound to Mozilla, I'd say glean-telemetry might be a sensible name there.
Mh, good point. What about glean-sdk
? I'm a bit hesitant about putting telemetry
in the name itself.
Comment 5•5 years ago
|
||
(In reply to Alessio Placitelli [:Dexter] from comment #4)
(In reply to Jan-Erik Rediger [:janerik] from comment #3)
Everything flies on crates.io. I have glean and glean-ffi reserved there already. IMO it makes sense to use
glean
there for the nice API (then we just have to find a name for the current crate, but that's already namesglean-core
so we could stay with it?).For the Python version I don't have too many opinions. Given that Glean is in theory not bound to Mozilla, I'd say glean-telemetry might be a sensible name there.
Mh, good point. What about
glean-sdk
? I'm a bit hesitant about puttingtelemetry
in the name itself.
I'm fine with either glean-sdk
or glean
. Let's make sure we match bug 1591558.
Reporter | ||
Comment 6•5 years ago
|
||
I guess we could go with glean-sdk
or glean-client
or even glean-python
, which would be consistent with "glean first" in bug 1591558, as well as glean_parser
which is already registered.
I don't think we can match bug 1591558 since glean
is already taken on PyPI, but that's just how the cookie crumbles.
Reporter | ||
Updated•5 years ago
|
Reporter | ||
Updated•5 years ago
|
Reporter | ||
Comment 7•5 years ago
|
||
:janerik --
Note that in Python, the PyPI package name (which is used for installation with pip) doesn't not have to match the actual package name (the name by which it is imported). It's pretty common for this to be the case when there are name clashes like this.
So we could call this glean-sdk
for PyPI, but use import glean
, which would still be consistent with the desired behavior on the Rust side of things to make use glean
work.
Reporter | ||
Updated•5 years ago
|
Description
•