Re: Issue 11715: building Python from source on multiarch Debian/Ubuntu

On Apr 01, 2011, at 08:37 AM, Nick Coghlan wrote:

>On Fri, Apr 1, 2011 at 3:35 AM, Éric Araujo <merwok <at> netwok.org> 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 checkout or from source (since
>they need to be able to do that in order to apply security patches).
>
>However, the combination of "running on Ubuntu 11.04+" and "need to
>build security patched version of old Python" seems unlikely.

I'll just plead as RM for 2.6 that it's not as unlikely as it seems :).

I'm happy to defer to MvL on its (non) applicability to 2.5.

Cheers,
-Barry

On Apr 01, 2011, at 08:37 AM, Nick Coghlan wrote:

>On Fri, Apr 1, 2011 at 3:35 AM, Éric Araujo <merwok <at> netwok.org> 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 checkout or from source (since
>they need to be able to do that in order to apply security patches).

Re: Please revert autofolding of tracker edit form

<div>
    On 3/31/2011 9:52 AM, Terry Reedy wrote:<br><blockquote cite="mid:in2bg7$v5q$1 <at> dough.gmane.org" type="cite">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.
    </blockquote>
    <br>
    +1.&nbsp;&nbsp; Or +0 reverse time sequence the messages.<br>
</div>

Re: Please revert autofolding of tracker edit form

On Thu, 31 Mar 2011 23:59:36 +0200, =?ISO-8859-1?Q?=22Martin_v=2E_L=F6wis=22?=
<martin <at> v.loewis.de> 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

Re: Please revert autofolding of tracker edit form

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. 
> 
> +1.   Or +0 reverse time sequence the messages.

-1 on reverse time sequence of messages -- no top posting!  ;)

~Ethan~

warn_unused_result warnings

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

Re: devguide: Add a table of contents to the FAQ.

On Fri, 01 Apr 2011 08:29:29 +1000, Nick Coghlan <ncoghlan <at> gmail.com> wrote:
> On Fri, Apr 1, 2011 at 2:34 AM, R. David Murray <rdmurray <at> bitdance.com> 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 in this case to only show the categories and not the
> individual questions.

I believe that requires editing the sphinx page template and adding
a special case of some sort.

--
R. David Murray           http://www.bitdance.com

Impaired Usability of the Mercurial Source Viewer

<div>
<div>The Hg source viewer needs to be tweaked to improve its usability.</div>
<div>What we've got now is a step backwards from the previous svn viewer.</div>
<div><br></div>
<div>Looking at&nbsp;<a href="http://hg.python.org/cpython/file/default/Lib/linecache.py">http://hg.python.org/cpython/file/default/Lib/linecache.py</a>&nbsp;for example,</div>
<div>there are two issues. &nbsp; 1) the code cannot be cut-and-pasted because the</div>
<div>line numbers are commingled with the source text. &nbsp;2) the code is hard</div>
<div>to read because of the alternating white and gray bars.</div>
<div><br></div>
<div>Contrast that to the more typical, beautiful presentations with a solid</div>
<div>background and the ability to cut-and-paste without grabbing line</div>
<div>numbers:</div>
<div><br></div>
<div>&nbsp;&nbsp;<a href="http://dpaste.org/qyKv/">http://dpaste.org/qyKv/</a>
</div>
<div><br></div>
<div>&nbsp;&nbsp;<a href="http://code.activestate.com/recipes/577629-namedtupleabc-abstract-base-class-mix-in-for-named/">http://code.activestate.com/recipes/577629-namedtupleabc-abstract-base-class-mix-in-for-named/</a>
</div>
<div><br></div>
<div><br></div>
<div>Raymond</div>
<div><br></div>
<div><br></div>
<div>P.S. &nbsp;The old svn viewer worked great (looked good and could be cut),</div>
<div>but that was changed just before the Mercurial switchover (the fonts</div>
<div>changed, the line numbering code changed, and the leading changed),</div>
<div>so it is not a good comparison anymore.</div>
</div>

Re: Please revert autofolding of tracker edit form

<div>
<br><div>
<div>On Mar 31, 2011, at 9:52 AM, Terry Reedy wrote:</div>
<br><blockquote type="cite"><div>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.<br>
</div></blockquote>
<br>
</div>
<div>While that sounds logical, I think it will be a usability problem. &nbsp;If someone doesn't see a the comment box immediately, they may not know to scroll down past dozens of messages to find it.</div>
<div><br></div>
<div>Rather that being trial-and-error amateur web page designers, it would be better to follow proven models. &nbsp;All of the following have the comment box at the top and the messages in reverse chronological order:</div>
<div><br></div>
<div>*&nbsp;<a href="http://news.ycombinator.com/item?id=2393587">http://news.ycombinator.com/item?id=2393587</a>&nbsp;&nbsp;</div>*&nbsp;<a href="http://digg.com/news/entertainment/top_12_game_shows_of_all_time">http://digg.com/news/entertainment/top_12_game_shows_of_all_time</a><div>*&nbsp;<a href="https://twitter.com/">https://twitter.com/</a>
</div>
<div><br></div>
<div><br></div>
<div>Raymond</div>
</div>

Re: Please revert autofolding of tracker edit form

2011/3/31 Raymond Hettinger <raymond.hettinger <at> gmail.com>:
>
> 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 that sounds logical, I think it will be a usability problem.  If
> someone doesn't see a the comment box immediately, they may not know to
> scroll down past dozens of messages to find it.
> Rather that being trial-and-error amateur web page designers, it would be
> better to follow proven models.  All of the following have the comment box
> at the top and the messages in reverse chronological order:

Please no reverse chronological order! Every bug tracker I know which
isn't underconfigured roundup uses chronological order.

--

-- 
Regards,
Benjamin
_______________________________________________
Python-Dev mailing list
Python-Dev <at> python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: http://mail.python.org/mailman/options/python-dev/python-python-dev%40m.gmane.org

Re: Please revert autofolding of tracker edit form

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 between comment box and last
> > message(s) is often of a nuisance.
> > 
> 
> 
> While that sounds logical, I think it will be a usability problem.  If
> someone doesn't see a the comment box immediately, they may not know
> to scroll down past dozens of messages to find it.
> 
> 
> Rather that being trial-and-error amateur web page designers, it would
> be better to follow proven models.  All of the following have the
> comment box at the top and the messages in reverse chronological
> order:
> 
> 
> * http://news.ycombinator.com/item?id=2393587  
> * http://digg.com/news/entertainment/top_12_game_shows_of_all_time
> * https://twitter.com/
> 
> 
> 
> 
> Raymond

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 call it, but when it comes to following a
discussion it's much easier to start with the first word.