Mirror of forum.nim-lang.org

9737 :: Mr. Rumpf, why didn't you went along with the Python standard library?

• grd (orginal) [2022-12-19T11:00:44+01:00] view original

  Right now I am struggling quite a lot with a new program that I am trying to rewrite. Everything is slightly different from the standard library of Python. So why did you got rid of this? Some of the things are pretty well thought of, I am well aware that they aren't designed to be as performant wise, but you could have implemented those as well, or couldn't you?

  I am not saying that the current standard library of Nim is bad or something else, it's only that I wonder why you diverted from Python?

  Gerard

---

• aEverr (orginal) [2022-12-19T11:02:05+01:00] view original

  because nim is not specifically aimed to be similar to python in every sense

---

• ElegantBeef (orginal) [2022-12-19T11:05:10+01:00] view original

  Nim is not a Python subset. It is its own distinct language with its own design principles. Aside from passing similarities they have very little in common.

---

• NameUndefined (orginal) [2022-12-19T11:05:12+01:00] view original

  Because Nim is not meant to be a compilable python, but if you still need some of python modules or functions there may be rewrites somewhere on the internet. For instance Narimiran ported the itertools python module to nim.

---

• matkuki (orginal) [2022-12-19T11:28:29+01:00] view original

  Nim has got (in my opinion) the best Python interop out there: nimpy

---

• jasonfi (orginal) [2022-12-19T11:35:46+01:00] view original

  Give ChatGPT a try. It's not perfect, but it can give you some ideas quickly.

  The question you asked about not going the way of the Python library is implying that Nim is a sped-up clone of Python, which it isn't.

---

• Araq (orginal) [2022-12-19T13:48:04+01:00] view original

  Nim is not similar enough to Python for this to provide any benefits. Instead Nim's standard library evolved with the Nim compiler and offers many little improvements like multiReplace or containsOrIncl and Python really should look into stealing.

---

• linwaytin (orginal) [2022-12-19T14:16:56+01:00] view original

  How about this? https://github.com/juancarlospaco/cpython

---

• grd (orginal) [2022-12-22T18:42:12+01:00] view original

  @linwaytin I didn't see anything like xml.etree and I really like the documentation in Python https://docs.python.org/3/library/xml.etree.elementtree.html

  Is there something like that in Nim?

---

• Yardanico (orginal) [2022-12-22T18:52:54+01:00] view original

  https://nim-lang.org/docs/xmltree.html

---

• grd (orginal) [2022-12-22T20:29:51+01:00] view original

  What is so good about the Python version is its documentation. IMHO that is lacking in Nim. Unless you can give me some good documentation.

---

• xigoi (orginal) [2022-12-23T00:04:42+01:00] view original

  In my opinion, Nim's standard library is documented well:

---

• Stefan_Salewski (orginal) [2022-12-23T00:38:48+01:00] view original

  well:

  It is not too bad, but in my personal opinion there is much room for improvements. I think I was really satisfied with the Ruby API docs 15 years ago.

---

• Araq (orginal) [2022-12-23T15:13:23+01:00] view original

  Most of Python's documentation consists of prose trying to describe the involved types...

---