I’m having an OCD moment here regarding naming, specifically about PythonObjectible. To match other similar types, does PythonObjectable not fit better? Or some alternative?
Trivial I know, but while not a bug it’s still bugging me. 
Here’s a list of a few similar types:
Brainstorming possible alternatives:
I kinda like PythonRepresentable, but defer to the Modular team on the technical implications of ‘representable’.
Unfortunately, non of these alternatives seems to be correct. PythonObjectible (convertible to PythonObject) in current state says, that conforming to this trait will allow to convert to PythonObject and this is the main purpose.
Then PythonObjectible → PythonObjectable?
From a quick search, object [i] ble is not a word, so …ible becomes …able?
Making it similar to existing types.
Yeah, this looks better and still correct
I’d like to acknowledge your OCD moment as the grammatically correct would be, I imagine, “PythonObjectifiable” though such a large word would be Objectionable.
The word “objectable” is in fact a word though considered rare.
Initial commit on Github by Chris Lattner:
[mojo-stdlib] Rework PythonObject list/tuple literal creation. (link)
“…
This patch introduces a new PythonObjectible trait (better name
suggestions welcome!) that has a single to_python_object()
requirement. This allows us to define these methods correctly in
terms of a trait instead of using static reflection.
…”
I think that I like PythonConvertable the most because it implies work being done as part of the conversion, letting users know it’s not free.
And it’s more generalisable. I also subconsciously used that spelling when talking about that on Discord, one datapoint for its naturalness I guess.
For me, this was first on my ‘alternatives’ list because it fell out naturally when I was thinking about what we intended to do…convert a Mojo object into a PythonObject.
I’d suggest something like PythonConvertible
Ugh, of course Convertible would be the correct spelling, versus Convertable which is not. PythonConvertible works for me. Better than PythonObjectible anyway.
Yep, “PythonConvertible” is what we called it in Swift: swift/docs/PythonInteroperability.md at main · tensorflow/swift · GitHub
It sounds like the team agreed that PythonConvertible would make sense - Joe went ahead with a rename.