"Rudy Rudolph" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]
>
> One thing that has always bothered me about Python is the lack of in-out
> parameters. Python is such a wonderful object-oriented language, but it
> lacks
> this feature that nearly every language has. Maybe we can fi
"Brett Cannon" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]
> See, this is what I am worried about. I **really** like not having to
> figure out what I need to do to read by lines from a file. If the
> FileStream object had an __iter__ that did the proper wrapping with
> LinedBuf
On 4/29/06, Steven Bethard <[EMAIL PROTECTED]> wrote:
> On 4/27/06, Guido van Rossum <[EMAIL PROTECTED]> wrote:
> > I just read PEP 3002 and while I like most of what I see (thanks
> > Steven Bethard!) there's one section that stands out as problematic.
> [snip]
> > Rather than a version of Python
On 4/27/06, Guido van Rossum <[EMAIL PROTECTED]> wrote:
> I just read PEP 3002 and while I like most of what I see (thanks
> Steven Bethard!) there's one section that stands out as problematic.
[snip]
> Rather than a version of Python
> 3000, I suggest to add such warning code to Python 2.x, and no
Rudy Rudolph wrote:
> I don't much care about the syntax. The proposed "inout" reserved word could
> be "ref" or "&" or "in out". We could even do "param : inout [type]".
> Whatever.
A more flexible approach would be to look at weakref.proxy and develop a
version that takes a strong reference to
On 4/29/06, Rudy Rudolph <[EMAIL PROTECTED]> wrote:
> One thing that has always bothered me about Python is the lack of in-out
> parameters. Python is such a wonderful object-oriented language, but it lacks
> this feature that nearly every language has. Maybe we can fix this in 3.0.
-1 since I can
On 4/29/06, Aahz <[EMAIL PROTECTED]> wrote:
> On Sat, Apr 29, 2006, Talin wrote:
> > My proposal is that we skip the middle portion of this process, and
> > pass the initial 4 collections directly to the called function.
>
> IIRC, you've already been asked to profile the machinery to find out
> whe
One thing that has always bothered me about Python is the lack of in-out
parameters. Python is such a wonderful object-oriented language, but it lacks
this feature that nearly every language has. Maybe we can fix this in 3.0.
There are two possibilities for how to do this: by reference or by copy
Georg Brandl wrote:
> They'll still have to type, pronounce and talk about English keywords, English
> operators and English standard library and 3rd-party module, class and method
> names, which makes a big percentage of code still Latin.
They don't have to understand the English meaning of the k
Guido van Rossum wrote:
>> > But Unicode has many alternative sets digits for which "isdigit" is
>> true.
>>
>> You mean, the Python isdigit() method? Sure, but the tokenizer uses
>> the C isdigit function, which gives true only for [0-9].
>
> Isn't that because it's only defined on 8-bit characte
On Sat, Apr 29, 2006, Talin wrote:
>
> My proposal is that we skip the middle portion of this process, and
> pass the initial 4 collections directly to the called function.
IIRC, you've already been asked to profile the machinery to find out
whether frame creation is still the primary bottleneck f
Antoine Pitrou <[EMAIL PROTECTED]> wrote:
>
> Le vendredi 28 avril 2006 à 23:14 -0700, Josiah Carlson a écrit :
> > Ultimately, PyGUI is essentially a wrapper of native or near-native
> > widgets into a common interface. wxPython is exactly the same thing,
> > only it has a much larger user base
greg.ewing at canterbury.ac.nz (Greg Ewing) writes:
>> given- much clearer and slightly more concise; or
>> ? - slightly clearer and much more concise ?
>
> That would be replacing something that's familiar to at least some
> people (even if they are geeks) with something that's famil
On 4/29/06, tomer filiba <[EMAIL PROTECTED]> wrote:
> i first thought on focusing on the socket module, because it's the part that
> bothers me most, but since people have expressed their thoughts on
> completely
> revamping the IO stack, perhaps we should be open to adopting new ideas,
> mainly fr
i first thought on focusing on the socket module, because it's the part thatbothers me most, but since people have expressed their thoughts on completelyrevamping the IO stack, perhaps we should be open to adopting new ideas,
mainly from the java/.NET world (keeping the momentum from the previous p
In the current implementation, a function call starts by gathering 4
collections of arguments:
-- The positional arguments, which are in a flat array
-- The keyword arguments, which are in a flat array of
keyword/value pairs.
-- The varargs argument, which is a reference to a sequence.
"Giovanni Bajo" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]
> There is simply no good enough solution for a GUI. There are far too many
> advanced different libraries with different wrappers.
>> The generic solution is better package fetching, such as apparently done
>> (I
>> ha
On 4/28/06, "Martin v. Löwis" <[EMAIL PROTECTED]> wrote:
> Guido van Rossum wrote:
> >> The distinction of letters and digits is also straight-forward:
> >> a digit is ASCII [0-9]; it's a separate lexical class only
> >> because it plays a special role in (number) literals. More
> >> generally, the
Oleg Broytmann wrote:
> On Sat, Apr 29, 2006 at 09:28:44AM +0200, Kay Schluehr wrote:
>> No one uses GTK+ on Windows.
>
>GAIM.
And Gimp, yes, but these only use it because they were originally
not made with a Windows port in mind.
Georg
___
Python
Raymond Hettinger <[EMAIL PROTECTED]> writes:
> Good question. To see the answer, look at a code tranformation from:
>
> if file_ext.lower() in set(['html', 'xml', 'xhtml']):
> handle(filename)
>
> into:
>
>
> if file_ext.lower() in {'html', 'xml', 'xhtml'}:
> handle(filen
Nick Coghlan <[EMAIL PROTECTED]> writes:
> If we change that, we can use it to support an alternate invocation
> syntax for functions that currently expect an iterable as their
> first argument. "EXPR{ARGS}" would be equivalent to "EXPR((ARGS,))",
> with the following differences in the parsing of
On Sat, Apr 29, 2006 at 09:28:44AM +0200, Kay Schluehr wrote:
> No one uses GTK+ on Windows.
GAIM.
Oleg.
--
Oleg Broytmannhttp://phd.pp.ru/[EMAIL PROTECTED]
Programmers don't die, they just GOSUB without RETURN.
_
Johan Dahlin schrieb:
>>No one uses GTK+ on Windows.
>>
>>
>
>Quite a few application does.
>
>The most popular application is Bittorrent, which has used it for quite
>some time. And Bittorrent is probably the most used python application.
>
>Johan
>
>
I don't want to insist on this point. T
Kay Schluehr wrote:
> Bill Janssen schrieb:
>
>> I mentioned this a couple of weeks ago, and here it is again.
>>
>> The biggest wart in Python 2, the one that forces me to use another
>> language, is the lack of a standard GUI. By standard, I mean that
>> when you install Python on a system, the
Martin v. Löwis wrote:
> Guido van Rossum wrote:
>>> I was hoping to propose a PEP on non-ASCII identifiers some
>>> day; that would (of course) include a requirement that the
>>> standard library would always be restricted to ASCII-only
>>> identifiers as a style-guide.
>>
>> IMO communication ab
Bill Janssen wrote:
> Terry, "popular" isn't the goal of Python 3000. Nor is "backwards
> compatibility"
Well, I would certainly hope that a certain amount of popularity is a
goal, or Python3k could be the best language that no one is using.
Mike
--
Michael P. Soulier <[EMAIL PROTECTED]>
"An
Kay Schluehr wrote:
> No one uses GTK+ on Windows.
Actually, I believe that WingIDE is done with PyGTK, on both Linux and
Windows.
Mike
--
Michael P. Soulier <[EMAIL PROTECTED]>
"Any intelligent fool can make things bigger and more complex... It
takes a touch of genius - and a lot of courage t
Paul Moore wrote:
> One downside, which I only point out because someone will, is that
> optimization opportunities will be lost for the usual reason - the
> optimizer can't be sure that set (or whatever) hasn't been reassigned.
> But I still see that as something to be addressed independently, if
Le vendredi 28 avril 2006 à 23:14 -0700, Josiah Carlson a écrit :
> Ultimately, PyGUI is essentially a wrapper of native or near-native
> widgets into a common interface. wxPython is exactly the same thing,
> only it has a much larger user base, developer support, and (native and
> emulated) platf
Le samedi 29 avril 2006 à 02:07 -0400, Tim Peters a écrit :
> If you don't remember these confusions, I think it should suffice to
> remind that Perl's join() does take the separator first (which is
> essentially forced in Perl, given its odd LIST syntax):
PHP's join does too, also some versions h
On 4/29/06, Nick Coghlan <[EMAIL PROTECTED]> wrote:
> However, I'm now -0 on having a set literal at all, and it's because I believe
> we can solve this problem in a more general fashion that applies to more
> functions than just the set() constructor.
>
> Currently, [] and () can appear both stand
> Ultimately, PyGUI is essentially a wrapper of native or near-native
> widgets into a common interface.
Have you read the PyGUI code? It's really more of an abstract API
that exploits certain bundles of functionality provide by
already-implemented toolkits for its implementation. It could
certa
> Tough sell to my coworkers who just install the
> JDK+Netbeans and have it all included, on any platform that I work on.
Yep, that's the problem in a nutshell.
Not standardizing a GUI system was an acceptable answer before Java,
but it won't wash in the 21st century. Of course, wxPython, PyGTK
Terry Reedy writes:
> To me, your logic is backwards. wxWidgets/wxPython are popular and have
> perhaps the highest usage (not counting IDLE) by voluntary choice.
Terry, "popular" isn't the goal of Python 3000. Nor is "backwards
compatibility" -- Py3K is about breaking compatibility. "Getting
Bill Janssen schrieb:
>I mentioned this a couple of weeks ago, and here it is again.
>
>The biggest wart in Python 2, the one that forces me to use another
>language, is the lack of a standard GUI. By standard, I mean that
>when you install Python on a system, the GUI toolkit is also
>installed.
35 matches
Mail list logo
