mguillech

11 ms·

1. 1.▲
   by mguillech 12y ago

   Python caches modules imported, you can check it out in your local shell with: import sys ; sys.modules. That's why whenever you make changes to a module which has been already loaded you won't see the changes until you load the m
2. 2.▲
   by mguillech 12y ago

   Please check out http://en.wikipedia.org/wiki/Late_binding to know more.
3. 3.▲
   by mguillech 12y ago

   Right, it's (re) defined every time you call 'foo2' but that's a different scenario than the one written in the article (hadn't you had 'foo2' and only 'foo' then you'd have the same time in
4. 4.▲
   by mguillech 12y ago

   Agreed 100%, this type of constructions should be avoided in the first place in favor of more "readable" ones but this happens in a fair amount of code that I've seen (and I keep seeing).
5. 5.▲
   by mguillech 12y ago

   That's right, in most Python implementations there's a "compiled" part (generally to bytecode) and then an "interpreted" one to run that bytecode. PyPy is a good example of a Python interpreter built on top of
6. 6.▲
   by mguillech 13y ago

   Found it really interesting, I'm one of those that know nothing about FX, this has been very enlightening to me.
7. 7.▲
   by mguillech 13y ago

   I work for toptal ( http://www.toptal.com ) and we're proud of having a very well selected network of developers (top-notch devs screening each other, our "let through" ratio is 1:10 approximately), that solely will rule out inexperienced d