2011/5/20 Gabriel Jacobo <gabo...@gmail.com>: > On Vie 20 May 2011 16:47:54 Benjamin Peterson escribió: >> 2011/5/20 Gabriel Jacobo <gabo...@gmail.com>: >> > On Vie 20 May 2011 13:44:15 Benjamin Peterson escribió: >> >> 2011/5/20 Gabriel Jacobo <gabo...@gmail.com>: >> >> > On Jue 19 May 2011 20:59:49 Benjamin Peterson escribió: >> >> >> 2011/5/19 Gabriel Jacobo <gabo...@gmail.com>: >> >> >> > Hi All! I have a quick question for the RPython gurus, are >> >> >> > properties supported? >> >> >> >> >> >> No. >> >> > >> >> > Ok, thanks for the answer. How would you grade the difficulty in >> >> > implementing them (Considering I have plenty of Python experience but >> >> > almost none with PyPy or RPython)? Any pointers as to how to implement >> >> > them? Are they a desired feature for RPython? >> >> >> >> Generally, we try to avoid adding new feature to the RPython language. >> >> Usually, there's a simpler way to achieve what you want. >> > >> > I have a good chunk of python code that uses properties all around, and I >> > wanted to see if I can run it through the pypy machinery and eventually >> > come the other side with a javascript end product (via RPythonic). Do >> > you have any suggestions as to best solve this situation? (Preprocessing >> > the code somehow perhaps?) >> >> Uh, the javascript backend doesn't really work anymore. > > I'm not using the javascript backend, I mentioned I'm using RPythonic which > goes with the LLVM->Emscripten->Javascript route. No ideas on a property > workaround?
You could rewrite to have getters like get_my_attr or some such. Using RPython for random projects is not really supported... -- Regards, Benjamin _______________________________________________ pypy-dev mailing list pypy-dev@python.org http://mail.python.org/mailman/listinfo/pypy-dev
