6 ms·

See https://github.com/JdeH/Transcrypt/blob/master/Transcrypt/demos/hello/hello.py#L29-L33 https://github.com/JdeH/Transcrypt/blob/master/Transcrypt/de... Ther

See https://github.com/JdeH/Transcrypt/blob/master/Transcrypt/demos/hello/hello.py#L29-L33 https://github.com/JdeH/Transcrypt/blob/master/Transcrypt/de... There are spaces before subscript operators, before `.method()` calls, and between `def name` and `(param1, param2)`.

StavrosK 11y ago
Yep, as a Python dev that's used to Python looking a certain way, this is very offputting. This is a great project, and I would hate for it to look "off" by something as trivial as Javascriptish whitespace and formatting conventions.
- JdeH 11y ago
  You're encouraged to follow PEP8 completely for your Transcrypt apps and libs. As for interop with JS libs, following JS conventions is probably best, although some often use libs may acquire a PEP8 facade.
  - StavrosK 11y ago
    Well, it's the documentation that looks off, not my apps and libs.
    - JdeH 11y ago
      You mean the docs of Transcrypt? In what way should it be improved? Any critisism to make it better is very welcome!