Ben Finney wrote:
Terry Reedy writes:
I watched and was greatly impressed by the video demo of Google's new
Wave collaborative communication system. I believe it would/will help
with some of the chronic problems we (and others) have.
Example: if PEPs were waves, then responses could either b
On 3 Jun, 07:08 pm, mar...@v.loewis.de wrote:
To go back to JP's original comments though: what was the right thing
for him to do, back in January, when he had these concerns?
To me, it's fairly clear: what the committer needs to get is guidance
in
any action to take. In most cases, the set
On Thu, 4 Jun 2009 at 12:23, Greg Ewing wrote:
Michael Foord wrote:
if you are added as nosy on a tracker item (which happens when you make a
comment or you can do yourself) then you get emailed about new comments.
That's good, but...
only going to the tracker to add responses.
is not
Antoine Pitrou writes:
> Terry Reedy udel.edu> writes:
> >
> > I watched and was greatly impressed by the video demo of Google's new
> > Wave collaborative communication system. I believe it would/will help
> > with some of the chronic problems we (and others) have.
>
> I really don't
Michael Foord wrote:
if you are added as nosy on a tracker item (which happens
when you make a comment or you can do yourself) then you get emailed
about new comments.
That's good, but...
only going to the tracker to add responses.
is not so good. If the goal is to ensure that all previou
Ben Finney wrote:
> Terry Reedy writes:
>
> > I watched and was greatly impressed by the video demo of Google's new
> > Wave collaborative communication system. I believe it would/will help
> > with some of the chronic problems we (and others) have.
>
> I watched that too. It appears to be hea
Terry Reedy writes:
> I watched and was greatly impressed by the video demo of Google's new
> Wave collaborative communication system. I believe it would/will help
> with some of the chronic problems we (and others) have.
I watched that too. It appears to be heavily reliant on *very* fast
intern
On Wed, Jun 3, 2009 at 2:58 PM, Raymond Hettinger wrote:
> [GvR]
Benjamin, what would be involved in removing it? I suppose there's the
module itself, some unit tests, and some docs. (I'm not asking you to
remove it yet -- but I'm asking to look into the consequences, so that
>
[GvR]
Benjamin, what would be involved in removing it? I suppose there's the
module itself, some unit tests, and some docs. (I'm not asking you to
remove it yet -- but I'm asking to look into the consequences, so that
we can be sure to do the right thing before releasing 3.1 final.)
[Benjamin P
Benjamin Peterson schrieb:
> 2009/6/2 Guido van Rossum :
>> Benjamin, what would be involved in removing it? I suppose there's the
>> module itself, some unit tests, and some docs. (I'm not asking you to
>> remove it yet -- but I'm asking to look into the consequences, so that
>> we can be sure to
Terry Reedy udel.edu> writes:
>
> I watched and was greatly impressed by the video demo of Google's new
> Wave collaborative communication system. I believe it would/will help
> with some of the chronic problems we (and others) have.
I really don't think technical systems are an answer to soc
gl...@divmod.com wrote:
So, here are my recommendations:
1. Use the tracker for discussing tickets, so that it's easy to refer
back to a previous point in the discussion, and so that people working
on those tickets can easily find your commentary.
2. Use the mailing list for drawing attenti
> Not true - if you are added as nosy on a tracker item (which happens
> when you make a comment or you can do yourself) then you get emailed
> about new comments. The email contains the body of the comment so you
> can follow discussions completely by email only going to the tracker to
> add respo
On Wed, Jun 3, 2009 at 2:56 PM, Michael Foord wrote:
> Paul Moore wrote:
>>
>> 2009/6/3 :
>>
>>>
>>> So, here are my recommendations:
>>>
>>> 1. Use the tracker for discussing tickets, so that it's easy to refer
>>> back
>>> to a previous point in the discussion, and so that people working on
>>
> The thing that stands out about the earlier tracker/mailing list
> discussions is how very few people affirmatively wanted ipaddr added
> to the standard library. Most people thought it sounded ok in
> principle, didn't care, or thought it was not a great idea but didn't
> feel like arguing abou
> To go back to JP's original comments though: what was the right thing
> for him to do, back in January, when he had these concerns? Should he
> have said "I am therefore -1 on this inclusion"? Should he have been
> discussing this on the mailing list rather than the tracker? Should he
> have k
Paul Moore wrote:
2009/6/3 :
So, here are my recommendations:
1. Use the tracker for discussing tickets, so that it's easy to refer back
to a previous point in the discussion, and so that people working on those
tickets can easily find your commentary.
2. Use the mailing list for drawing
In article
<20090603181236.12555.1355794514.divmod.xquotient.12...@weber.divmod.com
>gl...@divmod.com wrote:
> If you want to get email about new issues, subscribe to new-bugs-
> annou...@mail.python.org. If you want to know about every message on
> every issue, subscribe to python-bugs-l...@ma
On Wed, Jun 3, 2009 at 10:41 AM, wrote:
>
> On 02:39 am, gu...@python.org wrote:
>>
>> I'm disappointed in the process -- it's as if nobody really reviewed
>> the API until it was released with rc1, and this despite there being a
>> significant discussion about its inclusion and alternatives mont
On Wed, Jun 3, 2009 at 11:16 AM, R. David Murray wrote:
> I think this hits the nail on the head. Rather than network engineers
> having a less precise understanding of IP, what we have is two different
> sets of domain requirements. Network engineers deal with networks, with
> IPs being a nece
[GvR]
Whoa. Are you all suddenly trying to turn Python into a democracy?
Arthur: I am your king!
Woman: Well I didn't vote for you!
Arthur: You don't vote for kings.
Woman: Well how'd you become king then?
[Angelic music plays...]
Arthur: The Lady of the Lake, her arm clad in the purest s
On 05:42 pm, p.f.mo...@gmail.com wrote:
2009/6/3 :
So, here are my recommendations:
1. Use the tracker for discussing tickets, so that it's easy to refer
back
to a previous point in the discussion, and so that people working on
those
tickets can easily find your commentary.
2. Use the ma
On 05:19 pm, gu...@python.org wrote:
On Wed, Jun 3, 2009 at 10:13 AM, Neil Schemenauer
wrote:
Barry Warsaw wrote:
It would be really nice if say the Cheeseshop had a voting feature.
Use PEP 10 voting to get a rough estimate of a module's popularity
(download counts alone might not tell you ev
2009/6/3 :
> So, here are my recommendations:
>
> 1. Use the tracker for discussing tickets, so that it's easy to refer back
> to a previous point in the discussion, and so that people working on those
> tickets can easily find your commentary.
> 2. Use the mailing list for drawing attention to
On 07:51 am, p.f.mo...@gmail.com wrote:
2009/6/3 Stephen J. Turnbull :
One thing I would recommend is that while inclusion is not a matter of
voting, people who are recognized as domain experts on Python-Dev
*should* try to add their "+1" or "-1" early. �Especially if they
don't expect to have
On 02:44 am, a...@pythoncraft.com wrote:
On Tue, Jun 02, 2009, Guido van Rossum wrote:
I hope we can learn from this.
I'm not thrilled with adding more process just because we had a problem
here, and the only obvious solution I see is to require a PEP every
time
a module is added. Based on
On 02:39 am, gu...@python.org wrote:
I'm disappointed in the process -- it's as if nobody really reviewed
the API until it was released with rc1, and this despite there being a
significant discussion about its inclusion and alternatives months
ago. (Don't look at me -- I wouldn't recognize a net
On Wed, Jun 3, 2009 at 10:13 AM, Neil Schemenauer wrote:
> Barry Warsaw wrote:
>> It would be really nice if say the Cheeseshop had a voting feature.
>> Use PEP 10 voting to get a rough estimate of a module's popularity
>> (download counts alone might not tell you everything). Then at least
>> y
Barry Warsaw wrote:
> It would be really nice if say the Cheeseshop had a voting feature.
> Use PEP 10 voting to get a rough estimate of a module's popularity
> (download counts alone might not tell you everything). Then at least
> you can get a rough idea of how generally popular a module
R. David Murray wrote:
> Both approaches are valid, but lead to different design decisions.
> I don't see any reason why both needs cannot be met by a common API,
> but I'm wondering if any existing package is going to incorporate both
> approaches satisfactorily. As another poster said, each pa
On Wed, 3 Jun 2009 at 03:42, Mike Pennington wrote:
That said, I test drove ipaddr for about 30 minutes and so far like the
big-picture API design quite a bit. I'll specifically address Clay's concern
about hosts vs networks, because this issue is important to me; I've been in
the network engi
> I've just subscribed to python-dev again after being pointed towards
> this thread (thanks Raymond).
The same for me, thanks. :-)
I'm the author of IPLib [1]; I don't consider myself an expert on the
subject and my code dates back to Python 1.6 times (last updated in 2005).
Moreover, while it wo
Paul Moore wrote:
> Note 1 - by the way, I use this form because I don't understand how
> the /24 notation works. I can get the subnet mask from ipconfig, so I
> use that.
It's just a shorthand way of writing IPv4 net masks based on their
binary form:
/8 = 8 ones followed by 24 zeroes = 255.0.
On Jun 2, 2009, at 10:39 PM, Guido van Rossum wrote:
I hope we can learn from this.
One crazy thought: let's use the Cheeseshop.
When I search for 'ipaddr' I get three hits, with Google's module at
the top with a score of '8'. I really don't know what that means but
I'm guessing it means
On Jun 2, 2009, at 10:43 PM, Gregory P. Smith wrote:
Should it only be removed from py3k branch or also from trunk pending
a decision as to if the library is reworked or if something else
entirely is adopted?
I think it should be removed from trunk if it's removed from the py3k
branch. Noth
Hello,
2009/6/3 Stefan Behnel :
> Hi,
>
> I can't currently file a bug report on this, but I was told by Lisandro
> Dalcín that there is a serious problem with the doctest module in Py3.1rc1.
> In Cython, we use doctests to test the compiler in that we compile a
> Python/Cython module with doctest
Raymond solicited a comment from me about the design of ipaddr. By way
of full disclosure, I have a small competing project called pynet.
That said, I test drove ipaddr for about 30 minutes and so far like the
big-picture API design quite a bit. I'll specifically address Clay's
concern about
2009/6/2 R. David Murray :
> On Tue, 2 Jun 2009 at 21:02, Paul Moore wrote:
>> Simple example. If I want to scan all the IP addresses on my network
>> (my IP address is 192.168.1.101) I'd probably write:
>>
>> for i in range(253):
>> ip = '192.168.1.' + str(i+1)
>> ...
>>
>> - and to
2009/6/3 Stephen J. Turnbull :
> Aahz writes:
>
> > On Tue, Jun 02, 2009, Guido van Rossum wrote:
> > >
> > > I hope we can learn from this.
> >
> > I'm not thrilled with adding more process just because we had a problem
> > here, and the only obvious solution I see is to require a PEP every
Hi,
I can't currently file a bug report on this, but I was told by Lisandro
Dalcín that there is a serious problem with the doctest module in Py3.1rc1.
In Cython, we use doctests to test the compiler in that we compile a
Python/Cython module with doctests into a C module and then run doctest on
th
40 matches
Mail list logo
