Re: [Python-Dev] [RFC] PEP 418: Add monotonic time, performance counter and process time functions

On Fri, Apr 27, 2012 at 5:50 PM, Steven D'Aprano wrote: > Some issues with the PEP 418: > > > 1) time.clock is deprecated, but also supported by get_clock_info. Why > bother supporting it if you don't want people to use it? I see the deprecation of clock() as mostly symbolic -- it's used way too

Re: [Python-Dev] [RFC] PEP 418: Add monotonic time, performance counter and process time functions

> 1) time.clock is deprecated, but also supported by get_clock_info. Why > bother supporting it if you don't want people to use it? It will not be removed before Python 4, the function is still used by Python < 3.3. > 2) get_clock_info returns a dict. Why not a namedtuple? I don't like the tuple

Re: [Python-Dev] [RFC] PEP 418: Add monotonic time, performance counter and process time functions

Some issues with the PEP 418: 1) time.clock is deprecated, but also supported by get_clock_info. Why bother supporting it if you don't want people to use it? 2) get_clock_info returns a dict. Why not a namedtuple? 3) The dict returned by get_clock_info includes an optional key, "is_adjust

Re: [Python-Dev] Changes in html.parser may cause breakage in client code

Awesome! On Fri, Apr 27, 2012 at 3:07 PM, Carl Meyer wrote: > On 04/27/2012 08:36 AM, Guido van Rossum wrote: >> >> Someone should contact the Django folks. Alex Gaynor? > > > I committed the relevant code to Django (though I didn't write the patch), > and I've been following this thread. I have

Re: [Python-Dev] Changes in html.parser may cause breakage in client code

On 04/27/2012 08:36 AM, Guido van Rossum wrote: Someone should contact the Django folks. Alex Gaynor? I committed the relevant code to Django (though I didn't write the patch), and I've been following this thread. I have it on my todo list to review this code again with Ezio's suggestions in

Re: [Python-Dev] [RFC] PEP 418: Add monotonic time, performance counter and process time functions

Hi Victor, I read most of the PEP and I think it is ready for acceptance! Thanks for your patience in shepherding this through such a difficult and long discussion. Also thanks to the many other contributors, especially those who ended up as co-authors. We will have an awesome new set of time APIs

Re: [Python-Dev] package imports, sys.path and os.chdir()

On 27.04.12 22:00, Brett Cannon wrote: On Fri, Apr 27, 2012 at 10:39, Christian Tismer > wrote: On 27.04.12 02:39, Nick Coghlan wrote: On Fri, Apr 27, 2012 at 7:30 AM, Christian Tismermailto:tis...@stackless.com>> wrote: No big d

Re: [Python-Dev] package imports, sys.path and os.chdir()

On 4/27/2012 1:00 PM, Brett Cannon wrote: I'm personally in favour of changing the insertion of '' to sys.path to inserting the cwd when the interpreter is launched. +1 ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/li

Re: [Python-Dev] sys.implementation

On 4/27/2012 11:49 AM, R. David Murray wrote: On Fri, 27 Apr 2012 10:40:43 -0700, Glenn Linderman wrote: On 4/27/2012 12:34 AM, Eric Snow wrote: On Thu, Apr 26, 2012 at 8:31 AM, Barry Warsaw wrote: It's somewhat of a corner case, but I think a PEP couldn't hurt. The rationale section woul

Re: [Python-Dev] package imports, sys.path and os.chdir()

On Fri, Apr 27, 2012 at 10:39, Christian Tismer wrote: > On 27.04.12 02:39, Nick Coghlan wrote: > >> On Fri, Apr 27, 2012 at 7:30 AM, Christian Tismer >> wrote: >> >>> No big deal and easy to work around, I just would like to understand why. >>> >> I don't like it either and want to change it, bu

Re: [Python-Dev] sys.implementation

On Fri, 27 Apr 2012 10:40:43 -0700, Glenn Linderman wrote: > On 4/27/2012 12:34 AM, Eric Snow wrote: > > On Thu, Apr 26, 2012 at 8:31 AM, Barry Warsaw wrote: > >> It's somewhat of a corner case, but I think a PEP couldn't hurt. The > >> rationale section would be useful, at least. > >http:/

Re: [Python-Dev] sys.implementation

On 4/27/2012 12:34 AM, Eric Snow wrote: On Thu, Apr 26, 2012 at 8:31 AM, Barry Warsaw wrote: It's somewhat of a corner case, but I think a PEP couldn't hurt. The rationale section would be useful, at least. http://mail.python.org/pipermail/python-ideas/2012-April/014954.html The idea of

Re: [Python-Dev] Changes in html.parser may cause breakage in client code

On 4/27/2012 1:23 AM, Ezio Melotti wrote: html.parser doesn't use any private _name, so I was considering part of the public API only the documented names. Several methods are marked with an "# internal" comment, but that's not visible unless you go read the source code. I could not find __all

[Python-Dev] Summary of Python tracker Issues

ACTIVITY SUMMARY (2012-04-20 - 2012-04-27) Python tracker at http://bugs.python.org/ To view or respond to any of the issues listed below, click on the issue. Do NOT respond to this message. Issues counts and deltas: open3405 ( +9) closed 23056 (+41) total 26461 (+50) Open issues wit

Re: [Python-Dev] package imports, sys.path and os.chdir()

On 27.04.12 02:39, Nick Coghlan wrote: On Fri, Apr 27, 2012 at 7:30 AM, Christian Tismer wrote: No big deal and easy to work around, I just would like to understand why. I don't like it either and want to change it, but I'm also not going to mess with it until the importlib bootstrapping is fu

Re: [Python-Dev] Changes in html.parser may cause breakage in client code

Someone should contact the Django folks. Alex Gaynor? On Thursday, April 26, 2012, Ezio Melotti wrote: > Hi, > > On 26/04/2012 22.10, Vinay Sajip wrote: > >> Following recent changes in html.parser, the Python 3 port of Django I'm >> working >> on has started failing while parsing HTML. >> >> The

Re: [Python-Dev] sys.implementation

On Thu, Apr 26, 2012 at 8:31 AM, Barry Warsaw wrote: > It's somewhat of a corner case, but I think a PEP couldn't hurt.  The > rationale section would be useful, at least. http://mail.python.org/pipermail/python-ideas/2012-April/014954.html -eric ___