On 7/26/2010 7:36 AM, Guido van Rossum wrote:
According to CSP advicates, this approach will break down when you
need more than 8-16 cores since cache coherence breaks down at 16
cores. Then you would have to figure out a message-passing approach
(but the messages would have to be very fast).
2010/7/29 Nick Coghlan :
> On Thu, Jul 29, 2010 at 8:57 AM, Jesse Noller wrote:
>> I thought at the last two pycons, we've all discussed that we should
>> have a system in place for marking tests *and* modules within the
>> stdlib as "will only work on FooPython". I suspect that it's waiting
>> on
On Thu, Jul 29, 2010 at 8:10 AM, Nick Coghlan wrote:
> On Thu, Jul 29, 2010 at 8:57 AM, Jesse Noller wrote:
>> I thought at the last two pycons, we've all discussed that we should
>> have a system in place for marking tests *and* modules within the
>> stdlib as "will only work on FooPython". I su
On Thu, Jul 29, 2010 at 8:57 AM, Jesse Noller wrote:
> I thought at the last two pycons, we've all discussed that we should
> have a system in place for marking tests *and* modules within the
> stdlib as "will only work on FooPython". I suspect that it's waiting
> on the shared-stdlib effort, whic
On 28/07/2010 23:57, Jesse Noller wrote:
On Wed, Jul 28, 2010 at 5:20 PM, Benjamin Peterson wrote:
2010/7/25 Stefan Behnel:
Nick Coghlan, 25.07.2010 08:29:
We knew PEP 380 would be hurt by the moratorium when the moratorium
PEP went through.
The goals of the moratorium itse
On Wed, Jul 28, 2010 at 5:20 PM, Benjamin Peterson wrote:
> 2010/7/25 Stefan Behnel :
>> Nick Coghlan, 25.07.2010 08:29:
>>>
>>> We knew PEP 380 would be hurt by the moratorium when the moratorium
>>> PEP went through.
>>>
>>> The goals of the moratorium itself, in making it possible to have a
>>>
On 28/07/2010 22:20, Benjamin Peterson wrote:
2010/7/25 Stefan Behnel:
Nick Coghlan, 25.07.2010 08:29:
We knew PEP 380 would be hurt by the moratorium when the moratorium
PEP went through.
The goals of the moratorium itself, in making it possible to have a
3.2 release that is fully s
2010/7/25 Stefan Behnel :
> Nick Coghlan, 25.07.2010 08:29:
>>
>> We knew PEP 380 would be hurt by the moratorium when the moratorium
>> PEP went through.
>>
>> The goals of the moratorium itself, in making it possible to have a
>> 3.2 release that is fully supported by all of the major Python
>> i
On Mon, Jul 26, 2010 at 12:00 PM, Michael Foord
wrote:
> At Resolver Systems we created a "calculation system" that does large
> calculations on background threads using IronPython. Doing them on a
> background thread allows the ui to remain responsive. Several calculations
> could run simultaneou
Steve Holden writes:
> > Only if they have similar look and feel, and don't require you to
> > register the same login N times, though.
> >
> Is it really time to give devs a distributed identity good for a range
> of systems? Sounds like a potentially hairy management task.
Sure, but Pytho
Am 27.07.2010 12:49, schrieb Steve Holden:
> On 7/27/2010 11:02 AM, Antoine Pitrou wrote:
>> On Tue, 27 Jul 2010 09:57:22 +0200
>> Georg Brandl wrote:
>>
>>> Am 27.07.2010 04:43, schrieb Terry Reedy:
On 7/26/2010 5:15 PM, Georg Brandl wrote:
> Sure PyPI is part of the ecosystem. Bu
On 7/27/2010 11:02 AM, Antoine Pitrou wrote:
> On Tue, 27 Jul 2010 09:57:22 +0200
> Georg Brandl wrote:
>
>> Am 27.07.2010 04:43, schrieb Terry Reedy:
>>> On 7/26/2010 5:15 PM, Georg Brandl wrote:
>>>
Sure PyPI is part of the ecosystem. But so are quite a lot of other tools,
and none o
On Tue, 27 Jul 2010 09:57:22 +0200
Georg Brandl wrote:
> Am 27.07.2010 04:43, schrieb Terry Reedy:
> > On 7/26/2010 5:15 PM, Georg Brandl wrote:
> >
> >> Sure PyPI is part of the ecosystem. But so are quite a lot of other tools,
> >> and none of them are tracked in bugs.python.org. (This is al
2010/7/27 "Martin v. Löwis" :
>> I would classify the changes in three kinds:
>>
>> - minor: a new feature, a UI bugfix etc
>> - important: a new feature that changes a lot the end-user experience
>> (like the rating system)
>> - major: a change to the APIs (HTTP/XML-RPC)
>>
>> I think you should b
Am 27.07.2010 04:43, schrieb Terry Reedy:
> On 7/26/2010 5:15 PM, Georg Brandl wrote:
>
>> Sure PyPI is part of the ecosystem. But so are quite a lot of other tools,
>> and none of them are tracked in bugs.python.org. (This is also the case
>> for the website.) I'd really like bugs.python.org t
Terry Reedy wrote:
Should CPython be optimized for 1, 2, 3, or 4 or more cores?
The answer to this is obviously changing. I will soon replace a single
core with a 4/6 core machine,
I don't think you can answer that just by considering the average
number of cores in a CPU. Even if my CPU has 4
> I would classify the changes in three kinds:
>
> - minor: a new feature, a UI bugfix etc
> - important: a new feature that changes a lot the end-user experience
> (like the rating system)
> - major: a change to the APIs (HTTP/XML-RPC)
>
> I think you should briefly present your plans for import
On 7/26/2010 5:15 PM, Georg Brandl wrote:
Sure PyPI is part of the ecosystem. But so are quite a lot of other tools,
and none of them are tracked in bugs.python.org. (This is also the case
for the website.) I'd really like bugs.python.org to remain a tracker for
what we ship as the CPython di
On Mon, Jul 26, 2010 at 11:57 PM, "Martin v. Löwis" wrote:
>> Basically, I think what you'd like to have is Martin saying "I'm going to
>> work on this feature", in addition to "I implemented this feature now"
>> afterwards. That shouldn't be too hard.
>
> I'm not very good at blogging (more spec
> Basically, I think what you'd like to have is Martin saying "I'm going to
> work on this feature", in addition to "I implemented this feature now"
> afterwards. That shouldn't be too hard.
I'm not very good at blogging (more specifically, I never blog).
People interested in following even the
On Mon, Jul 26, 2010 at 11:15 PM, Georg Brandl wrote:
..
> Sure PyPI is part of the ecosystem. But so are quite a lot of other tools,
> and none of them are tracked in bugs.python.org. (This is also the case
> for the website.) I'd really like bugs.python.org to remain a tracker for
> what we s
Am 26.07.2010 23:03, schrieb Tarek Ziadé:
> On Mon, Jul 26, 2010 at 10:39 PM, Georg Brandl wrote:
>
>>> I think we need to improve this: it can be a very frustrating
>>> experience to contribute to PyPI.
>>
>> I did not experience it this way. On the contrary, I tried to run
>> PyPI locally
On Mon, Jul 26, 2010 at 10:39 PM, Georg Brandl wrote:
...
>> I think we need to improve this: it can be a very frustrating
>> experience to contribute to PyPI.
>
> I did not experience it this way. On the contrary, I tried to run
> PyPI locally for testing purposes, but didn't want to compile and
Am 26.07.2010 13:02, schrieb Tarek Ziadé:
> On Sat, Jul 24, 2010 at 4:08 PM, Guido van Rossum wrote:
> [...]
>> - A lot of things seem to be happening to make PyPI better. Is this
>> being summarized somewhere? Based on some questions I received during
>> my keynote Q&A (http://bit.ly/bdflqa) I th
FWIW, a leading magazine (IEEE Spectrum) this week has an interesting
opinion piece about multicore.
http://spectrum.ieee.org/computing/software/the-trouble-with-multicore
--
--Guido van Rossum (python.org/~guido)
___
Python-Dev mailing list
Python-Dev
On Jul 26, 2010, at 10:50 AM, Ian Bicking wrote:
>On Mon, Jul 26, 2010 at 9:06 AM, Barry Warsaw wrote:
>
>> On Jul 24, 2010, at 07:08 AM, Guido van Rossum wrote:
>> >privileges enough. So, my recommendation (which surely is a
>> >turn-around of my *own* attitude in the past) is to give out more
>
On 7/26/2010 2:40 AM, Peter Portante wrote:
Yet, shouldn't we be able to write a simple embarrassingly parallel
multithreaded algorithm in python (no C-extensions) and have its execution
use all the cores on a system using CPython?
Abstractly, yes, and I believe you can do that now with some
On Mon, Jul 26, 2010 at 9:06 AM, Barry Warsaw wrote:
> On Jul 24, 2010, at 07:08 AM, Guido van Rossum wrote:
> >privileges enough. So, my recommendation (which surely is a
> >turn-around of my *own* attitude in the past) is to give out more
> >commit privileges sooner.
>
> +1, though I'll observe
> According to CSP advicates, this approach will break down when you
> need more than 8-16 cores since cache coherence breaks down at 16
> cores. Then you would have to figure out a message-passing approach
> (but the messages would have to be very fast).
It does break down, and probably always w
On Tue, 27 Jul 2010 12:36:37 am Stefan Behnel wrote:
> geremy condra, 26.07.2010 16:29:
> > I've noticed that I don't have a lot of success in shifting this
> > kind of debate, so I'm not sure it's a good idea to publicly
> > discuss vulnerabilities in something that may wind up being
> > implement
On Mon, Jul 26, 2010 at 7:36 AM, Stefan Behnel wrote:
> geremy condra, 26.07.2010 16:29:
>>
>> I've noticed that I don't have a lot of success in shifting this kind
>> of debate, so I'm not sure it's a good idea to publicly discuss
>> vulnerabilities in something that may wind up being implemented
On Mon, Jul 26, 2010 at 7:36 AM, Stefan Behnel wrote:
> geremy condra, 26.07.2010 16:29:
>>
>> I've noticed that I don't have a lot of success in shifting this kind
>> of debate, so I'm not sure it's a good idea to publicly discuss
>> vulnerabilities in something that may wind up being implemented
On Mon, Jul 26, 2010 at 4:29 PM, geremy condra wrote:
...
> I've noticed that I don't have a lot of success in shifting this kind
> of debate, so I'm not sure it's a good idea to publicly discuss
> vulnerabilities in something that may wind up being implemented as-is,
> but it's up to you guys.
I
geremy condra, 26.07.2010 16:29:
I've noticed that I don't have a lot of success in shifting this kind
of debate, so I'm not sure it's a good idea to publicly discuss
vulnerabilities in something that may wind up being implemented as-is,
but it's up to you guys.
Hmm, security by obscurity? That
On Mon, Jul 26, 2010 at 3:00 AM, Michael Foord
wrote:
> At Resolver Systems we created a "calculation system" that does large
> calculations on background threads using IronPython. Doing them on a
> background thread allows the ui to remain responsive. Several calculations
> could run simultaneous
On 26 Jul, 2010,at 12:00 PM, Michael Foord wrote:On 26/07/2010 04:42, Guido van Rossum wrote:
> On Sun, Jul 25, 2010 at 8:31 PM, Peter Portante
> wrote:
>
>> FWIW: We use Python at Tabblo, straddled across Python 2.5.4 and 2.6.5. They
>> work. And they work well. But we make light use of thr
On Mon, Jul 26, 2010 at 7:21 AM, Tarek Ziadé wrote:
> On Mon, Jul 26, 2010 at 2:10 PM, geremy condra wrote:
>> On Mon, Jul 26, 2010 at 4:52 AM, Tarek Ziadé wrote:
>>> On Mon, Jul 26, 2010 at 1:20 PM, geremy condra wrote:
On Mon, Jul 26, 2010 at 4:02 AM, Tarek Ziadé wrote:
> On Sat, Ju
On Mon, Jul 26, 2010 at 2:10 PM, geremy condra wrote:
> On Mon, Jul 26, 2010 at 4:52 AM, Tarek Ziadé wrote:
>> On Mon, Jul 26, 2010 at 1:20 PM, geremy condra wrote:
>>> On Mon, Jul 26, 2010 at 4:02 AM, Tarek Ziadé wrote:
On Sat, Jul 24, 2010 at 4:08 PM, Guido van Rossum wrote:
>>>
>>>
>>
On Jul 24, 2010, at 07:08 AM, Guido van Rossum wrote:
>privileges enough. So, my recommendation (which surely is a
>turn-around of my *own* attitude in the past) is to give out more
>commit privileges sooner.
+1, though I'll observe that IME, actual commit privileges become much less of
a special
On Mon, Jul 26, 2010 at 4:52 AM, Tarek Ziadé wrote:
> On Mon, Jul 26, 2010 at 1:20 PM, geremy condra wrote:
>> On Mon, Jul 26, 2010 at 4:02 AM, Tarek Ziadé wrote:
>>> On Sat, Jul 24, 2010 at 4:08 PM, Guido van Rossum wrote:
>>
>>
>>
Mirroring apparently also
requires some client chan
On Mon, Jul 26, 2010 at 1:20 PM, geremy condra wrote:
> On Mon, Jul 26, 2010 at 4:02 AM, Tarek Ziadé wrote:
>> On Sat, Jul 24, 2010 at 4:08 PM, Guido van Rossum wrote:
>
>
>
>>> Mirroring apparently also
>>> requires some client changes.
>>
>> Mirrors can be used as long as you manually point a
On Mon, Jul 26, 2010 at 4:02 AM, Tarek Ziadé wrote:
> On Sat, Jul 24, 2010 at 4:08 PM, Guido van Rossum wrote:
>> Mirroring apparently also
>> requires some client changes.
>
> Mirrors can be used as long as you manually point a mirror when using
> them. We we are working on making the
> switc
On Sat, Jul 24, 2010 at 4:08 PM, Guido van Rossum wrote:
[...]
> - A lot of things seem to be happening to make PyPI better. Is this
> being summarized somewhere? Based on some questions I received during
> my keynote Q&A (http://bit.ly/bdflqa) I think not enough people are
> aware of what we are
On Mon, Jul 26, 2010 at 12:02 PM, Michael Foord
wrote:
> On 26/07/2010 04:42, Guido van Rossum wrote:
>>
>> On Sun, Jul 25, 2010 at 8:31 PM, Peter Portante
>> wrote:
>>
>>>
>>> FWIW: We use Python at Tabblo, straddled across Python 2.5.4 and 2.6.5.
>>> They
>>> work. And they work well. But we m
Guido van Rossum wrote:
> While the EuroPython sprints are still going on, I am back home, and
> after a somewhat restful night of sleep, I have some thoughts I'd like
> to share before I get distracted. Note, I am jumping wildly between
> topics.
>
> - Commit privileges: Maybe we've been too caref
On 26/07/2010 04:42, Guido van Rossum wrote:
On Sun, Jul 25, 2010 at 8:31 PM, Peter Portante
wrote:
FWIW: We use Python at Tabblo, straddled across Python 2.5.4 and 2.6.5. They
work. And they work well. But we make light use of threads (mostly
background I/O handling), and heavy use of mul
On 26/07/2010 04:42, Guido van Rossum wrote:
On Sun, Jul 25, 2010 at 8:31 PM, Peter Portante
wrote:
FWIW: We use Python at Tabblo, straddled across Python 2.5.4 and 2.6.5. They
work. And they work well. But we make light use of threads (mostly
background I/O handling), and heavy use of mul
On 7/25/10 11:42 PM, "Guido van Rossum" wrote:
> On Sun, Jul 25, 2010 at 8:31 PM, Peter Portante
> wrote:
>> FWIW: We use Python at Tabblo, straddled across Python 2.5.4 and 2.6.5. They
>> work. And they work well. But we make light use of threads (mostly
>> background I/O handling), and heavy u
On Sun, Jul 25, 2010 at 8:31 PM, Peter Portante
wrote:
> FWIW: We use Python at Tabblo, straddled across Python 2.5.4 and 2.6.5. They
> work. And they work well. But we make light use of threads (mostly
> background I/O handling), and heavy use of multiple processes because we
> can't take advanta
On 7/25/10 3:19 PM, "Gregory P. Smith" wrote:
>
> On Sat, Jul 24, 2010 at 7:08 AM, Guido van Rossum wrote:
>>
>> - Commit privileges: Maybe we've been too careful with only giving
>> commit privileges to to experienced and trusted new developers. I
>> spoke to Ezio Melotti and from his experie
On Sun, Jul 25, 2010 at 2:26 PM, Jesse Noller wrote:
> On Sat, Jul 24, 2010 at 10:08 AM, Guido van Rossum wrote:
>> - After seeing Raymond's talk about monocle (search for it on PyPI) I
>> am getting excited again about PEP 380 (yield from, return values from
>> generators). Having read the PEP o
On Sat, Jul 24, 2010 at 7:08 AM, Guido van Rossum wrote:
>
>
> - Commit privileges: Maybe we've been too careful with only giving
> commit privileges to to experienced and trusted new developers. I
> spoke to Ezio Melotti and from his experience with getting commit
> privileges, it seems to be a c
On Sat, Jul 24, 2010 at 10:08 AM, Guido van Rossum wrote:
> While the EuroPython sprints are still going on, I am back home, and
> after a somewhat restful night of sleep, I have some thoughts I'd like
> to share before I get distracted. Note, I am jumping wildly between
> topics.
>
> - Commit pri
At 04:29 PM 7/25/2010 +1000, Nick Coghlan wrote:
So, while I can understand Guido's temptation (PEP 380 *is* pretty
cool), I'm among those that hope he resists that temptation. Letting
these various ideas bake a little longer without syntactic support
likely won't hurt either.
Well, if somebody
Am 25.07.2010 08:54, schrieb Stefan Behnel:
> Nick Coghlan, 25.07.2010 08:29:
>> We knew PEP 380 would be hurt by the moratorium when the moratorium
>> PEP went through.
>>
>> The goals of the moratorium itself, in making it possible to have a
>> 3.2 release that is fully supported by all of the ma
Nick Coghlan, 25.07.2010 08:29:
We knew PEP 380 would be hurt by the moratorium when the moratorium
PEP went through.
The goals of the moratorium itself, in making it possible to have a
3.2 release that is fully supported by all of the major Python
implementations, still apply, and I believe mak
On Sun, Jul 25, 2010 at 2:16 PM, Steven D'Aprano wrote:
> On Sun, 25 Jul 2010 10:04:57 am Steve Holden wrote:
>> > - After seeing Raymond's talk about monocle (search for it on PyPI)
>> > I am getting excited again about PEP 380 (yield from, return values
>> > from generators). Having read the PEP
On Sat, Jul 24, 2010 at 9:16 PM, Steven D'Aprano wrote:
> On Sun, 25 Jul 2010 10:04:57 am Steve Holden wrote:
>> > - After seeing Raymond's talk about monocle (search for it on PyPI)
>> > I am getting excited again about PEP 380 (yield from, return values
>> > from generators). Having read the PEP
On Sun, 25 Jul 2010 10:04:57 am Steve Holden wrote:
> > - After seeing Raymond's talk about monocle (search for it on PyPI)
> > I am getting excited again about PEP 380 (yield from, return values
> > from generators). Having read the PEP on the plane back home I
> > didn't see anything wrong with i
On 7/24/2010 3:08 PM, Guido van Rossum wrote:
> While the EuroPython sprints are still going on, I am back home, and
> after a somewhat restful night of sleep, I have some thoughts I'd like
> to share before I get distracted. Note, I am jumping wildly between
> topics.
>
> - Commit privileges: May
On Sat, Jul 24, 2010 at 2:05 PM, Terry Reedy wrote:
> On 7/24/2010 10:08 AM, Guido van Rossum wrote:
>
>> - Commit privileges: Maybe we've been too careful with only giving
>> commit privileges to to experienced and trusted new developers. I
>> spoke to Ezio Melotti and from his experience with ge
On 7/24/2010 10:08 AM, Guido van Rossum wrote:
- Commit privileges: Maybe we've been too careful with only giving
commit privileges to to experienced and trusted new developers. I
spoke to Ezio Melotti and from his experience with getting commit
privileges, it seems to be a case of "the lion is
While the EuroPython sprints are still going on, I am back home, and
after a somewhat restful night of sleep, I have some thoughts I'd like
to share before I get distracted. Note, I am jumping wildly between
topics.
- Commit privileges: Maybe we've been too careful with only giving
commit privileg
63 matches
Mail list logo
