On Mon, Jan 30, 2012 at 2:51 PM, Ethan Furman wrote:
> raise ... from ... is not disallowed outside a try block, but this
> behavior is not guaranteed to remain.
>
> --
>
> Should that last disclaimer be there? Should it be changed?
Latest addition for PEP 409 has been sent. Text follows:
Language Details
Currently, __context__ and __cause__ start out as None, and then get set
as exceptions occur.
To support 'from None', __context__ will stay as it is, but __cause__
will start out as False, and will chang
On Sat, Jan 28, 2012 at 3:07 PM, Benjamin Peterson wrote:
> But why would you want to pass a float? It seems like API abuse to me.
>
Agreed. Anything else seems meaningless.
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailma
I still have gdb 6.somthing,
would you mail me the full output please,
so I can see what the problem is.
It's done, let me know if you need more output.
Cheers,
francis
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman
I think an advocacy of 3rd party modules would start with modules such as
ipaddr, requests, regex. Linking directly to them from the python core
documentation, while requesting they hold a successful moratorium in order
to be included in a later standard module release.
On Jan 30, 2012 10:47 AM, "N
>> import threading
>> s = threading.Semaphore(0.5)
>
> But why would you want to pass a float? It seems like API abuse to me.
If something should be changed, Semaphore(arg) should raise a
TypeError if arg is not an integer.
Victor
___
Python-Dev mailin
On Mon, Jan 30, 2012 at 8:44 AM, Barry Warsaw wrote:
> Nothing beats people beating on it heavily for years in production code to
> shake things out. I often think a generic answer to "did I get the API right"
> could be "no, but it's okay" :)
Heh, my answer to complaints about the urrlib (etc)
Mark Shannon wrote:
Antoine Pitrou wrote:
On Sun, 29 Jan 2012 09:56:11 -0500
Benjamin Peterson wrote:
2012/1/29 Mark Shannon :
Hi,
Now that issue 13703 has been largely settled,
I want to propose my new dictionary implementation again.
It is a little more polished than before.
If you're se
Matt Joiner wrote:
Mark, Good luck with getting this in, I'm also hopeful about coroutines,
maybe after pushing your dict optimization your coroutine implementation
will get more consideration.
Shush, don't say the C word or you'll put people off ;)
I'm actually not that fussed about the coro
>> Please clarify the status of that code: are you actually proposing
>> 6a21f3b35e20 for inclusion into Python as-is? If so, please post it
>> as a patch to the tracker, as it will need to be reviewed (possibly
>> with requests for further changes).
>
> I thought it already was a patch. What do I
> I... I think I might have already done this, inadvertently. I
> needed an x64 VS2010 debug build of Subversion/APR*/Python a few
> weeks ago -- forgetting the fact that we're still on VS2008.
There is a lot of duplication of work going on here: at least four
people have done the sam
Martin v. Löwis wrote:
Now that issue 13703 has been largely settled,
I want to propose my new dictionary implementation again.
It is a little more polished than before.
Please clarify the status of that code: are you actually proposing
6a21f3b35e20 for inclusion into Python as-is? If so, pleas
On Jan 28, 2012, at 07:29 PM, Guido van Rossum wrote:
>Finally, if you really want to put warnings in whenever an
>experimental module is being used, make it a silent warning, like
>SilentDeprecationWarning. That allows people to request more strict
>warnings without unduly alarming the users of a
francis wrote:
On 01/29/2012 11:31 AM, Mark Shannon wrote:
It passes all the tests.
(I had to change a couple that relied on dict repr() ordering)
Hi Mark,
I've cloned the repo, build it the I've tried with ./python -m test. I
got some errors:
First in general:
340 tests OK.
2 tests failed:
> Now that issue 13703 has been largely settled,
> I want to propose my new dictionary implementation again.
> It is a little more polished than before.
Please clarify the status of that code: are you actually proposing
6a21f3b35e20 for inclusion into Python as-is? If so, please post it
as a patch
On 29 January 2012 21:39, Gregory P. Smith wrote:
> An example of this working: ipaddr is ready to go in. It got the
> eyeballs and API modifications while still a pypi library as a result
> of the discussion around the time it was originally suggested as being
> added. I or any other committers
On 01/29/2012 11:31 AM, Mark Shannon wrote:
It passes all the tests.
(I had to change a couple that relied on dict repr() ordering)
Hi Mark,
I've cloned the repo, build it the I've tried with ./python -m test. I
got some errors:
First in general:
340 tests OK.
2 tests failed:
test_dis te
On Fri, Jan 27, 2012 at 9:26 AM, Alex wrote:
> Eli Bendersky gmail.com> writes:
>
>>
>> Hello,
>>
>> Following an earlier discussion on python-ideas [1], we would like to
>> propose the following PEP for review. Discussion is welcome. The PEP
>> can also be viewed in HTML form at
>> http://www.py
On Fri, Jan 27, 2012 at 6:33 PM, Benjamin Peterson wrote:
> 2012/1/27 Steven D'Aprano :
>> Benjamin Peterson wrote:
>>>
>>> Hello everyone,
>>> In effort to get a fix out before Perl 6 goes mainstream, Barry and I
>>> have decided to pronounce on what we want for our stable releases.
>>> What we h
On Fri, Jan 27, 2012 at 11:39 AM, wrote:
>
> In fact, none of the strategies fixes all issues with hash collisions;
> even the hash-randomization solutions only deal with string keys, and
> don't consider collisions on non-string keys.
The hash-randomization approach also works fine on immutable
On Sun, Jan 29, 2012 at 17:34, Andrea Crotti wrote:
> I have a newbie question about CPython.
> Looking at the C code I noted that for example in tupleobject.c there is
> only one include
> #include "Python.h"
>
> Python.h actually includes everything as far as I can I see so:
> - it's very hard w
On 01/29/2012 06:34 PM, Paul Moore wrote:
On 29 January 2012 18:10, C. Titus Brown wrote:
python-dev isn't that inappropriate, IMO, but probably the best place to
go with this discussion is python-ideas. Could you repost over there?
I agree that python-dev isn't particularly appropriate, pyth
On 29 January 2012 18:10, C. Titus Brown wrote:
> python-dev isn't that inappropriate, IMO, but probably the best place to
> go with this discussion is python-ideas. Could you repost over there?
I agree that python-dev isn't particularly appropriate, python-list is
probably your best bet. The py
On Sun, Jan 29, 2012 at 05:59:51PM +, Andrea Crotti wrote:
> On 01/29/2012 05:22 PM, Oleg Broytman wrote:
>> Hello.
>>
>> We are sorry but we cannot help you. This mailing list is to work on
>> developing Python (adding new features to Python itself and fixing bugs);
>> if you're having pro
On 01/29/2012 05:22 PM, Oleg Broytman wrote:
Hello.
We are sorry but we cannot help you. This mailing list is to work on
developing Python (adding new features to Python itself and fixing bugs);
if you're having problems learning, understanding or using Python, please
find another forum. Pro
Hello.
We are sorry but we cannot help you. This mailing list is to work on
developing Python (adding new features to Python itself and fixing bugs);
if you're having problems learning, understanding or using Python, please
find another forum. Probably python-list/comp.lang.python mailing list/
Antoine Pitrou wrote:
On Sun, 29 Jan 2012 09:56:11 -0500
Benjamin Peterson wrote:
2012/1/29 Mark Shannon :
Hi,
Now that issue 13703 has been largely settled,
I want to propose my new dictionary implementation again.
It is a little more polished than before.
If you're serious about changing
I have a newbie question about CPython.
Looking at the C code I noted that for example in tupleobject.c there is
only one include
#include "Python.h"
Python.h actually includes everything as far as I can I see so:
- it's very hard with a not-enough smart editor to find out where the
not-locally
Antoine Pitrou wrote:
Hi,
On Sun, 29 Jan 2012 10:31:48 +
Mark Shannon wrote:
Now that issue 13703 has been largely settled,
I want to propose my new dictionary implementation again.
It is a little more polished than before.
https://bitbucket.org/markshannon/hotpy_new_dict
I briefly took
2012/1/29 Antoine Pitrou :
> On Sun, 29 Jan 2012 09:56:11 -0500
> Benjamin Peterson wrote:
>
>> 2012/1/29 Mark Shannon :
>> > Hi,
>> >
>> > Now that issue 13703 has been largely settled,
>> > I want to propose my new dictionary implementation again.
>> > It is a little more polished than before.
>
On Sun, 29 Jan 2012 09:56:11 -0500
Benjamin Peterson wrote:
> 2012/1/29 Mark Shannon :
> > Hi,
> >
> > Now that issue 13703 has been largely settled,
> > I want to propose my new dictionary implementation again.
> > It is a little more polished than before.
>
> If you're serious about changing t
2012/1/29 Mark Shannon :
> Hi,
>
> Now that issue 13703 has been largely settled,
> I want to propose my new dictionary implementation again.
> It is a little more polished than before.
If you're serious about changing the dictionary implementation, I
think you should write a PEP. It should explai
Hi,
On Sun, 29 Jan 2012 10:31:48 +
Mark Shannon wrote:
>
> Now that issue 13703 has been largely settled,
> I want to propose my new dictionary implementation again.
> It is a little more polished than before.
>
> https://bitbucket.org/markshannon/hotpy_new_dict
I briefly took a look at y
Hi,
Now that issue 13703 has been largely settled,
I want to propose my new dictionary implementation again.
It is a little more polished than before.
https://bitbucket.org/markshannon/hotpy_new_dict
Object-oriented benchmarks use considerably less memory and are
sometimes faster (by a small am
Am 29.01.2012 08:42, schrieb Ethan Furman:
> Benjamin Peterson wrote:
>> 2012/1/26 Ethan Furman :
>>> PEP: XXX
>>
>> Congratulations, you are now PEP 409.
>
> Thanks, Benjamin!
>
> So, how do I make changes to it?
Please send PEP updates to the PEP editors at p...@python.org.
Georg
__
For those not on the nosy list, here's the latest post
to http://bugs.python.org/issue6210:
---
It looks like agreement is forming around the
raise ... from None
method. It has been mentioned more than once that having the context
saved
Benjamin Peterson wrote:
2012/1/26 Ethan Furman :
PEP: XXX
Congratulations, you are now PEP 409.
Thanks, Benjamin!
So, how do I make changes to it?
~Ethan~
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/
37 matches
Mail list logo
