Raymond Hettinger wrote:
> I think this would harm more than it would help. It more confusing to
> have several rounding-thingies to choose from than it is have an
> explicit two-step.
But is it more confusing enough to be worth forcing
everyone to pay two function calls instead of one
in the
Martin,
Thanks for the reply.
> I notice that my message comes across pretty negative.
No worries. I'm a volunteer too. :)
> It's a new feature, so it can't possibly get into Python 2.5. That means
> that no action is likely taken before October. It might take years until
> the patch gets con
Chad Whitacre schrieb:
[I notice that my message comes across pretty negative. In a single
sentence: We are all volunteers with limited time, and we contribute
to Python because its fun and because it helps us solve our own
problems.]
> Last week I submitted a patch (my first), and now I'm wond
Skip,
> It's worth noting that a number of people will look at a patch after the
> submitter has reviewed five other patches or bug reports
Also helpful, thanks!
chad
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/li
Brett,
> "We" is most of the developers on python-dev. There is a Python patches
> mailing list that most developers subscribe to.
Helpful, thanks.
> The latter unfortunatley. Since this all relies on people's volunteer
> efforts the patch usually has to matter to someone to lead to them putt
Chad> And is every patch eventually responded to? Or do some simply fall
Chad> by the wayside?
Brett> The latter unfortunatley. Since this all relies on people's
Brett> volunteer efforts the patch usually has to matter to someone to
Brett> lead to them putting the time and ef
On 7/31/06, Chad Whitacre <[EMAIL PROTECTED]> wrote:
Brett,Thanks for the helpful reply.> Let it sit for now. We get email notifications when new patches come in.Can I ask who "we" are? Is that the seven SF "Project Admins?" Is that
the 68 SF "Developers?""We" is most of the developers on python-d
Brett,
Thanks for the helpful reply.
> Let it sit for now. We get email notifications when new patches come in.
Can I ask who "we" are? Is that the seven SF "Project Admins?" Is that
the 68 SF "Developers?"
And is every patch eventually responded to? Or do some simply fall by
the wayside?
On 7/31/06, Chad Whitacre <[EMAIL PROTECTED]> wrote:
Dear All,Last week I submitted a patch (my first),Thanks!
and now I'm wondering what myexpectations should be. Do I sit around and wait? How long? Do I notifythis list? Do I notify a specific person, say, an author or reviewer ofthe original co
Dear All,
Last week I submitted a patch (my first), and now I'm wondering what my
expectations should be. Do I sit around and wait? How long? Do I notify
this list? Do I notify a specific person, say, an author or reviewer of
the original code I modified? Do I use SF's assignment mechanism? Who
Greg Ewing wrote:
>As an aside, does anyone else think that it would be
>useful to have a builtin which rounds and converts to
>an int in one go? Whenever I use round(), I almost
>always want the result as an int, and making me do
>it in two steps seems unnecessarily bothersome.
>
>
I think this
[me, on 25 July]
> I have
> discovered other hypothetical cases of bad chunking that cause httplib
> to go into an infinite loop or block forever on socket.readline().
> Should we worry about those cases as well, despite not having seen them
> happen in the wild? More annoying, I can reproduce the
12 matches
Mail list logo
