Re: [Python-mode] milestone 5.1.1

2011-01-09 Thread Barry Warsaw
On Jan 09, 2011, at 08:29 AM, Georg Brandl wrote:

I've now commented out the problematic code -- I'll try to find out more and
maybe ask the Emacs devs, but it's not important enough to hold up a relese.

BTW, NEWS says New in version 5.2.0, so if you want to call the release
5.1.1 you have to adapt this; however I'd say there are enough changes to
warrant a minor-version step.

I agree.  I retired 5.1.1 and moved its items to the 5.2.0 milestone.  I've
tagged the tree and uploaded both the .el and the tgz file.  Thanks for all
your great work; I'm sending the announcement momentarily.

-Barry


signature.asc
Description: PGP signature
___
Python-mode mailing list
Python-mode@python.org
http://mail.python.org/mailman/listinfo/python-mode


[Python-mode] Triple quoted string problem

2011-01-09 Thread skip

I hesitate to open a new bug because this has probably been covered
somewhere and I already opened one (sort of) duplicate bug today, but it's
hard to tell because there are so many open triple-quoted string bug
reports.

Using the latest release I created a new file with just a #! line and a doc
string:

#!/usr/bin/env python


Maintain the recent best price and alert when it remains
the best price for a user-defined time.


When I attempt to fill the docstring's paragraph with the cursor positioned
in front of Maintain it zaps the space before 'best' and fails to actually
fill the paragraph:

#!/usr/bin/env python


Maintain the recentbest price and alert when it remains
the best price for a user-defined time.


If I then move the cursor down a line (point positioned ahead of 'the') and
fill again, I get this:

#!/usr/bin/env python


Maintain the recentbest price and alert when it remains the best price 
for a user-defined
time.


which is pretty bad considering fill-column is set to 70 in that buffer.

This is using XEmacs 21.5.28 on Solaris.  On XEmacs 21.4.22 (on Mac OSX) I
get somewhat different behavior.  There, not sure why, but my fill-column is
76.  It formats the entire docstring onto one line:

#!/usr/bin/env python


Maintain the recentbest price and alert when it remains the best price 
for a user-defined time.


In short, I'm not sure that paragraph filling inside triple-quoted strings
is any better now than before the release.  In fact, it might even be worse
overall. :-(

Skip

___
Python-mode mailing list
Python-mode@python.org
http://mail.python.org/mailman/listinfo/python-mode


Re: [Python-mode] Triple quoted string problem

2011-01-09 Thread skip

When I attempt to fill the docstring's paragraph with the cursor positioned
in front of Maintain it zaps the space before 'best' and fails to actually
fill the paragraph:

#!/usr/bin/env python


Maintain the recentbest price and alert when it remains
the best price for a user-defined time.


FYI, changing the quoting around the word best from quotation marks to
apostrophes results in correct behavior.

S
___
Python-mode mailing list
Python-mode@python.org
http://mail.python.org/mailman/listinfo/python-mode


[Python-mode] avoiding edit wars

2011-01-09 Thread Andreas Röhler

Hi Barry,

with respect to bug-fixing discussions last days it
might be useful to reflect some rules in order to avoid
edit wars.

If several developers join interest in a solution, it's
fine. However, different persons tend to harbour
different opinions, that's normal.

So how to make decisions then?

Probably you won't have the time to make all. Also voting
might not be realistic for the same reason.

So delegation is needed. How to delegate?

Understood the instrument of assigning a bug to someone
in such, having a person in charge not just for writing
fixes but taking care for the process until it's
committed.

Setting the status flags should be part of the job,
as it signals proceeding, might call others for action
etc.

If people don't agree with decisions of the assignee,
they should post to him/her, but not toggle the flags
themselves.

Finally it's your job IMHO to revoke an assignment, if
disputes can't be settled otherwise.

These understanding seems not common so far.

Happy to see things developing fast last days, what's
great. Just makes it worthwhile to address upcoming
dangers.

Thanks all

Andreas
___
Python-mode mailing list
Python-mode@python.org
http://mail.python.org/mailman/listinfo/python-mode