Re: Unclear (for Python people) import behavior. And how to deal with it

2020-06-18 Thread ZadaZorg
@juancarlospaco thanks, I read links you provide before. Maybe I'm skipped, but there were no explanations of such catch. @Yardanico oh, thanks a lot. I think that is it!

Re: Unclear (for Python people) import behavior. And how to deal with it

2020-06-18 Thread juancarlospaco
* [imports](https://github.com/nim-lang/Nim/wiki/Nim-for-Python-Programmers#Imports) * [Objects](https://github.com/nim-lang/Nim/wiki/Nim-for-Python-Programmers#Objects) * [I recommend read it completely](https://github.com/nim-lang/Nim/wiki/Nim-for-Python-Programmers#table-of-contents)

Re: Unclear (for Python people) import behavior. And how to deal with it

2020-06-18 Thread Yardanico
Your example can be fixed by doing export ex.uuid Run Or, if you want to export _everything_ from that module (export only exports things which are marked by `*`: import ex export ex Run See [https://nim-lang.org/docs/manual.html#mod

Unclear (for Python people) import behavior. And how to deal with it

2020-06-18 Thread ZadaZorg
During my learning of nim, I'm trying to implement some kind of code common for Python OOP. I'm spent a lot of time reading articles, book, forum and feels like I'm more or less OK with basics. But today I meet strange bug (as I initially think), which is explained in 3 listings below... File