Re: [Python-Dev] PEP 418: Add monotonic clock

On Tue, Mar 27, 2012 at 3:51 PM, Jeffrey Yasskin wrote: > FWIW, I'm not sure you're the right person to drive time PEPs. You > don't seem to have come into it with much knowledge of time, and it's > taken several repetitions for you to take corrections into account in > both this discussion and th

Re: [Python-Dev] PEP 418: Add monotonic clock

FWIW, I'm not sure you're the right person to drive time PEPs. You don't seem to have come into it with much knowledge of time, and it's taken several repetitions for you to take corrections into account in both this discussion and the Decimal/datetime representation PEP. On Mon, Mar 26, 2012 at 4

Re: [Python-Dev] Playing with a new theme for the docs, iteration 2

On Mon, Mar 26, 2012 at 6:42 AM, Terry Reedy wrote: >> Of course you can always use a user stylesheet to override our choices. > > Can anyone tell me the best way to do that with FireFox? http://kb.mozillazine.org/UserContent.css explains clearly enough. I can't help you with your particular ve

Re: [Python-Dev] Playing with a new theme for the docs, iteration 2

Hi, Le 25/03/2012 15:25, Georg Brandl a écrit : > On 25.03.2012 21:11, Steven D'Aprano wrote: >> I think it would be better to leave 2.7 with the old theme, >> to keep it visually distinct from the nifty new theme used >> with the nifty new 3.2 and 3.3 versions. > Hmm, -0 here. I'd like more opin

Re: [Python-Dev] PEP 418: Add monotonic clock

Cheers, that clears things up. ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com

Re: [Python-Dev] PEP 411 - request for pronouncement

On Tue, Mar 27, 2012 at 05:34, Guido van Rossum wrote: > On Mon, Mar 26, 2012 at 8:23 PM, Eli Bendersky wrote: >>> I think the PEP is almost ready for approval. Congratulations! A few >>> comments: >>> >>> - I'd leave some wiggle room for the docs owner (Georg) about the >>> exact formulation of

Re: [Python-Dev] PEP 411 - request for pronouncement

> > I've marked it up as Approved. Thanks, and congrats! > Thanks! Eli ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-ar

Re: [Python-Dev] PEP 418: Add monotonic clock

On 3/26/2012 10:59 PM, Matt Joiner wrote: > So does anyone care to dig into the libstd++/boost/windoze > implementation to see how they each did steady_clock? The Boost implementation can be summarized as: system_clock: mac = gettimeofday posix = clock_gettime(CLOCK_REALTIME) win = GetSyst

Re: [Python-Dev] PEP 411 - request for pronouncement

On Mon, Mar 26, 2012 at 8:23 PM, Eli Bendersky wrote: >> I think the PEP is almost ready for approval. Congratulations! A few >> comments: >> >> - I'd leave some wiggle room for the docs owner (Georg) about the >> exact formulation of the text blurb included for provisional modules >> and the glo

Re: [Python-Dev] PEP 411 - request for pronouncement

> I think the PEP is almost ready for approval. Congratulations! A few comments: > > - I'd leave some wiggle room for the docs owner (Georg) about the > exact formulation of the text blurb included for provisional modules > and the glossary entry; I don't want the PEP to have the last word > here.

Re: [Python-Dev] Playing with a new theme for the docs

On Tue, Mar 27, 2012 at 1:35 AM, PJ Eby wrote: > On Sun, Mar 25, 2012 at 2:56 AM, Stephen J. Turnbull > wrote: >> >> But since he's arguing the >> other end in the directory layout thread (where he says there are many >> special ways to invoke Python so that having different layouts on >> differe

Re: [Python-Dev] PEP 418: Add monotonic clock

So does anyone care to dig into the libstd++/boost/windoze implementation to see how they each did steady_clock? ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mail

Re: [Python-Dev] Drop the new time.wallclock() function?

Inside time.steady, there are two different clocks trying to get out. I think this steady business should be removed sooner rather than later. ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscrib

Re: [Python-Dev] Drop the new time.wallclock() function?

On Mon, Mar 26, 2012 at 5:07 PM, Victor Stinner wrote: >> >> If someone has a use case which fits the "steady or else fall back to wall >> clock" pattern, I would like to learn about it. > > Python 3.2 doesn't provide a monotonic clock, so most program uses > time.time() even if a monotonic cloc

Re: [Python-Dev] PEP 418: Add monotonic clock

>  system_clock = wall clock time >  monotonic_clock = always goes forward but can be adjusted >  steady_clock = always goes forward and cannot be adjusted >  high_resolution_clock = steady_clock || system_clock Note that the C++ standard deprecated monotonic_clock once they realized that there is

Re: [Python-Dev] PEP 418: Add monotonic clock

On 3/26/2012 7:32 PM, Victor Stinner wrote: > I started to write the PEP 418 to clarify the notions of monotonic and > steady clocks. """ time.steady This clock advances at a steady rate relative to real time. It may be adjusted. """ Please do not call this "steady". If the clock can be adjusted,

Re: [Python-Dev] PEP 418: Add monotonic clock

> I started to write the PEP 418 to clarify the notions of monotonic and > steady clocks. > > The PEP is a draft and everyone is invited to contribute! time.steady() doesn't fit the benchmarking use case: it looks like we have to decide between stability and clock resolution. QueryPerformanceCoun

[Python-Dev] PEP 418: Add monotonic clock

Hi, I started to write the PEP 418 to clarify the notions of monotonic and steady clocks. The PEP is a draft and everyone is invited to contribute! http://www.python.org/dev/peps/pep-0418/ http://hg.python.org/peps/file/tip/pep-0418.txt Victor ___ Pyt

Re: [Python-Dev] Drop the new time.wallclock() function?

On Mar 26, 2012, at 6:31 PM, Zooko Wilcox-O'Hearn wrote: > On Fri, Mar 23, 2012 at 11:27 AM, Victor Stinner > wrote: >> >> time.steady(strict=False) is what you need to implement timeout. > > No, that doesn't fit my requirements, which are about event > scheduling, profiling, and timeouts. See

Re: [Python-Dev] Drop the new time.wallclock() function?

> So using one kind of clock and then "falling back" to the other kind > is a choice that should be rare, explicit, and discouraged. The > provision of such a function in the standard library is an attractive > nuisance -- a thing that people naturally think that they want when > they haven't thoug

Re: [Python-Dev] [Python-checkins] cpython: Issue #7652: Integrate the decimal floating point libmpdec library to speed

Victor Stinner wrote: > > The 80x is a ballpark figure for the maximum expected speedup for > > standard numerical floating point applications. > > Ok, but it's just surprising when you read the What's New document. > 72x and 80x look to be inconsistent. Yes, indeed, I'll reword that. > > For

Re: [Python-Dev] Drop the new time.wallclock() function?

On Fri, Mar 23, 2012 at 11:27 AM, Victor Stinner wrote: > > time.steady(strict=False) is what you need to implement timeout. No, that doesn't fit my requirements, which are about event scheduling, profiling, and timeouts. See below for more about my requirements. I didn't say this explicitly eno

Re: [Python-Dev] cpython: Fix time.steady(strict=True): don't use CLOCK_REALTIME

On Mon, 26 Mar 2012 22:53:37 +0200 victor.stinner wrote: > http://hg.python.org/cpython/rev/566527ace50b > changeset: 75960:566527ace50b > user:Victor Stinner > date:Mon Mar 26 22:53:14 2012 +0200 > summary: > Fix time.steady(strict=True): don't use CLOCK_REALTIME Victor, cou

Re: [Python-Dev] PEP 393 decode() oddity

25.03.12 23:55, mar...@v.loewis.de написав(ла): The results are fairly stable (±0.1 µsec) from run to run. It looks funny thing. This is not surprising. Thank you. Indeed, it is logical. I looked at the code and do not see how to speed it up. ___

Re: [Python-Dev] PEP 393 decode() oddity

27.03.12 01:04, Serhiy Storchaka написав(ла): 26.03.12 01:28, Victor Stinner написав(ла): loop in cascade of independent loops which fallback onto each other (as you have already done in utf8_scanner). Sorry. Not you. Antoine Pitrou. ___ Python-Dev m

Re: [Python-Dev] PEP 393 decode() oddity

26.03.12 01:28, Victor Stinner написав(ла): Cool, Python 3.3 is *much* faster to decode pure ASCII :-) He even faster on large data. 1000 characters is not enough to completely neutralize the constant costs of the function calls. Python 3.3 is really cool. encoding string

Re: [Python-Dev] PEP 411 - request for pronouncement

On Fri, Mar 23, 2012 at 2:51 AM, Eli Bendersky wrote: > PEP 411 -- Provisional packages in the Python standard library > > Has been updated with all accumulated feedback from list discussions. > Here it is: http://www.python.org/dev/peps/pep-0411/ (the text is also > pasted in the bottom of this e

Re: [Python-Dev] Python install layout and the PATH on win32 (Rationale part 1: Regularizing the layout)

On 3/26/2012 1:21 PM, Glenn Linderman wrote: Hmm. And here's something else that might be missing: integration of the launcher with .py files that are actually ZIP archives... where does it find the #! line? (probably it can't, currently -- I couldn't figure out how to make it do it). Is it po

Re: [Python-Dev] Python install layout and the PATH on win32 (Rationale part 1: Regularizing the layout)

On 3/26/2012 12:27 PM, PJ Eby wrote: On Mon, Mar 26, 2012 at 12:58 PM, Carl Meyer > wrote: No disagreement here. I think virtualenv's sweet spot is as a convenient tool for development environments (used in virtualenvwrapper fashion, where the file struct

Re: [Python-Dev] cpython: Adding unittest.mock documentation

On 26 Mar 2012, at 08:11, Georg Brandl wrote: > On 26.03.2012 00:13, michael.foord wrote: >> http://hg.python.org/cpython/rev/adc1fc2dc872 >> changeset: 75938:adc1fc2dc872 >> user:Michael Foord >> date:Sun Mar 25 23:12:55 2012 +0100 >> summary: >> Adding unittest.mock document

Re: [Python-Dev] Playing with a new theme for the docs, iteration 2

Antoine Pitrou wrote: On Sun, 25 Mar 2012 08:34:44 +0200 Also I think there should be some jquery animation when collapsing/expanding. Please, no. I don't need my technical web pages singing and dancing for me. ;) ~Ethan~ ___ Python-Dev mailing l

Re: [Python-Dev] Playing with a new theme for the docs, iteration 2

Antoine Pitrou wrote: On Mon, 26 Mar 2012 12:25:20 -0700 Ethan Furman wrote: Georg Brandl wrote: On 25.03.2012 21:11, Steven D'Aprano wrote: Georg Brandl wrote: Thanks everyone for the overwhelmingly positive feedback. I've committed the new design to 3.2 and 3.3 for now, and it will be li

Re: [Python-Dev] Python install layout and the PATH on win32 (Rationale part 1: Regularizing the layout)

On Mon, Mar 26, 2012 at 12:58 PM, Carl Meyer wrote: > No disagreement here. I think virtualenv's sweet spot is as a convenient > tool for development environments (used in virtualenvwrapper fashion, > where the file structure of the virtualenv itself is hidden away and you > never see it at all).

Re: [Python-Dev] Playing with a new theme for the docs, iteration 2

On Mon, 26 Mar 2012 12:25:20 -0700 Ethan Furman wrote: > Georg Brandl wrote: > > On 25.03.2012 21:11, Steven D'Aprano wrote: > >> Georg Brandl wrote: > >> > >>> Thanks everyone for the overwhelmingly positive feedback. I've committed > >>> the > >>> new design to 3.2 and 3.3 for now, and it will

Re: [Python-Dev] Playing with a new theme for the docs

On 3/26/2012 10:58 AM, Ethan Furman wrote: Glenn Linderman wrote: On 3/26/2012 10:19 AM, R. David Murray wrote: Like Philip, I have *one* window. My window manager (ratpoison) is more like 'screen' for X: you *can* split the window up, but it is *much* more useful to have only one window v

Re: [Python-Dev] Playing with a new theme for the docs, iteration 2

Georg Brandl wrote: Here's another try, mainly with default browser font size, more contrast and collapsible sidebar again: http://www.python.org/~gbrandl/build/html2/ I've also added a little questionable gimmick to the sidebar (when you collapse it and expand it again, the content is shown at

Re: [Python-Dev] Playing with a new theme for the docs, iteration 2

Georg Brandl wrote: On 25.03.2012 21:11, Steven D'Aprano wrote: Georg Brandl wrote: Thanks everyone for the overwhelmingly positive feedback. I've committed the new design to 3.2 and 3.3 for now, and it will be live for the 3.3 docs momentarily (3.2 isn't rebuilt at the moment until 3.2.3 fin

Re: [Python-Dev] Playing with a new theme for the docs

Glenn Linderman wrote: On 3/26/2012 10:19 AM, R. David Murray wrote: Like Philip, I have *one* window. My window manager (ratpoison) is more like 'screen' for X: you *can* split the window up, but it is *much* more useful to have only one window visible at a time, most of the time. I'm amaz

Re: [Python-Dev] Playing with a new theme for the docs

On 3/26/2012 10:19 AM, R. David Murray wrote: Like Philip, I have*one* window. My window manager (ratpoison) is more like 'screen' for X: you*can* split the window up, but it is*much* more useful to have only one window visible at a time, most of the time. I'm amazed at the number of people

Re: [Python-Dev] Playing with a new theme for the docs

On Mon, 26 Mar 2012 12:55:42 -0400, PJ Eby wrote: > On Sat, Mar 24, 2012 at 8:41 PM, Ben Finney wrote: > > So, again, why make your browser window *for reading text* that large? > > Because I have one browser window, and it's maximized. And I can do this, > because most websites are designed in

Re: [Python-Dev] Python install layout and the PATH on win32 (Rationale part 1: Regularizing the layout)

On 03/23/2012 09:22 PM, PJ Eby wrote: > On Mar 23, 2012 3:53 PM, "Carl Meyer" > On 03/23/2012 12:35 PM, PJ Eby wrote: >> > AFAICT, virtualenvs are overkill for most development anyway. If you're >> > not using distutils except to install dependencies, then configure >> > distutils to install scrip

Re: [Python-Dev] Playing with a new theme for the docs

On Sat, Mar 24, 2012 at 8:41 PM, Ben Finney wrote: > PJ Eby writes: > > > On Sat, Mar 24, 2012 at 1:32 AM, Greg Ewing >wrote: > > > > > If you don't want 1920-pixel-wide text, why make your browser window > > > that large? > > > > Not every tab in my browser is text for reading; some are apps th

Re: [Python-Dev] Playing with a new theme for the docs

On 03/24/2012 03:30 AM, PJ Eby wrote: Weird - I have the exact *opposite* problem, where I have to resize my window because somebody *didn't* set their text max-width sanely (to a reasonable value based on ems instead of pixels), and I have nearly 1920 pixels of raw text spanning my screen.

Re: [Python-Dev] Playing with a new theme for the docs

On Sun, Mar 25, 2012 at 2:56 AM, Stephen J. Turnbull wrote: > But since he's arguing the > other end in the directory layout thread (where he says there are many > special ways to invoke Python so that having different layouts on > different platforms is easy to work around), I can't give much wei

Re: [Python-Dev] Playing with a new theme for the docs, iteration 2

On 3/26/2012 8:46 AM, Zvezdan Petkovic wrote: On Mar 26, 2012, at 12:22 AM, Terry Reedy wrote: Does the css specify Courier New or is this an unfortunate fallback that might be improved? Perhaps things look better on max/*nix? I just checked pydoctheme.css and Courier New is not specified th

Re: [Python-Dev] Python install layout and the PATH on win32

I heard back from Enthought on this part of the proposal. They could accommodate this change. 1) The layout for the python root directory for all platforms should be as follows: stdlib = {base/userbase}/lib/ platstdlib = {base/userbase}/lib/ purelib = {base/userbase}/lib/site-packages platlib =

Re: [Python-Dev] Playing with a new theme for the docs, iteration 2

On Mon, 26 Mar 2012 08:44:40 -0400, Scott Dial wrote: > Why even bother formatting the page? The web started out as *content markup*. Functional declarations, not style declarations. I wish it had stayed that way, but it was inevitable that it would not. > The authorship and editorship have a

Re: [Python-Dev] Playing with a new theme for the docs, iteration 2

the text in the nav bar is too small, particularly in the search box. ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archi

Re: [Python-Dev] Playing with a new theme for the docs, iteration 2

On Mar 26, 2012, at 12:22 AM, Terry Reedy wrote: > Does the css specify Courier New or is this an unfortunate fallback that > might be improved? Perhaps things look better on max/*nix? I just checked pydoctheme.css and Courier New is not specified there. It only specifies monospace. That's a d

Re: [Python-Dev] Playing with a new theme for the docs, iteration 2

On 3/26/2012 1:00 AM, Greg Ewing wrote: > This seems to be another case of the designer over-specifying > things. The page should just specify a sans-serif font and let > the browser choose the best one available. Or not specify > a font at all and leave it up to the user whether he wants > serif o

Re: [Python-Dev] cpython: Adding unittest.mock documentation

On 26.03.2012 00:13, michael.foord wrote: > http://hg.python.org/cpython/rev/adc1fc2dc872 > changeset: 75938:adc1fc2dc872 > user:Michael Foord > date:Sun Mar 25 23:12:55 2012 +0100 > summary: > Adding unittest.mock documentation > > files: > Doc/library/development.rst