Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Project name (continued) #2

Closed
rth opened this issue Apr 5, 2023 · 3 comments
Closed

Project name (continued) #2

rth opened this issue Apr 5, 2023 · 3 comments

Comments

@rth
Copy link
Member

rth commented Apr 5, 2023

A fair number of users in Pyodide are coming from Python and have relatively little knowledge of the JS world. So a name like web-idl wouldn't really tell them much, and actually, there is a very similar-sounding stdlib module https://docs.python.org/3/library/idle.html. So personally, when seeing this package name in emails I thought this was a web version of that :)

Sorry I missed the pings in the parent issues about naming. If it's not too late, and if the target audience is Python developers who are going to use this from Python, I would suggest something that would be more familiar to them.

Here are some (filtered) "free associations" by GPT4 for the name,

  1. pyodide-webtypes: This name suggests that the package contains type annotations specific to the web platform within the Pyodide ecosystem.
  2. webtypy: A playful combination of "web," "type," and "Python" that reflects the package's goal of providing type annotations for web platform native objects in Python.
  3. pywebidl: Drawing inspiration from Web IDL, this name suggests that the package serves a similar purpose in the context of Python and Pyodide.
  4. webpytypes: Combining "web," "Python," and "types," this name signifies that the package provides Python type annotations for the web platform. [the issue is that web.py is an existing web framework (rth)]
  5. pybrowserdefs: Combining "Python," "browser," and "definitions," this name highlights that the package offers type definitions for browser components and web platform native objects in Python.

another thing to keep in mind is that it's better for the project name to be searchable. Even once this project exists with documentation people will never end up on this page by searching "web idl", they would probably have to search "python web idl" but then they would end up on all the Python parsers for web IDL (such as widlparser and pywebidl2. They would end up here searching "pyodide web idl" but that's very specific, and as far as I understand the project could potentially for any Python in the browser distribution.

I was going to suggest pywebidl, but then it would feel like pywebidl2 is the next version.
Maybe webtypy could be cute, and relatively searchable.

"python web idl" -> 4M google search results
webtypy -> "17k "

I also like a vague association with with mypy with lots of "y".

But anyway @simonegiacomelli it's your project, so you should choose the name :) We can also keep the current name.

@simonegiacomelli
Copy link
Collaborator

@rth thank you for taking care of this aspect! I believe it's very important; after reading about web-idl I went back to my notes where I sketched some name but everyone was not worth mentioning...

I actually like webtypy; it does have a good sound to it and I agree it's pythonically cute :)

From my part, we can proceed to rename the repo (and thus the project).

@rth
Copy link
Member Author

rth commented Apr 6, 2023

That works. Renaming done.

@rth rth closed this as completed Apr 6, 2023
@hoodmane
Copy link
Member

hoodmane commented Apr 6, 2023

Thanks Roman and @simonegiacomelli!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants