You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'll state up front: I think we should be consistent in how we refer to Ibis when writing prose documentation.
When referring to top-level functions and methods, we are already consistently using backticks so that it is clear that it is a callable function/method, e.g. ibis.read_csv
When referring to the library in non-code contexts, we're a bit more scattered:
A backend is where execution of Ibis table expressions...
You can perform joins on local data to ibis expressions from your backend...
Which convention would you like to use across all Ibis documentation?
Ibis -- (always capitalized)
60%
ibis -- (always lowercase)
20%
[Ii]bis -- (lowercase unless capitalized at start of sentence)
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
I'll state up front: I think we should be consistent in how we refer to Ibis when writing prose documentation.
When referring to top-level functions and methods, we are already consistently using backticks so that it is clear that it is a callable function/method, e.g.
ibis.read_csv
When referring to the library in non-code contexts, we're a bit more scattered:
5 votes ·
Beta Was this translation helpful? Give feedback.
All reactions