Currently we strive for pretty high compatibility with cpython. This is a difficult path. Maybe we can ease development by deliberately not implementing certain parts of python that might be weird in the first place.
Examples of things we could explicitly not implement:
Access to the __dict__ attribute. We could hide this, and implement in a simpler way.
The handling of the locals keyword. Also, the possibility to modify a local dictionary.
String glueing: "fu" "bar" == "fubar", a leftover from the C era, and error prone.
I would say that anything that is not documented in the CPython documentation can be changed without discussion. On any other deviation an issue should be opened and once accepted we will document the deviation.
Access to the dict attribute. We could hide this, and implement in a simpler way.
This is used in many places in the stdlib so I am not sure about this.
String glueing: "fu" "bar" == "fubar", a leftover from the C era, and error prone.
Summary
How compatible should rustpython be with cpython?
Detailed Explanation
Currently we strive for pretty high compatibility with cpython. This is a difficult path. Maybe we can ease development by deliberately not implementing certain parts of python that might be weird in the first place.
Examples of things we could explicitly not implement:
__dict__attribute. We could hide this, and implement in a simpler way.localskeyword. Also, the possibility to modify a local dictionary."fu" "bar" == "fubar", a leftover from the C era, and error prone.Background information about this topic:
Unresolved Questions
What should we leave out?
The text was updated successfully, but these errors were encountered: