In his first article about Jython, Noel Rappin discussed the features of the Python scripting language and its Jython implementation that would be of greatest interest to Java programmers. Jython is a complete implementation of the Python programming language written in 100% pure Java, and allows easy access to Java libraries. This article contains 10 tips for using Java objects in Jython.
Jython Tips for Python Programmers
About The Author
Eugenia Loli
Ex-programmer, ex-editor in chief at OSNews.com, now a visual artist/filmmaker.
Follow me on Twitter @EugeniaLoli
<flamebait>
Those underscores and colons kill me! I can’t stand them.
Don’t the designers understand that it is much better to have keywords than symbols. Look at C# and VB. Very little symbol usage. Look at Java, almost no symbol usage. Those were created by people who did a lot of research on user friendliness (especially MS). I don’t think that it matters much for the compiler/interpereter that keywords are used instead of symbols, but it matters a lot to a significant number of programmers (at least me).
</flamebait>
perhaps my comment did get to you after all
take care Eugenia
nice *another* spinoff.. how useful.
Python and Jython usually use the underscore characters for magic methods and, by convention, some private variables. Except for the __init__ constructor in a class you can usually do without them. Colons are usually used in place of braces: one colon usually does the work of two braces (in Java, C#).
Python has some of the most readable code around. Ever look at Perl code? Ever look at the code of another Java or C# programmer who uses braces differently than you do? Ever check out C/C++ code with all the pointer and reference symbols? VB? If you happen to think VB is some kind of paradigmn, you are a discrace.
Underscores? OK, about 2/3 of the way into the article, underscores show up in identifiers like “__init__”, but they’re not symbols, just a distinctive spelling notation for a type of special built in identifier. That was what killed you? You wouldn’t maybe have skipped the article and failed to notice that it isn’t about Perl?
I don’t think spinoff is an issue. This Java Python has historically been enthusiastically supported by the author of the C version. At worst, it’s kind of an impediment, because at least one very useful feature of the C implementation (immediate finalization of unreferenced objects) can’t be supported by the Java version, so it isn’t an official feature. Least common denominator.
>Python has some of the most readable code around
It’s not about readability, it’s about writability.
No it’s about being able to read some code you two years ago
and not having it look like complete gibbish.