FWIW it doesn't hurt to err on the side of what worked. i have generally
have issues with low contrast, the current stable design is very good with
this.
i've just built the docs from tip, and the nav bar issue is fixed, nicely
done
i also don't see any reason to backport theme changes, +0
__
On Mon, Mar 26, 2012 at 05:40, Eli Bendersky wrote:
> On Sat, Mar 24, 2012 at 13:53, Lennart Regebro wrote:
>> On Fri, Mar 23, 2012 at 10:51, Eli Bendersky wrote:
>>> The PEP received mostly positive feedback. The only undecided point is
>>> where to specify that the package is provisional. Curr
Steven D'Aprano wrote:
While I sympathize with the ideal of making the docs readable,
particular for those of us who don't have 20-20 vision, "must be
readable from halfway across the room" is setting the bar too high.
The point is that reducing contrast never makes anything more
readable, an
On 3/25/2012 8:37 PM, Steven D'Aprano wrote:
For what it's worth, it wouldn't surprise me if the problem is the
fallback font. If I'm reading the CSS correctly, the standard font used
in the new docs is Lucinda Grande, with a fallback of Arial.
Unfortunately, Lucinda Grande is normally only avai
On Sun, Mar 25, 2012 at 21:25, 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
>>> momentar
On Sat, Mar 24, 2012 at 13:53, Lennart Regebro wrote:
> On Fri, Mar 23, 2012 at 10:51, Eli Bendersky wrote:
>> The PEP received mostly positive feedback. The only undecided point is
>> where to specify that the package is provisional. Currently the PEP
>> mandates to specify it in the documentati
On 3/25/2012 8:37 PM, Steven D'Aprano wrote:
Terry Reedy wrote:
I ran the following experiment: I put old and new versions of the
buitin functions page side-by-side in separate browser windows. I
asked my teenage daughter to come into the room, approach slowly, and
say when she could read one
On 3/25/2012 8:37 PM, Steven D'Aprano wrote:
> E.g. change the font-family from
>
> font-family: 'Lucida Grande',Arial,sans-serif;
>
> to
>
> font-family: 'Lucida Grande','Lucida Sans Unicode','Lucida
> Sans',Tahoma,Verdana,Arial,sans-serif;
>
> or similar.
>
+1 To providing other fallbacks.
On Sun, Mar 25, 2012 at 05:00, Jon K Peck wrote:
>
> I am out of the office until 03/30/2012.
>
> I will be out of the office through Friday, March 30. I expect to have
> some email access but may be delayed in responding.
>
>
> Note: This is an automated response to your message "Python-Dev Dig
On Mon, Mar 26, 2012 at 7:42 AM, Terry Reedy wrote:
> Can anyone tell me the best way to do that with FireFox?
For general webbrowsing, I'm reasonably impressed by the effectiveness
of www.readability.com. It's a sign-up service however, and I've never
tried it on technical material like the Pyth
Terry Reedy wrote:
On 3/25/2012 12:32 PM, Georg Brandl wrote:
On 25.03.2012 17:54, Terry Reedy wrote:
On 3/25/2012 2:34 AM, Georg Brandl wrote:
Here's another try, mainly with default browser font size, more
contrast
Untrue. You still changed the high contrast dark blue to the same low
contr
> 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.
> For huge numbers _decimal is also faster than int:
>
> factorial(100
Cool, Python 3.3 is *much* faster to decode pure ASCII :-)
> encoding string 2.7 3.2 3.3
>
> ascii " " * 1000 5.4 5.3 1.2
4.5 faster than Python 2 here.
> utf-8 " " * 1000 6.7 2.4 2.1
3.2x faster
It's cool because in practice, a lot
On 3/25/2012 12:32 PM, Georg Brandl wrote:
On 25.03.2012 17:54, Terry Reedy wrote:
On 3/25/2012 2:34 AM, Georg Brandl wrote:
Here's another try, mainly with default browser font size, more contrast
Untrue. You still changed the high contrast dark blue to the same low
contrast light blue for b
Brian Curtin writes:
> On Sun, Mar 25, 2012 at 14:50, Andrew Svetlov
> wrote:
> > I like to see new schema only for 3.3 as sign of shiny new release.
>
> Please don't do this. It will result in endless complaints.
Complaints of what nature? Do you think those complaints are justified?
--
\
On Sun, Mar 25, 2012 at 14:50, Andrew Svetlov wrote:
> I like to see new schema only for 3.3 as sign of shiny new release.
Please don't do this. It will result in endless complaints.
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.o
On Sun, Mar 25, 2012 at 9:25 PM, 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
>>> moment
Anyone can test.
$ ./python -m timeit -s 'enc = "latin1"; import codecs; d =
codecs.getdecoder(enc); x = ("\u0020" * 10).encode(enc)' 'd(x)'
1 loops, best of 3: 59.4 usec per loop
$ ./python -m timeit -s 'enc = "latin1"; import codecs; d =
codecs.getdecoder(enc); x = ("\u0080" * 1000
On Mon, Mar 19, 2012 at 2:50 PM, Ethan Furman wrote:
> [1] I'm assuming that 'iter(some_list)' is a quick operation.
This seems to be the case so I've just gone ahead and renamed
collapse_address_list to collapse_addresses and added 'return
iter(...)' to the end.
The rest of the list-returning
I like to see new schema only for 3.3 as sign of shiny new release.
On Sun, Mar 25, 2012 at 10:25 PM, 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 t
On 3/24/2012 6:37 AM, Victor Stinner wrote:
- time.monotonic(): monotonic clock, its speed may or may not be
adjusted by NTP but it only goes forward, may raise an OSError
- time.steady(): monotonic clock or the realtime clock, depending on
what is available on the platform (use monotonic in prio
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 final goes out
On 25.03.2012 21:09, Matt Joiner wrote:
> Not sure if you addressed this in your answers to other comments...
>
> Scroll down the page. Minimize the nav bar on the left. Bring it back
> out again. Now the text in the nav bar permanently starts at an offset
> from the top of the page.
Yes, that wa
On 25 March 2012 19:51, Serhiy Storchaka wrote:
> Anyone can test.
>
> $ ./python -m timeit -s 'enc = "latin1"; import codecs; d =
> codecs.getdecoder(enc); x = ("\u0020" * 10).encode(enc)' 'd(x)'
> 1 loops, best of 3: 59.4 usec per loop
> $ ./python -m timeit -s 'enc = "latin1"; import co
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 final goes out).
I'll transplant to 2.7 too, probably after the final
Not sure if you addressed this in your answers to other comments...
Scroll down the page. Minimize the nav bar on the left. Bring it back
out again. Now the text in the nav bar permanently starts at an offset
from the top of the page.
On Sun, Mar 25, 2012 at 7:44 PM, Matt Joiner wrote:
> Is nice
25.03.12 20:01, Antoine Pitrou написав(ла):
The general problem with decoding is that you don't know up front what
width (1, 2 or 4 bytes) is required for the result. The solution is
either to compute the width in a first pass (and decode in a second
pass), or decode in a single pass and enlarge
On 25.03.2012 08:34, 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 expa
> How serious a problem this is for the Python 3.3 release? I could do the
> optimization, if someone is not working on this already.
I think the people who did the original implementation (Torsten,
Victor, and myself) are done with optimizations. So: contributions are
welcome. I'm not aware of an
Hi,
On Sun, 25 Mar 2012 19:25:10 +0300
Serhiy Storchaka wrote:
>
> But decoding is not so good.
The general problem with decoding is that you don't know up front what
width (1, 2 or 4 bytes) is required for the result. The solution is
either to compute the width in a first pass (and decode in
On 25.03.2012 13:09, Stephen J. Turnbull wrote:
> On Sun, Mar 25, 2012 at 11:04 AM, Stefan Krah wrote:
>
>> Do you mean a fixed search box like this one?
>>
>> http://coq.inria.fr/documentation
>>
>> Please don't do this, I find scrolling exceptionally distracting in the
>> presence of fixed elem
On 25.03.2012 17:54, Terry Reedy wrote:
> On 3/25/2012 2:34 AM, Georg Brandl wrote:
>> Here's another try, mainly with default browser font size, more contrast
>
> Untrue. You still changed the high contrast dark blue to the same low
> contrast light blue for builtin names, etc. What problem do y
PEP 393 (Flexible String Representation) is, without doubt, one of the
pearls of the Python 3.3. In addition to reducing memory consumption, it
also often leads to a corresponding increase in speed. In particular,
the string encoding now in 1.5-3 times faster.
But decoding is not so good. Here
On 25.03.2012 10:06, Peter Otten wrote:
> 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/
>
> Nice! Lightweight and readable.
>
>>From the bikeshedding departmen
On 25.03.2012 17:26, Ned Batchelder wrote:
> On 3/25/2012 2:34 AM, 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/
> Georg, thanks so much for taking on this thankless
On 25.03.2012 09:19, Ben Finney wrote:
> Georg Brandl writes:
>
>> Here's another try, mainly with default browser font size, more
>> contrast and collapsible sidebar again:
>>
>> http://www.python.org/~gbrandl/build/html2/
>
> Great! You've improved it nicely. I especially like that you have
>
Stephen J. Turnbull wrote:
> Not with just a header. http://turnbull.sk.tsukuba.ac.jp/Teach/IntroSES/
> is a (very primitive and not stylistically improved in years) example
> of a frame-based layout that I use some of my classes. I would
> put a search field in the top frame (if I had one. :-)
On 3/25/2012 2:34 AM, Georg Brandl wrote:
Here's another try, mainly with default browser font size, more contrast
Untrue. You still changed the high contrast dark blue to the same low
contrast light blue for builtin names, etc. What problem do you think
you are trying to solve by making the
On 25/03/2012 16:26, Ned Batchelder wrote:
Georg, thanks so much for taking on this thankless task with grace and
skill. It can't be easy dealing with the death by a thousand tweaks
Seconded. I'm constantly edified by the way in which people
in the community respond to even quite abrupt critici
On 3/25/2012 2:34 AM, 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/
Georg, thanks so much for taking on this thankless task with grace and
skill. It can't be easy dealing w
On Sun, Mar 25, 2012 at 07:07, Antoine Pitrou wrote:
>>
>> I've also added a little questionable gimmick to the sidebar (when you
>> collapse
>> it and expand it again, the content is shown at your current scroll
>> location).
>
> The gimmick is buggy (when you collapse then expand it in the mid
On Sun, Mar 25, 2012 at 2:34 PM, Stefan Krah wrote:
> Stephen J. Turnbull wrote:
>> Does it bother you when the header is fixed and contains
>> the search box? I prefer that arrangement, anyway.
>
> Do you have an example website?
Not with just a header. http://turnbull.sk.tsukuba.ac.jp/Teach
Stephen J. Turnbull wrote:
> > Do you mean a fixed search box like this one?
> >
> > http://coq.inria.fr/documentation
> >
> > Please don't do this, I find scrolling exceptionally distracting in the
> > presence of fixed elements.
>
> Does it bother you when the header is fixed and contains
> the
On Sun, 25 Mar 2012 08:34:44 +0200
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
> collaps
Is nice yes?! When I small the nav bar, then embiggen it again, the text
centers vertically. It's in the wrong place. The new theme is very minimal,
perhaps a new color should be chosen. We've done green, what about orange,
brown or blue?
___
Python-Dev m
On Sun, Mar 25, 2012 at 08:34:44AM +0200, Georg Brandl wrote:
> http://www.python.org/~gbrandl/build/html2/
Perfect! I like it!
Oleg.
--
Oleg Broytmanhttp://phdru.name/p...@phdru.name
Programmers don't die, they just GOSUB without RETURN.
__
On Sun, Mar 25, 2012 at 11:04 AM, Stefan Krah wrote:
> Do you mean a fixed search box like this one?
>
> http://coq.inria.fr/documentation
>
> Please don't do this, I find scrolling exceptionally distracting in the
> presence of fixed elements.
Does it bother you when the header is fixed and con
Serhiy Storchaka wrote:
>> * Maybe the Next/Previous Page headers on the left could link to the
>> respective page.
>
> Do you mean next/previous links in header/footer?
No, I mean the two sections in the sidebar on the left, below "Table of
Contents".
I am out of the office until 03/30/2012.
I will be out of the office through Friday, March 30. I expect to have
some email access but may be delayed in responding.
Note: This is an automated response to your message "Python-Dev Digest,
Vol 104, Issue 91" sent on 03/25/2012 1:19:50.
This is t
Hi Georg,
Am 25.03.2012 um 08:34 schrieb Georg Brandl:
> Here's another try, mainly with default browser font size, more contrast and
> collapsible sidebar again:
>
> http://www.python.org/~gbrandl/build/html2/
I really like it!
Only one nitpick: If a header follows on a “seealso”, the vertica
On Sun, Mar 25, 2012 at 12:04 PM, Stefan Krah wrote:
> Andrew Svetlov wrote:
>> I like to always see "Quick search" widget without scrolling page to
>> top. Is it possible?
>
> Do you mean a fixed search box like this one?
>
> http://coq.inria.fr/documentation
>
No. You are right, it's distractin
Andrew Svetlov wrote:
> I like to always see "Quick search" widget without scrolling page to
> top. Is it possible?
Do you mean a fixed search box like this one?
http://coq.inria.fr/documentation
Please don't do this, I find scrolling exceptionally distracting in the
presence of fixed elements
25.03.12 09:34, Georg Brandl написав(ла):
I've also added a little questionable gimmick to the sidebar (when you collapse
it and expand it again, the content is shown at your current scroll location).
I'm not sure if this is possible, and how good it would look like, but I
have one crazy idea.
In the header next to "Python v3.3a1 documentation" there is a
"»" symbol, which suggests something can be expanded. Knowing
that there are many versions of the documentation, I thought it
might bring up a menu of versions. But clicking does nothing. Is
that intentional? I guess it's supposed t
I like to always see "Quick search" widget without scrolling page to
top. Is it possible?
Or maybe you can embed some keyboard shortcut for quick jump to search
input box?
On Sun, Mar 25, 2012 at 11:44 AM, Serhiy Storchaka wrote:
> 25.03.12 11:06, Peter Otten написав(ла):
>
>> * Inlined code does
25.03.12 11:06, Peter Otten написав(ла):
* Inlined code doesn't need the gray background. The bold font makes it
stand out enough.
I believe that the gray background is good, but it should make it lighter.
* Instead of the box consider italics or another color for [New in ...]
text.
Yes, th
25.03.12 09:34, Georg Brandl написав(ла):
Here's another try, mainly with default browser font size, more contrast and
collapsible sidebar again:
It may be worth now the line-height reduce too?
I've also added a little questionable gimmick to the sidebar (when you collapse
it and expand it ag
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/
Nice! Lightweight and readable.
>From the bikeshedding department:
* Inlined code doesn't need the gray background. Th
On 3/24/2012 11:34 PM, Georg Brandl wrote:
I've also added a little questionable gimmick to the sidebar (when you collapse
it and expand it again, the content is shown at your current scroll location).
It would be educational to see how you pulled that trick! I will look if
I get time. However
On Sun, Mar 25, 2012 at 08:34, 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
Georg Brandl writes:
> Here's another try, mainly with default browser font size, more
> contrast and collapsible sidebar again:
>
> http://www.python.org/~gbrandl/build/html2/
Great! You've improved it nicely. I especially like that you have
https://en.wikipedia.org/wiki/Unobtrusive_JavaScript>
61 matches
Mail list logo
