Am 07.12.2011 02:23, schrieb Cameron Simpson:
> On 30Nov2011 22:10, Raymond Hettinger wrote:
> | When updating the documentation, please don't go overboard with warnings.
> | The docs need to be worded affirmatively -- say what a tool does and show
> how to use it correctly.
> | See http://docs.p
> I think we have an unwritten rule that test class and method names
> should tell something about what they test. (We do have things like
> TestWeirdBugs and test_12345, but I don’t think it’s a useful pattern to
> follow :)
I completely disagree. test_12345 is a very good name for a test case,
I've just added a news item to the python.org home page noting that Linux
Journal readers have voted Python the Best Programming Language for the third
year in a row.
This is excellent news, though I find it hard to believe that coming up on the
outside we see C++. While it demonstrates that Li
Hello Steve,
congratulations to all of you in the foundation who work hard to make Python
the success that it is.
Massimo
On Dec 7, 2011, at 12:40 PM, Steve Holden wrote:
> I've just added a news item to the python.org home page noting that Linux
> Journal readers have voted Python the Best P
Georg Brandl wrote:
Am 07.12.2011 02:23, schrieb Cameron Simpson:
On 30Nov2011 22:10, Raymond Hettinger wrote:
| When updating the documentation, please don't go overboard with warnings.
| The docs need to be worded affirmatively -- say what a tool does and show how
to use it correctly.
| See
On Wed, Dec 7, 2011 at 11:00 AM, Ethan Furman wrote:
>
> No, of course not -- although it might /affect/ said reader by causing
> him/her to think, "I don't think that word means what you think it means..."
> ;)
>
> Seriously, it's best to use the correct words with the correct meanings. If
> so
Georg Brandl writes:
> Am 07.12.2011 02:23, schrieb Cameron Simpson:
> > This assures that files are flushed [...]
> >
> > It does not. It _ensures_ that files are flushed. The doco style
> > "affirmative tone" _assures_. The coding practice _ensures_!
>
> Oh, come on, surely this doesn't effe
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 12/07/2011 01:22 PM, Georg Brandl wrote:
> Am 07.12.2011 02:23, schrieb Cameron Simpson:
>> On 30Nov2011 22:10, Raymond Hettinger
>> wrote: | When updating the documentation, please don't go overboard
>> with warnings. | The docs need to be worded
Hi,
I would like to deny the creation of an Unicode string containing characters
outside the range [U+; U+10]. The check is already present in some
places (e.g. the builtin chr() function), but not everywhere. The last
important function is PyUnicode_FromWideChar, function used to decod
Georg Brandl writes:
> Oh, come on, surely this doesn't effect the casual reader?
Casual readers aren't effective in any case; you want to hear the
opinions of those who care.
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/ma
On the heels of Armin's blog post about the troubles of making the same
codebase run on both Python 2 and Python 3, I have a concrete
suggestion.
It would help a lot for code that straddles both Py2 and Py3 to be able
to make use of u'' literals. It would seem to be an easy thing to
reenable (see
2011/12/8 Chris McDonough :
> On the heels of Armin's blog post about the troubles of making the same
> codebase run on both Python 2 and Python 3, I have a concrete
> suggestion.
>
> It would help a lot for code that straddles both Py2 and Py3 to be able
> to make use of u'' literals.
Helpful or
On Thu, 2011-12-08 at 01:02 -0500, Benjamin Peterson wrote:
> 2011/12/8 Chris McDonough :
> > On the heels of Armin's blog post about the troubles of making the same
> > codebase run on both Python 2 and Python 3, I have a concrete
> > suggestion.
> >
> > It would help a lot for code that straddles
2011/12/8 Chris McDonough :
> On Thu, 2011-12-08 at 01:02 -0500, Benjamin Peterson wrote:
>> 2011/12/8 Chris McDonough :
>> > On the heels of Armin's blog post about the troubles of making the same
>> > codebase run on both Python 2 and Python 3, I have a concrete
>> > suggestion.
>> >
>> > It woul
On Thu, 2011-12-08 at 01:18 -0500, Benjamin Peterson wrote:
> 2011/12/8 Chris McDonough :
> > On Thu, 2011-12-08 at 01:02 -0500, Benjamin Peterson wrote:
> >> 2011/12/8 Chris McDonough :
> >> > On the heels of Armin's blog post about the troubles of making the same
> >> > codebase run on both Pytho
Such code still won't work on 3.2, hence restoring the redundant notation
would be ultimately pointless.
--
Nick Coghlan (via Gmail on Android, so likely to be more terse than usual)
On Dec 8, 2011 4:34 PM, "Chris McDonough" wrote:
> On Thu, 2011-12-08 at 01:18 -0500, Benjamin Peterson wrote:
>
On Thu, 2011-12-08 at 17:33 +1000, Nick Coghlan wrote:
> Such code still won't work on 3.2, hence restoring the redundant
> notation would be ultimately pointless.
None of the code I've written which straddles Python 2/3 supports
anything except Python 3.2+, and likewise I expect that for the nex
17 matches
Mail list logo
