On 3/31/2011 8:44 PM, Antoine Pitrou wrote:
Impacting only the source viewer looks like it would require a patch
to the generation logic, although I could be mistaken.
Is there not something in the context surrounding the changelog and the
source viewer that is different? And therefore someth
On 2011-03-31, at 8:44 PM, Antoine Pitrou wrote:
> On Thu, 31 Mar 2011 18:20:53 -0700
> Raymond Hettinger wrote:
>>
>> Surely, we at least have control over our own CSS.
>> At http://hg.python.org/cpython/static/style-paper.css
>> there are two lines that control the alternating bars:
>>
>> .
On 3/31/2011 8:26 PM, Antoine Pitrou wrote:
On Thu, 31 Mar 2011 12:52:23 -0400
Terry Reedy wrote:
Here is my proposal for a redesign based on an analysis of my usage ;-).
I have a 1600x1050 (or thereabouts), 20" (measured) diagonal, 17" across
screen.
The left column has a 7/8" margin, 2 3/8"
On Thu, 2011-03-31 at 21:21 -0500, s...@pobox.com wrote:
> Antoine> Let's say that by using non-metric units you have already lost
> Antoine> me, sorry.
>
> Wouldn't it be cool if you could feed the text to Google Translator and have
> it not only translate the English to bad French, but trans
On Thu, 2011-03-31 at 21:18 -0500, s...@pobox.com wrote:
> Terry> Even though such is standard for the majority of web fora?
>
> I participate in a couple different web forums (914s and swimming). Both
> present their topics in chronological order and provide a link at the top of
> every page whi
On Thu, 31 Mar 2011 18:20:53 -0700
Raymond Hettinger wrote:
>
> Surely, we at least have control over our own CSS.
> At http://hg.python.org/cpython/static/style-paper.css
> there are two lines that control the alternating bars:
>
> .parity0 { background-color: #f0f0f0; }
> .parity1 { backgroun
On 3/31/2011 5:22 PM, Raymond Hettinger wrote:
Perhaps the most important part is that the comment box goes at the top.
As long as it is adjacent to the last comment, that would be fine.
(said while tongue removing the last bit of supper from the space
outside the teeth)
Ethan> Are there cases where someone should be posting new comments who
Ethan> /hasn't/ read the existing comments? I would hope that new
Ethan> comments would come only after reading what has already
Ethan> transpired -- in which case one would find the comment box when
Ethan
Antoine> Let's say that by using non-metric units you have already lost
Antoine> me, sorry.
Wouldn't it be cool if you could feed the text to Google Translator and have
it not only translate the English to bad French, but translate the units to
metric (hopefully with more accuracy than th
Terry> Even though such is standard for the majority of web fora?
I participate in a couple different web forums (914s and swimming). Both
present their topics in chronological order and provide a link at the top of
every page which jumps the user to the first unread message (no matter how
m
>> I would like to try putting the comment box after the last (most
>> recent) comment, as that is the message one most ofter responds
>> to. Having to now scroll up and down between comment box and last
>> message(s) is often of a nuisance.
Raymond> While that sounds logical,
Ethan Furman writes:
> -1 on reverse time sequence of messages -- no top posting! ;)
I'd really like this to be a browse-time option, and for bonus points,
it should be "sticky". For issues I'm not familiar with, I want to
read in more or less chronological order. For issues I *am* familiar
w
Can someone give Raymond write access to the website already so he can
fix it himself?
On Thu, Mar 31, 2011 at 6:44 PM, Benjamin Peterson wrote:
> 2011/3/31 Raymond Hettinger :
>>
>> On Mar 31, 2011, at 6:28 PM, Victor Stinner wrote:
>>
>> Le 01/04/2011 01:15, Raymond Hettinger a écrit :
>>
>> Th
On 3/31/2011 8:30 PM, Antoine Pitrou wrote:
> On Thu, 31 Mar 2011 16:15:48 -0700
> Raymond Hettinger wrote:
>> The Hg source viewer needs to be tweaked to improve its usability.
>> What we've got now is a step backwards from the previous svn viewer.
>>
>> Looking at http://hg.python.org/cpython/fi
2011/3/31 Raymond Hettinger :
>
> On Mar 31, 2011, at 6:28 PM, Victor Stinner wrote:
>
> Le 01/04/2011 01:15, Raymond Hettinger a écrit :
>
> The Hg source viewer needs to be tweaked to improve its usability.
>
> What we've got now is a step backwards from the previous svn viewer.
>
> Looking at ht
On Mar 31, 2011, at 6:28 PM, Victor Stinner wrote:
> Le 01/04/2011 01:15, Raymond Hettinger a écrit :
>> The Hg source viewer needs to be tweaked to improve its usability.
>> What we've got now is a step backwards from the previous svn viewer.
>>
>> Looking at http://hg.python.org/cpython/file/d
Le 01/04/2011 01:15, Raymond Hettinger a écrit :
The Hg source viewer needs to be tweaked to improve its usability.
What we've got now is a step backwards from the previous svn viewer.
Looking at
http://hg.python.org/cpython/file/default/Lib/linecache.py for example,
there are two issues. 1)
2011/3/31 Victor Stinner :
> Le 01/04/2011 01:11, Benjamin Peterson a écrit :
>>
>> I'm rather sick of seeing this warnings on all compiles, so I propose
>> we enable the -Wno-unused-results option. I judge that most of the
>> cases where this occurs are error reporting functions, where not much
>>
Le 01/04/2011 01:11, Benjamin Peterson a écrit :
I'm rather sick of seeing this warnings on all compiles, so I propose
we enable the -Wno-unused-results option. I judge that most of the
cases where this occurs are error reporting functions, where not much
with return code can be done.
Can't we tr
On Mar 31, 2011, at 5:55 PM, Antoine Pitrou wrote:
> Le jeudi 31 mars 2011 à 17:46 -0700, Raymond Hettinger a écrit :
>> On Mar 31, 2011, at 5:30 PM, Antoine Pitrou wrote:
>>
>>> On Thu, 31 Mar 2011 16:15:48 -0700
>>> Raymond Hettinger wrote:
The Hg source viewer needs to be tweaked to imp
Raymond Hettinger wrote:
On Mar 31, 2011, at 9:52 AM, Terry Reedy wrote:
I would like to try putting the comment box after the last (most
recent) comment, as that is the message one most ofter responds to.
Having to now scroll up and down between comment box and last
message(s) is often of a n
Le jeudi 31 mars 2011 à 17:46 -0700, Raymond Hettinger a écrit :
> On Mar 31, 2011, at 5:30 PM, Antoine Pitrou wrote:
>
> > On Thu, 31 Mar 2011 16:15:48 -0700
> > Raymond Hettinger wrote:
> >> The Hg source viewer needs to be tweaked to improve its usability.
> >> What we've got now is a step bac
On Mar 31, 2011, at 5:30 PM, Antoine Pitrou wrote:
> On Thu, 31 Mar 2011 16:15:48 -0700
> Raymond Hettinger wrote:
>> The Hg source viewer needs to be tweaked to improve its usability.
>> What we've got now is a step backwards from the previous svn viewer.
>>
>> Looking at http://hg.python.org/
On Thu, 31 Mar 2011 18:11:46 -0500
Benjamin Peterson wrote:
> I'm rather sick of seeing this warnings on all compiles, so I propose
> we enable the -Wno-unused-results option. I judge that most of the
> cases where this occurs are error reporting functions, where not much
> with return code can be
On Thu, 31 Mar 2011 16:15:48 -0700
Raymond Hettinger wrote:
> The Hg source viewer needs to be tweaked to improve its usability.
> What we've got now is a step backwards from the previous svn viewer.
>
> Looking at http://hg.python.org/cpython/file/default/Lib/linecache.py for
> example,
> there
On Thu, 31 Mar 2011 12:52:23 -0400
Terry Reedy wrote:
>
> Here is my proposal for a redesign based on an analysis of my usage ;-).
> I have a 1600x1050 (or thereabouts), 20" (measured) diagonal, 17" across
> screen.
>
> The left column has a 7/8" margin, 2 3/8" text area, and 1" gutter.
> Thes
On 3/31/2011 7:15 PM, Raymond Hettinger wrote:
The Hg source viewer needs to be tweaked to improve its usability.
What we've got now is a step backwards from the previous svn viewer.
Looking at http://hg.python.org/cpython/file/default/Lib/linecache.py
for example,
there are two issues. 1) the c
On Thu, 31 Mar 2011 23:59:36 +0200
"Martin v. Löwis" wrote:
> > What's more, it lacks the most important: the issue title.
>
> Notice that the issue title was always there, in your browser's title
> bar (unless you have a web browser that doesn't display the page title).
Sure, but it's far remov
On 3/31/2011 7:27 PM, Raymond Hettinger wrote:
On Mar 31, 2011, at 9:52 AM, Terry Reedy wrote:
I would like to try putting the comment box after the last (most
recent) comment, as that is the message one most ofter responds to.
Having to now scroll up and down between comment box and last
mess
On Mar 31, 2011, at 5:02 PM, Westley Martínez wrote:
>
> How 'bout no? YouTube uses this and it's horrid and unnatural, and
> bulletin boards have been using chronological order for whiles with
> great success. Reverse chronological order has a niche for feeds,
> updates, whatever you want to cal
On Thu, 2011-03-31 at 16:27 -0700, Raymond Hettinger wrote:
>
> On Mar 31, 2011, at 9:52 AM, Terry Reedy wrote:
>
> > I would like to try putting the comment box after the last (most
> > recent) comment, as that is the message one most ofter responds to.
> > Having to now scroll up and down betwe
2011/3/31 Raymond Hettinger :
>
> On Mar 31, 2011, at 9:52 AM, Terry Reedy wrote:
>
> I would like to try putting the comment box after the last (most recent)
> comment, as that is the message one most ofter responds to. Having to now
> scroll up and down between comment box and last message(s) is
On Mar 31, 2011, at 9:52 AM, Terry Reedy wrote:
> I would like to try putting the comment box after the last (most recent)
> comment, as that is the message one most ofter responds to. Having to now
> scroll up and down between comment box and last message(s) is often of a
> nuisance.
While t
The Hg source viewer needs to be tweaked to improve its usability.
What we've got now is a step backwards from the previous svn viewer.
Looking at http://hg.python.org/cpython/file/default/Lib/linecache.py for
example,
there are two issues. 1) the code cannot be cut-and-pasted because the
line
On Fri, 01 Apr 2011 08:29:29 +1000, Nick Coghlan wrote:
> On Fri, Apr 1, 2011 at 2:34 AM, R. David Murray wro=
> te:
> > I agree with this point. =A0The sidebar list of questions is effectively
> > useless.
>
> Indeed. If it's simple, I'd actually be inclined to reduce the depth
> of the sidebar
I'm rather sick of seeing this warnings on all compiles, so I propose
we enable the -Wno-unused-results option. I judge that most of the
cases where this occurs are error reporting functions, where not much
with return code can be done.
--
Regards,
Benjamin
___
Glenn Linderman wrote:
On 3/31/2011 9:52 AM, Terry Reedy wrote:
I would like to try putting the comment box after the last (most
recent) comment, as that is the message one most ofter responds to.
Having to now scroll up and down between comment box and last
message(s) is often of a nuisance
On Thu, 31 Mar 2011 23:59:36 +0200, =?ISO-8859-1?Q?=22Martin_v=2E_L=F6wis=22?=
wrote:
> Notice that the issue title was always there, in your browser's title
> bar (unless you have a web browser that doesn't display the page title).
I do.
--
R. David Murray http://www.bitdance.com
___
On 3/31/2011 9:52 AM, Terry Reedy wrote:
I would like to try putting the comment box after the last (most
recent) comment, as that is the message one most ofter responds to.
Having to now scroll up and down between comment box and last
message(s) is often of a nuisance.
+1. Or +0 reverse t
On Apr 01, 2011, at 08:37 AM, Nick Coghlan wrote:
>On Fri, Apr 1, 2011 at 3:35 AM, Éric Araujo wrote:
>> If I understand the policy correctly, 2.5 and 2.6 are not considered
>> active branches, so any doc, build or bug fixes are not acceptable.
>
>Actual build fixes may be acceptable, if they're
On Fri, Apr 1, 2011 at 3:35 AM, Éric Araujo wrote:
> If I understand the policy correctly, 2.5 and 2.6 are not considered
> active branches, so any doc, build or bug fixes are not acceptable.
Actual build fixes may be acceptable, if they're needed to allow
people to build from a version control c
On Fri, Apr 1, 2011 at 2:34 AM, R. David Murray wrote:
> I agree with this point. The sidebar list of questions is effectively
> useless.
Indeed. If it's simple, I'd actually be inclined to reduce the depth
of the sidebar in this case to only show the categories and not the
individual questions.
> What's more, it lacks the most important: the issue title.
Notice that the issue title was always there, in your browser's title
bar (unless you have a web browser that doesn't display the page title).
Regards,
Martin
___
Python-Dev mailing list
Pytho
> > http://hg.python.org/cpython/rev/61626c3f3a54
> >...
> > -assert (b -a)>= pause
> > +assert (b - a)>= pause, "{{}}< {{}}".format(b - a, pause)
>
> > +assert (b - a)>= pause, "{{}}< {{}}".format(b - a, pause)
>
> >>> a,b,pause = 0,0,1
> >>> "{{}} < {{}}".format(b - a, pause
Hi,
On 31/03/2011 19.52, Terry Reedy wrote:
On 3/31/2011 9:59 AM, Antoine Pitrou wrote:
Le jeudi 31 mars 2011 à 23:48 +1000, Nick Coghlan a écrit :
On Thu, Mar 31, 2011 at 10:16 PM, Antoine
Pitrou wrote:
It would be nice if someone with UI design experience was
interested in
maintaining/imp
> I would like to apply this patch (or its moral equivalent) to all active,
> affected branches of Python, meaning 2.5 through 2.7, and 3.1 through 3.3, as
> soon as possible. Without this, it will be very difficult for anyone on
> future Ubuntu or Debian releases to build Python. Since it's not
On 3/31/2011 9:59 AM, Antoine Pitrou wrote:
Le jeudi 31 mars 2011 à 23:48 +1000, Nick Coghlan a écrit :
On Thu, Mar 31, 2011 at 10:16 PM, Antoine Pitrou wrote:
It would be nice if someone with UI design experience was interested in
maintaining/improving the tracker.
The challenge is the same
Hi,
I just added a --timeout option to Lib/test/regrtest.py: if a test (one
function, not a whole file) takes more than TIMEOUT seconds, the
traceback is dumped and it exits. I tested it on 3 buildbots with a
timeout of 5 minutes and it worked as expected: see #11727 for
examples.
It would be ni
On Thu, 31 Mar 2011 18:47:39 +0300, Ezio Melotti wrote:
> On 30/03/2011 23.20, Antoine Pitrou wrote:
> > On Tue, 29 Mar 2011 21:00:22 +0200
> > ezio.melotti wrote:
> >> http://hg.python.org/devguide/rev/f722956afeac
> >> changeset: 405:f722956afeac
> >> user:Ezio Melotti
> >> date:
On 30/03/2011 23.20, Antoine Pitrou wrote:
On Tue, 29 Mar 2011 21:00:22 +0200
ezio.melotti wrote:
http://hg.python.org/devguide/rev/f722956afeac
changeset: 405:f722956afeac
user:Ezio Melotti
date:Tue Mar 29 22:00:13 2011 +0300
summary:
Add a table of contents to the FAQ.
C
2011/3/31 Tres Seaver :
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On 03/30/2011 09:54 PM, Victor Stinner wrote:
>> Hi,
>>
>> I pushed my faulthandler module into the default branch (Python 3.3).
>> Since one week, I fixed a lot of bugs (platform issues), improved the
>> tests and Antoin
Le jeudi 31 mars 2011 à 23:48 +1000, Nick Coghlan a écrit :
> On Thu, Mar 31, 2011 at 10:16 PM, Antoine Pitrou wrote:
> > It would be nice if someone with UI design experience was interested in
> > maintaining/improving the tracker.
>
> The challenge is the same as with any UI designer involvemen
On Thu, Mar 31, 2011 at 10:16 PM, Antoine Pitrou wrote:
> It would be nice if someone with UI design experience was interested in
> maintaining/improving the tracker.
The challenge is the same as with any UI designer involvement in open
source stuff though: they really need to be given the freedo
Hi all members,
I'm Francesco and I am writing on behalf of "Python Italia APS", a no-profit
association promoting EuroPython conference. (www.europython.eu)
Europython End of Call for Presentations is April 6th. I'd like to ask to
you to forward this mail to anyone that you feel may be interested
On 3/31/2011 12:31 AM, Mark Hammond wrote:
Hi,
There are a couple of changes I'd like to make and would like some
guidance on policy:
http://bugs.python.org/issue6498 is a documentation bug which exists in
Python 2.6 and later. The patch in that bug touches the docs and a
comment in one source f
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 03/30/2011 09:54 PM, Victor Stinner wrote:
> Hi,
>
> I pushed my faulthandler module into the default branch (Python 3.3).
> Since one week, I fixed a lot of bugs (platform issues), improved the
> tests and Antoine wrote a new implementation of dum
On Thu, 31 Mar 2011 06:20:03 -0500
s...@pobox.com wrote:
>
> skip> Please see this thread in the tracker-discuss list:
> skip>
> http://mail.python.org/pipermail/tracker-discuss/2011-March/thread.html
>
> That didn't read right. I meant see that thread to see other discussion
> abou
skip> Please see this thread in the tracker-discuss list:
skip>
http://mail.python.org/pipermail/tracker-discuss/2011-March/thread.html
That didn't read right. I meant see that thread to see other discussion
about the folding topic, not that it would necessary convince you all to
ch
Please see this thread in the tracker-discuss list:
http://mail.python.org/pipermail/tracker-discuss/2011-March/thread.html
Skip
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
http:
On Wed, Mar 30, 2011 at 10:08 PM, Terry Reedy wrote:
> Yes, there is a good reason why database records are routinely displayed in
> labeled and located fields rather than in variable length natural language
> sentences with a monochrome font. Form letters, of course, are an exception.
Yep.
Whil
60 matches
Mail list logo
