Martin v. Löwis wrote:
> What's wrong with the rfe type? Why does it have to be a keyword?
For one it's the name. Personally I didn't know the meaning of RFE until
I googled it.
Christian
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.py
Benjamin Peterson schrieb:
> Hi,
> What is the policy regarding nosy lists? Is it appropriate it add people
> to it besides oneself? As I cannot assign items, I'm sometimes tempted
> to add someone relevant to the list. (ie Should I add Georg to
> documentation related issues?)
In my case, yes
On Feb 18, 2008, at 1:21 PM, Jeroen Ruigrok van der Werven wrote:
> A bug tracker is a much better way of registering such information.
> It also
> can be easier referenced in the future since even though when it is
> closed,
> the debate and other stuff will remain in the tracker's tickets for
> IIUC, RFC 4217 mandates that a TLS shutdown is exchanged (although they
> apparently didn't read the TLS spec when they wrote the RFC, as the
I'm pretty dubious about section 5 there. I don't think reverting to
a plaintext state, once you've been in TLS, happens in real life to
real connections
On Feb 19, 2008 6:15 PM, Steve Holden <[EMAIL PROTECTED]> wrote:
> Steve Holden wrote:
> [...]
> > The one that surprised me was the legality of
> >
> > def eggs((a, )=c):
> > pass
> >
> > That just seems like unpacking-abuse to me.
> >
> Needless to say, a call that tries to *use* th
Okay, my conclusion is
def f((a)=5)
is wrong, and the code should be changed to report a better error
message. I'll file a bug against that.
and I'm going with Brett suggestion that
[x for x in 1,]
is not supported because it's almost certainly a programming error. I
think therefore the
> I haven't looked closely at the Python tracker, but I noticed that you
> have a "busybody" detector. I thought that requesting to be on the
> nosy list was what this detector was for?
No. We also have a mailing list (python-bugs) to which any tracker
change is mailed. That's the busybody list.
> Perhaps that would be nice, but switching to plain-text use of the
> socket can be coordinated outside the SSL protocol. I had an accessor
> for SSL_shutdown, in an earlier version, but there were semantic
> conflicts with the socket shutdown() method, and I didn't think anyone
> would use it an
Steve Holden wrote:
[...]
> The one that surprised me was the legality of
>
> def eggs((a, )=c):
> pass
>
> That just seems like unpacking-abuse to me.
>
Needless to say, a call that tries to *use* the default value fails
horribly, as the parameter form does require an iterable:
2008/2/19, "Martin v. Löwis" <[EMAIL PROTECTED]>:
> >> Problem is, we don't have an 'rfe' keyword anymore :)
> >
> > Shall we grow one again?
>
> What's wrong with the rfe type? Why does it have to be a keyword?
For me, none. I'm just trying to converge the mail thread to a result, :)
As far as
Andrew Dalke wrote:
> On Feb 19, 2008 1:38 PM, Andrew Dalke <[EMAIL PROTECTED]> wrote:
>> def spam((a) = c):
>> print a
>
> On Feb 20, 2008 12:29 AM, Brett Cannon <[EMAIL PROTECTED]> wrote:
[..]
>> Are you asking why the decision was made to make the expression
>> illegal, or why the grammar is
> But shouldn't there be a way to invoke SSL_shutdown? You need to get
> the close_notify alert message sent, IIUC.
Perhaps that would be nice, but switching to plain-text use of the
socket can be coordinated outside the SSL protocol. I had an accessor
for SSL_shutdown, in an earlier version, but
"Martin v. Löwis" writes:
> > What is the policy regarding nosy lists? Is it appropriate it add people
> > to it besides oneself? As I cannot assign items, I'm sometimes tempted
> > to add someone relevant to the list. (ie Should I add Georg to
> > documentation related issues?)
>
> I wo
On Feb 19, 2008 1:38 PM, Andrew Dalke <[EMAIL PROTECTED]> wrote:
> def spam((a) = c):
> print a
On Feb 20, 2008 12:29 AM, Brett Cannon <[EMAIL PROTECTED]> wrote:
> The error might be odd, but I don't see why that should be allowed
> syntax. Having a parameter surrounded by a parentheses like tha
On Feb 19, 2008 1:38 PM, Andrew Dalke <[EMAIL PROTECTED]> wrote:
> I'm finishing up a PLY lexer and parser for the current CVS version of
> the Python grammar. As part of it I've been testing a lot of dark
> corners in the grammar definition and implementation. Python 2.5 has
> some small and rar
> What is the policy regarding nosy lists? Is it appropriate it add people
> to it besides oneself? As I cannot assign items, I'm sometimes tempted
> to add someone relevant to the list. (ie Should I add Georg to
> documentation related issues?)
I would find it appropriate. In theory, there sho
> I suggest using socket.dup(sslsock) to simply create a non-encrypted
> copy of the socket, and switch to using that copy. There's no way to
> "unwrap" an SSLSocket.
But shouldn't there be a way to invoke SSL_shutdown? You need to get
the close_notify alert message sent, IIUC.
Regards,
Martin
_
>> Problem is, we don't have an 'rfe' keyword anymore :)
>>
>
> Shall we grow one again?
What's wrong with the rfe type? Why does it have to be a keyword?
Regards,
Martin
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/
Hi,
What is the policy regarding nosy lists? Is it appropriate it add people to
it besides oneself? As I cannot assign items, I'm sometimes tempted to add
someone relevant to the list. (ie Should I add Georg to documentation
related issues?)
Thanks for your patience,
Benjamin
--
Benjamin Peterso
> We really do need to write some of this down in an information track PEP
> so we're all using the same values to mean the same thing...
There is actually an official meaning to pending: An issue marked
pending will get automatically closed by the tracker after some period
of time (which used t
I'm finishing up a PLY lexer and parser for the current CVS version of
the Python grammar. As part of it I've been testing a lot of dark
corners in the grammar definition and implementation. Python 2.5 has
some small and rare problems which I'm pleased to note have been
pretty much fixed in Pytho
On Feb 19, 2008 12:22 PM, Facundo Batista <[EMAIL PROTECTED]> wrote:
> 2008/2/19, Georg Brandl <[EMAIL PROTECTED]>:
>
> > Problem is, we don't have an 'rfe' keyword anymore :)
>
> Shall we grow one again?
Isn't the RFE type field enough?
> What would happen with PEP 42? will it be deprecated?
I
On Fri, Feb 15, 2008 at 10:53:14PM -0500, Mark Dickinson wrote:
>* New float methods: is_finite, is_inf, is_integer and is_nan.
>* New cmath functions: phase, polar and rect, isinf and isnan.
>* New complex method: is_finite.
This may be a dumb question, but is there any particular rea
Facundo Batista wrote:
> What would happen with PEP 42? will it be deprecated?
It seems 42 isn't the answer at all. What a shame. *scnr* :)
Christian
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
2008/2/19, Georg Brandl <[EMAIL PROTECTED]>:
>
> Problem is, we don't have an 'rfe' keyword anymore :)
>
Shall we grow one again?
What would happen with PEP 42? will it be deprecated?
--
.Facundo
Blog: http://www.taniquetil.com.ar/plog/
PyAr: http://www.python.org/ar/
___
Nick Coghlan schrieb:
> Brett Cannon wrote:
>> My issue with keeping the RFEs in the tracker as they are is that it
>> artificially inflates the open issue count. Python does not have over
>> 1,700 open bugs.
>
> That's a problem with our status reporting, not with the fact that there
> are RFE's
Lisandro Dalcin wrote:
> On 2/11/08, Travis Oliphant <[EMAIL PROTECTED]> wrote:
>> My perception is that you are seeing too much of a connection between
>> the C-compiler and the PEP description of memory. Perhaps that's not
>> it, and I'm missing something else.
>>
>
> Travis, all this make me
> I've read through ssl.py but I didn't notice anything useful.
> It seems that ssl.SSLSocket class does not provide any method/facility
> to switch back to a plain text socket state.
I suggest using socket.dup(sslsock) to simply create a non-encrypted
copy of the socket, and switch to using that
Nick Coghlan wrote:
> We've also veered fairly far off topic for the Py3k list - further ideas
> for positional-only argument syntax or decorators should probably be
> kicked around on python-ideas rather than here or python-dev.
For a function specification like this:
def f(w, x=1, *, y,
On Tue, Feb 19, 2008, Nick Coghlan wrote:
> Brett Cannon wrote:
>>
>> My issue with keeping the RFEs in the tracker as they are is that it
>> artificially inflates the open issue count. Python does not have over
>> 1,700 open bugs.
>
> That's a problem with our status reporting, not with the fact
Christian Heimes wrote:
> Steve Holden wrote:
>> There there's the Status field. I understand "open" and "closed", but
>> what's the semantic of "pending". Is it awaiting triage, awaiting status
>> assignment, or what?
>
> I've used pending for two states. For one I've put an issue on pending
>
Brett Cannon wrote:
> My issue with keeping the RFEs in the tracker as they are is that it
> artificially inflates the open issue count. Python does not have over
> 1,700 open bugs.
That's a problem with our status reporting, not with the fact that there
are RFE's in the issue tracker ;)
Adding
Hi all,
I'm trying to extend the base ftplib module to add SSL/TLS support as
described in RFC-4217 (see also issue 2054).
RFC-4217 defines a certain command ("CCC") which permit to return to a
plain text socket state without closing the connection.
That is useful since that, being FTP a port-hoppi
On 2/19/08, Virgil Dupras <[EMAIL PROTECTED]> wrote:
> closed_status = db.status.lookup('chatting')
Oops, replace 'chatting' with 'closed'
Virgil
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubs
On 2/19/08, "Martin v. Löwis" <[EMAIL PROTECTED]> wrote:
> > No, I don't, which is why I would find it interesting to run some
> > queries on the roundup database to have completion statistics for low
> > activity tickets. Is is possible to get a copy of that db somehow?
>
> I would rather not make
Steve Holden wrote:
> There there's the Status field. I understand "open" and "closed", but
> what's the semantic of "pending". Is it awaiting triage, awaiting status
> assignment, or what?
I've used pending for two states. For one I've put an issue on pending
state when it was fixed on the trun
> No, I don't, which is why I would find it interesting to run some
> queries on the roundup database to have completion statistics for low
> activity tickets. Is is possible to get a copy of that db somehow?
I would rather not make it available, as it contains certain
privacy-related information
37 matches
Mail list logo
