Hello,
I'd like to propose formally marking os.system() as deprecated in the
docs for next release of Python (v3.2 ?).
The docs for os.system() /already/ include the following paragraph,
which is basically tantamount to calling system() deprecated and very
much resembles the deprecation notes for
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 7:20 PM, Alexander Belopolsky
wrote:
> On Sun, Jul 25, 2010 at 9:46 PM, Guido van Rossum wrote:
> ..
>>> Maybe self.__format__(..).encode('ascii')? ...encode('utf-8') is a
>>> tempting alternative as well.
>>
>> -1
>>
>> That would bring back the "it fails for some users
On Sun, Jul 25, 2010 at 9:46 PM, Guido van Rossum wrote:
..
>> Maybe self.__format__(..).encode('ascii')? ...encode('utf-8') is a
>> tempting alternative as well.
>
> -1
>
> That would bring back the "it fails for some users but passes for the
> developer" problem. (True, if the developer calls .
On Sun, Jul 25, 2010 at 9:46 PM, Guido van Rossum wrote:
..
> If I had to choose I'd never show the microseconds.
Or the timezone offset, right?
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubsc
On Sun, Jul 25, 2010 at 11:53 AM, Raymond Hettinger
wrote:
> On Jul 25, 2010, at 11:38 AM, Michael Foord wrote:
>> Antonio Cuni demoed some *great* improvements to the pdb module at
>> EuroPython. A project called pdb++
>>
>> http://codespeak.net/svn/user/antocuni/hack/pdb.py
>>
>> Among its impr
On Sun, Jul 25, 2010 at 10:41 AM, Alexander Belopolsky
wrote:
> On Sun, Jul 25, 2010 at 1:13 PM, Eric Smith wrote:
>> On 7/23/10 2:44 AM, Guido van Rossum wrote:
>>>
>>> Indeed, we meant b'...{}...{}...'.format(x, y). The problem is that it
>>> can't invoke x.__format__() or y.__format__() since
Am 26.07.2010 02:24, schrieb Terry Reedy:
> To review a patch on the tracker, I have to read and try to make sense
> of the raw diff file. Sometimes that is easy, sometimes not.
>
> *After* a patch is applied, I can click the rev link and then the
> 'text changed' link and see a nice, colored,
To review a patch on the tracker, I have to read and try to make sense
of the raw diff file. Sometimes that is easy, sometimes not.
*After* a patch is applied, I can click the rev link and then the
'text changed' link and see a nice, colored, side-by-side web-pace view
created by ViewVC. I
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
P.J. Eby wrote:
I would like to reiterate (no pun intended) the suggestion of a special
syntactic form for the return
Allowing a return
value, but then having that value silently disappear, seems like it
would delay ... learning
If I remember correctly, all these arguments were made at th
On 7/24/2010 11:21 PM, Guido van Rossum wrote:
On Sat, Jul 24, 2010 at 6:51 PM, P.J. Eby wrote:
By the way, the PEP's "optimized" implementation could probably be done just
by making generator functions containing yield-from statements return an
object of a different type than the standard ge
On 7/25/2010 2:58 PM, Leonhard Vogt wrote:
I have made a documentation patch for issue 7447.
I cannot change the stage to patch-review - is this intentional?
Would be great if someone could comment on the patch.
Done x 3
--
Terry Jan Reedy
___
Pyth
On Sun, Jul 25, 2010 at 5:57 PM, Nick Coghlan wrote:
..
> While the general preference is to backport tests, it is also
> acknowledged that that can become overly difficult as the test cases
> diverge. Up to you if you want to manually fix your patch for 3.1,
> drop the test_profilehooks changes,
On Mon, Jul 26, 2010 at 1:50 AM, Alexander Belopolsky
wrote:
> On Sat, Jul 24, 2010 at 11:18 PM, Nick Coghlan wrote:
>> On Sun, Jul 25, 2010 at 2:20 AM, Alexander Belopolsky
>> wrote:
> ..
>>> Step 1: Rename test_trace to test_sys_settrace and test_profilehooks
>>> to test_sys_setprofile.
> ..
>
> Interested, yes. But until either a) I can commit patches, or b) there
> is someone who will respond to commit review recommendations with "No,
> here is why not" or "Yes, committed", I will work on other issues, such
> as doc issues, for which I can get responses.
If you are then still interest
>> There's no reason why Tal should be obstructed in his goal of making
>> IDLE at least acceptable again. It's fairly obvious thaat there aren't
>> any committers who have both the inclination /and/ the time to do this,
>> so adding Tal (and other interested parties) as a developer makes a lot
>>
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
Hi
I have made a documentation patch for issue 7447.
I cannot change the stage to patch-review - is this intentional?
Would be great if someone could comment on the patch.
Leonhard
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.
On Jul 25, 2010, at 11:38 AM, Michael Foord wrote:
> On 25/07/2010 19:34, Alexander Belopolsky wrote:
>> [snip...]
>>> On the other hand, posting actual patches that fix actual bugs can
>>> make a lot of a difference. Also, having a maintainer who is willing
>>> to look into these patches and acc
On 25/07/2010 19:34, Alexander Belopolsky wrote:
[snip...]
On the other hand, posting actual patches that fix actual bugs can
make a lot of a difference. Also, having a maintainer who is willing
to look into these patches and accept the good ones will make a lot
of a difference.
With resp
On Sun, Jul 25, 2010 at 1:22 PM, "Martin v. Löwis" wrote:
..
> It is at best entertaining to ponder about reasons here; I doubt
> anything productive can come out of such a discussion.
>
I disagree. Depending on the reasons for the relative lack of
attention to these components, several alternat
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
So OK, thank you for response.
No, I wasn't joking. I'm sorry, I didn't know that you Python guys get offended
from being compared to PHP or Perl. Perhaps that shouldn't surprise me, though.
I have posted all of this here, because I was hoping this feature would be
implemented secretly, with
On Sun, Jul 25, 2010 at 1:13 PM, Eric Smith wrote:
> On 7/23/10 2:44 AM, Guido van Rossum wrote:
>>
>> Indeed, we meant b'...{}...{}...'.format(x, y). The problem is that it
>> can't invoke x.__format__() or y.__format__() since those will return
>> text strings instead of bytes. A proposed soluti
On Fri, Jul 23, 2010 at 2:44 AM, Guido van Rossum wrote:
..
> Indeed, we meant b'...{}...{}...'.format(x, y). The problem is that it
> can't invoke x.__format__() or y.__format__() since those will return
> text strings instead of bytes. A proposed solution was to try
> x.__bformat__() etc. Anothe
> Oh, and with business philosophy I mean: mails like the one you start
> this thread with are interpreted by me as being very pushy, overly
> sarcastic and if my project manager at the office sends me an email
> like that I know I have to do it right now. I would dislike to be
> spoken to like thi
> Part of me agrees with you regarding the generally different tool
> lifecycle, but another part says we need these tools in the standard
> library or we risk inadvertently breaking the hooks they would still
> rely on, even as third party projects.
>
> I suspect a major factor here relates to th
On 7/23/10 2:44 AM, Guido van Rossum wrote:
Indeed, we meant b'...{}...{}...'.format(x, y). The problem is that it
can't invoke x.__format__() or y.__format__() since those will return
text strings instead of bytes. A proposed solution was to try
x.__bformat__() etc. Another proposed solution was
On Sun, Jul 25, 2010 at 12:32 PM, Ron Adam wrote:
..
>> I'd be completely fine with dropping the "Search For" box from the GUI
>> interface, but the persistent window listing the served port and
>> providing "Open Browser" and "Quit Serving" buttons still seems quite
>> useful even without the sea
On 07/24/2010 10:38 PM, Nick Coghlan wrote:
On Sun, Jul 25, 2010 at 5:34 AM, Ron Adam wrote:
On 07/24/2010 05:37 AM, Nick Coghlan wrote:
On Sat, Jul 24, 2010 at 10:05 AM, Ron Adamwrote:
I am not sure I like the fact that the browser is started automatically.
Please bring this up on
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
On Sat, Jul 24, 2010 at 11:18 PM, Nick Coghlan wrote:
> On Sun, Jul 25, 2010 at 2:20 AM, Alexander Belopolsky
> wrote:
..
>> Step 1: Rename test_trace to test_sys_settrace and test_profilehooks
>> to test_sys_setprofile.
..
> A tracetester helper module + the two test module renames sounds like
>
On Sat, Jul 24, 2010 at 8:29 PM, Nick Coghlan wrote:
> On Sun, Jul 25, 2010 at 3:30 AM, Guido van Rossum wrote:
>> On Fri, Jul 23, 2010 at 4:20 PM, Alexander Belopolsky
>> wrote:
>>> There must be a good reason why traditional software development tools
>>> such as debugger, profiler and coverag
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
37 matches
Mail list logo
