Landscape painting is a term that covers the depiction of natural scenery such as mountains, valleys, trees, rivers, and forests, and especially art where the main subject is a wide view, with its elements arranged into a coherent composition. In other works landscape backgrounds for figures can still form an important part of the work. Sky is almost always included in the view, and weather is often an element of the composition. Detailed landscapes as a distinct subject are not found in all artistic traditions, and develop when there is already a sophisticated tradition of representing other subjects. The two main traditions spring from Western painting and Chinese art, going back well over a thousand years in both cases.
... the keyword starting the line that heads a block draws a lot of attention to it. This is true for "if", "while", "for", "try", "def" and "class". But the "using" keyword (or any other keyword in its place) doesn't deserve that attention; the emphasis should be on the decorator or decorators inside the suite, since those are the important modifiers to the function definition that follows. ...
The discussion continued on and off on python-dev from February 2002 through July 2004. Hundreds and hundreds of posts were made, with people proposing many possible syntax variations. Guido took a list of proposals to EuroPython 2004 , where a discussion took place. Subsequent to this, he decided that we'd have the Java-style  @decorator syntax, and this appeared for the first time in 2.4a2. Barry Warsaw named this the 'pie-decorator' syntax, in honor of the Pie-thon Parrot shootout which occurred around the same time as the decorator syntax, and because the @ looks a little like a pie. Guido outlined his case  on Python-dev, including this piece  on some of the (many) rejected forms.
In Python 2.4a3 (to be released this Thursday), everything remains as currently in CVS. For 2.4b1, I will consider a change of @ to some other single character, even though I think that @ has the advantage of being the same character used by a similar feature in Java. It's been argued that it's not quite the same, since @ in Java is used for attributes that don't change semantics. But Python's dynamic nature makes that its syntactic elements never mean quite the same thing as similar constructs in other languages, and there is definitely significant overlap. Regarding the impact on 3rd party tools: IPython's author doesn't think there's going to be much impact; Leo's author has said that Leo will survive (although it will cause him and his users some transitional pain). I actually expect that picking a character that's already used elsewhere in Python's syntax might be harder for external tools to adapt to, since parsing will have to be more subtle in that case. But I'm frankly undecided, so there's some wiggle room here. I don't want to consider further syntactic alternatives at this point: the buck has to stop at some point, everyone has had their say, and the show must go on.
Categories: English 2-syllable wordsEnglish terms with IPA pronunciationEnglish terms with audio linksEnglish words suffixed with -er (agent noun)English terms derived from Middle FrenchEnglish lemmasEnglish nounsEnglish countable nounsEnglish terms with obsolete sensesen:NauticalAmerican EnglishEnglish agent nounsEnglish terms with multiple etymologiesen:Artistsen:People