In article <9a827369-b36f-4a86-870a-e5a505e34...@q33g2000pra.googlegroups.com>, Vsevolod <vselo...@gmail.com> wrote: >On Apr 27, 8:18 pm, a...@pythoncraft.com (Aahz) wrote: >> >> If you want to talk about Python and problems you're running into, you >> should start a new thread. > >I'm not at that level of proficiency with the language. I believe most >of my technical problems are connected with lack of knowledge or >experience, not the language's features. While conceptual problems >seem futile to discuss. There's another saying: "when in Rome do as >the Romans do"
c.l.py isn't just for the experts; if you have a question along the lines of "here's something I do in Lisp, how do I do it in Python?", you're entirely on-topic. Also, most of us are happy to explain why Python does things in certain ways -- as with Lisp, the more you wrap your mind into the Python Way, the easier you'll find your work. Note that neither of these is "why isn't Python more like Lisp?", that's where you get into futility territory. ;-) -- Aahz (a...@pythoncraft.com) <*> http://www.pythoncraft.com/ "If you think it's expensive to hire a professional to do the job, wait until you hire an amateur." --Red Adair -- http://mail.python.org/mailman/listinfo/python-list
