On 12/22/2010 1:21 AM, Nick Coghlan wrote:
On Wed, Dec 22, 2010 at 1:39 PM, Terry Reedy wrote:
Python 3.2 PyDoc Server (32 bit)
is shorter. But since pydoc.py is has no 'bitness',
PyDoc Server (Python 3.2 - 32 bit)
is more in line with below
- IDLE (Python 3.2 GUI - 32 bit)
I think
On 12/22/2010 1:23 AM, Adal Chiriliuc wrote:
Microsoft recommendations:
Irrelevant.
Avoid putting a version number in a program name unless that is how
users normally refer to your program.
Version numbers are the point of this issue, because people *do* have
multiple version installed.
> I put my initial proposal (reproduced below) at
> http://bugs.python.org/issue10747. I'll let this thread run a bit and
> see if there are any substantial improvements suggested, or valid
> objections raised (I tried to pre-empt the length issue by pushing the
> typically least important informat
Microsoft recommendations:
Avoid putting a version number in a program name unless that is how
users normally refer to your program.
Put only program shortcuts on the Start menu. Don't put shortcuts to
the following items on the Start menu:
- Program uninstallers. Users access uninstallers throug
On Wed, Dec 22, 2010 at 1:39 PM, Terry Reedy wrote:
> Python 3.2 PyDoc Server (32 bit)
> is shorter. But since pydoc.py is has no 'bitness',
>
> PyDoc Server (Python 3.2 - 32 bit)
> is more in line with below
>
>> - IDLE (Python 3.2 GUI - 32 bit)
>
> I think of IDLE as an IDE, not a GUI, but
On Tue, Dec 21, 2010 at 9:16 PM, Terry Reedy wrote:
..
>> A non-normative HTML file listing all valid identifier characters for
>> Unicode
>> 4.1 can be found at
>> http://www.dcl.hpi.uni-potsdam.de/home/loewis/table-3131.html
>
> Has that file been updated for Unicode 6.0?
Apparently not. In
On 12/21/2010 8:37 PM, alexander.belopolsky wrote:
Author: alexander.belopolsky
Date: Wed Dec 22 02:37:36 2010
New Revision: 87433
Log:
Both PEP 3131 and the current implementation use NFKC normalization
for identifiers. Fixed the documentation to agree.
Modified:
python/branches/py3k/D
On 12/21/2010 7:01 AM, Nick Coghlan wrote:
On Tue, Dec 21, 2010 at 6:36 PM, "Martin v. Löwis" wrote:
Given the changing dynamics of the desktop launch menus to better
support direct access as an alternative to hierarchical navigation,
would it be reasonable to consider including the major versi
On 12/21/2010 7:17 AM, Michael Foord wrote:
My first priority is that doc and code match.
Close second is consistency (hence, ease of learning and use) between
various AssertXs.
Symmetrical diffs (element in first not in second, element in second not
in first) solves the problem without impos
On Tue, Dec 21, 2010 at 5:12 PM, Nick Coghlan wrote:
> I actually agree with Guido that anything we do is going to be
> suboptimal in some way. Encouraging the actual/expected ordering and
> updating the diff output so "expected=old" strikes me as least bad,
> but using the neutral first/second te
On Wed, Dec 22, 2010 at 6:18 AM, Georg Brandl wrote:
> Since PEP 3003, the Moratorium on Language Changes, is in effect, there
> are no changes in Python's syntax and built-in types in Python 3.2.
Minor nit - we actually did tweak a few of the builtin types a bit
(mostly the stuff to improve Sequ
On Tue, Dec 21, 2010 at 11:17 PM, Michael Foord
wrote:
> On 21/12/2010 01:57, Nick Coghlan wrote:
>> My own +1 goes to keeping the actual/expected terminology (and
>> ordering) and adjusting the diffs accordingly (with a header noting
>> that the diff is old=expected, new=actual).
>>
>
> Well we d
On Tue, Dec 21, 2010 at 4:17 AM, Michael Foord
wrote:
> On 21/12/2010 01:57, Nick Coghlan wrote:
>>
>> On Tue, Dec 21, 2010 at 1:31 AM, Antoine Pitrou
>> wrote:
Diffing is completely an implementation detail of how the failure
messages are generated. The important thing is that fai
On 12/21/2010 4:17 AM, Michael Foord wrote:
Glenn Linderman wants (actual, expected) and diffing to follow that
If you say that is what I said, fine. I might not have understood the
example well enough to say the right thing. I liked Nick's explanation,
using the actual and expected words i
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On behalf of the Python development team, I'm happy to announce the
second beta preview release of Python 3.2.
Python 3.2 is a continuation of the efforts to improve and stabilize the
Python 3.x line. Since the final release of Python 2.7, the 2.x li
On 21/12/2010 01:57, Nick Coghlan wrote:
On Tue, Dec 21, 2010 at 1:31 AM, Antoine Pitrou wrote:
Diffing is completely an implementation detail of how the failure
messages are generated. The important thing is that failure messages
make sense with respect to actual result and expected result.
W
On Tue, Dec 21, 2010 at 6:36 PM, "Martin v. Löwis" wrote:
>> Given the changing dynamics of the desktop launch menus to better
>> support direct access as an alternative to hierarchical navigation,
>> would it be reasonable to consider including the major version number
>> in the start menu shortc
17 matches
Mail list logo