On Wed, Dec 8, 2010 at 11:51 AM, Vinay Sajip wrote:
> Nick Coghlan gmail.com> writes:
>
>> Indeed - I was very surprised to find just now that calling
>> "logging.warn('Whatever')" is not the same as doing "log =
>> logging.getLogger(); log.warn('Whatever')".
>
> Don't know why you'd be surprised
On 2010/12/08 0:11, David Bolen wrote:
In thinking about it some more, I suppose there's still a small window
for a loss of communication during a test which results in clean not
being run (which could then block the next svn checkout without an
opportunity to kill the processes), so maybe the ri
On 2010-12-07 17:58 , Vinay Sajip wrote:
Robert Kern gmail.com> writes:
If I had my druthers, I would simply remove the "No handlers could be
found for logger XXX" message. If we always wrote entire applications
from the ground up, it makes a lot of sense. The person that writes the
code tha
Nick Coghlan gmail.com> writes:
> Indeed - I was very surprised to find just now that calling
> "logging.warn('Whatever')" is not the same as doing "log =
> logging.getLogger(); log.warn('Whatever')".
Don't know why you'd be surprised: it's been that way since logging was added to
Python, and th
On Dec 08, 2010, at 12:01 AM, Vinay Sajip wrote:
>Barry, if you mean +1 as in "I agree this is how it should work", then
>we're all agreed.
Yep, that's what I meant!
-Barry
signature.asc
Description: PGP signature
___
Python-Dev mailing list
Python-D
Antoine Pitrou pitrou.net> writes:
>
> Why wouldn't it be the default for all logging calls ? Such special
> cases don't really make things easy to remember.
>
One size doesn't fit all. Everything's documented reasonably well. If you use it
often, you remember it. If you use it seldom, you migh
On Wed, Dec 8, 2010 at 10:09 AM, Antoine Pitrou wrote:
> On Tue, 7 Dec 2010 23:45:39 + (UTC)
> Vinay Sajip wrote:
>> Antoine Pitrou pitrou.net> writes:
>>
>> >
>> > I thought "error" and "critical" messages were logged to stderr by
>> > default? Isn't it the case?
>> >
>>
>> Only if you call
On 12/07/2010 07:09 PM, Vinay Sajip wrote:
Eric Smith trueblade.com> writes:
Wouldn't it make more sense to add these to test.support? I don't think
we make any guarantees about its API being stable, although I have a
faint recollection of that being debated in the past.
That's what I mea
The monitor said it went away at 23:50 UTC and came back 22 minutes
later at 00:12 UTC.
Richard
On Wed, Dec 8, 2010 at 11:07 AM, MRAB wrote:
> I can't get http://pypi.python.org and I've double-checked using
> http://downforeveryoneorjustme.com/.
> _
Eric Smith trueblade.com> writes:
> Wouldn't it make more sense to add these to test.support? I don't think
> we make any guarantees about its API being stable, although I have a
> faint recollection of that being debated in the past.
>
That's what I mean when I said "unit test infrastructu
On Tue, 7 Dec 2010 23:45:39 + (UTC)
Vinay Sajip wrote:
> Antoine Pitrou pitrou.net> writes:
>
> >
> > I thought "error" and "critical" messages were logged to stderr by
> > default? Isn't it the case?
> >
>
> Only if you call basicConfig() or use the logging.debug(), logging.info(),
> et
I can't get http://pypi.python.org and I've double-checked using
http://downforeveryoneorjustme.com/.
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
http://mail.python.org/mailman/option
Barry Warsaw python.org> writes:
>
> On Dec 07, 2010, at 04:59 PM, Robert Kern wrote:
>
> >As a library author, I would dearly love to just add logging liberally
> >without placing any additional burden to the users of my library. If my users
> >wants to read those logs, he will configure loggi
Robert Kern gmail.com> writes:
> If I had my druthers, I would simply remove the "No handlers could be
> found for logger XXX" message. If we always wrote entire applications
> from the ground up, it makes a lot of sense. The person that writes the
> code that issues logs is the same person that
Antoine Pitrou pitrou.net> writes:
>
> I thought "error" and "critical" messages were logged to stderr by
> default? Isn't it the case?
>
Only if you call basicConfig() or use the logging.debug(), logging.info(), etc.
module-level convenience functions (which call basicConfig under the hood).
On Dec 07, 2010, at 04:59 PM, Robert Kern wrote:
>As a library author, I would dearly love to just add logging liberally
>without placing any additional burden to the users of my library. If my users
>wants to read those logs, he will configure logging. If he doesn't, he
>won't. With the current b
On 12/7/10 4:59 PM, Robert Kern wrote:
On 12/7/10 2:26 PM, Vinay Sajip wrote:
This issue was brought to my notice today:
http://bugs.python.org/issue10626
and reference was made in the comments to possible obstacles facing stdlib
maintainers who might wish to use logging in the stdlib and in i
On Tue, Dec 7, 2010 at 13:57, Eric Smith wrote:
> On 12/07/2010 03:26 PM, Vinay Sajip wrote:
>>
>> I would suggest that when unit testing, rather than adding StreamHandlers
>> to log
>> to stderr, that something like TestHandler and Matcher from this post:
>>
>> http://plumberjack.blogspot.com/201
On 12/7/10 2:26 PM, Vinay Sajip wrote:
This issue was brought to my notice today:
http://bugs.python.org/issue10626
and reference was made in the comments to possible obstacles facing stdlib
maintainers who might wish to use logging in the stdlib and in its unit tests.
From my perspective and
Wiadomość napisana przez Antoine Pitrou w dniu 2010-12-07, o godz. 22:19:
>> If you're writing an application then the "No handlers could be found"
>> message is actually useful because there's hardly any reason no to include
>> one.
>
> Why do you say that? Not having to add a handler is certa
2010/12/7 Alexander Belopolsky :
> On Tue, Dec 7, 2010 at 8:02 AM, Vlastimil Brom
> wrote:
> ..
>> Do you know of any re engine fully complying to to tr18, even at the
>> first level: "Basic Unicode Support"?
>>
> """
> ICU Regular Expressions conform to Unicode Technical Standard #18 ,
> Unicode
On 12/07/2010 03:26 PM, Vinay Sajip wrote:
I would suggest that when unit testing, rather than adding StreamHandlers to log
to stderr, that something like TestHandler and Matcher from this post:
http://plumberjack.blogspot.com/2010/09/unit-testing-and-logging.html
This will allow assertion chec
On Tue, Dec 7, 2010 at 8:02 AM, Vlastimil Brom wrote:
..
> Do you know of any re engine fully complying to to tr18, even at the
> first level: "Basic Unicode Support"?
>
"""
ICU Regular Expressions conform to Unicode Technical Standard #18 ,
Unicode Regular Expressions, level 1, and in addition in
On Tue, 7 Dec 2010 22:04:36 +0100
Łukasz Langa wrote:
> Wiadomość napisana przez Antoine Pitrou w dniu 2010-12-07, o godz. 21:50:
>
> > If any library defining a logger must also add a NullHandler just in
> > case, ISTM that complicates a lot the use of logging (and could explain
> > its impopula
Wiadomość napisana przez Antoine Pitrou w dniu 2010-12-07, o godz. 21:50:
> If any library defining a logger must also add a NullHandler just in
> case, ISTM that complicates a lot the use of logging (and could explain
> its impopularity). Both for library writers and application writers,
> appare
On Tue, 7 Dec 2010 20:26:06 + (UTC)
Vinay Sajip wrote:
>
> >From my perspective and as mentioned in the logging documentation, library
> >code
> which uses logging should add a NullHandler instance to any top-level logger,
> which will avoid any "No handlers could be found for logger XXX" me
In article <4cfe6dd1.9030...@netwok.org>,
Éric Araujo wrote:
> > Author: ronald.oussoren
> > New Revision: 87118
> > Log: Two small changes to adjust framework builds to the new stable ABI
> >
> > Modified: python/branches/py3k/Mac/BuildScript/build-installer.py
> > =
This issue was brought to my notice today:
http://bugs.python.org/issue10626
and reference was made in the comments to possible obstacles facing stdlib
maintainers who might wish to use logging in the stdlib and in its unit tests.
>From my perspective and as mentioned in the logging documentatio
Am 07.12.2010 04:03, schrieb Alexander Belopolsky:
> On Sat, Dec 4, 2010 at 5:58 PM, "Martin v. Löwis" wrote:
>>> I actually wonder if Python's re module can claim to provide even
>>> Basic Unicode Support.
>>
>> Do you really wonder? Most definitely it does not.
>>
>
> Were you more optimistic f
Hello,
> Author: ronald.oussoren
> New Revision: 87118
> Log: Two small changes to adjust framework builds to the new stable ABI
>
> Modified: python/branches/py3k/Mac/BuildScript/build-installer.py
> ==
> +LDVERSION=
On Tue, 2010-12-07 at 00:05 +0100, "Martin v. Löwis" wrote:
> >> So by this policy, RHEL and SuSE users would be off worse than with
> >> my original proposal (10 years).
> >
> > Red Hat continues to provide patches for RHEL within the "Extended Life
> > Cycle" (years 8, 9 and 10), but it's an op
Tres Seaver writes:
> Maybe belt-and-suspenders it in both places.
The clean batch file is also called from the build step, so relocating it
there should maintain the existing behavior as well.
Hirokazu (ocean-city) pointed out in my new issue an earlier issue he
created (#9973) that included a
On Tue, Dec 7, 2010 at 8:02 AM, Vlastimil Brom wrote:
..
> It seems, e.g. in Perl, there are some omissions too
> http://perldoc.perl.org/perlunicode.html#Unicode-Regular-Expression-Support-Level
>
> Do you know of any re engine fully complying to to tr18, even at the
> first level: "Basic Unicode
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 12/06/2010 07:24 PM, David Bolen wrote:
> I previously wrote:
>
>> I suspect the problem may be on the "identify which process to kill"
>> rather than the "kill it" part, but it's definitely going to take time
>> to figure that out for sure. While
2010/12/7 Alexander Belopolsky :
> On Sat, Dec 4, 2010 at 5:58 PM, "Martin v. Löwis" wrote:
>>> I actually wonder if Python's re module can claim to provide even
>>> Basic Unicode Support.
>>
>> Do you really wonder? Most definitely it does not.
>>
>
> Were you more optimistic four years ago?
>
>
On 6 December 2010 18:55, "Martin v. Löwis" wrote:
> Am 06.12.2010 14:40, schrieb Floris Bruynooghe:
>> On 6 December 2010 09:18, "Martin v. Löwis" wrote:
Also, it is not clear what to do about distributions/OSs
without any official EOL or life cycles.
>>>
>>> Here my proposal stands: 1
Wiadomość napisana przez Georg Brandl w dniu 2010-12-06, o godz. 22:46:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On behalf of the Python development team, I'm happy to announce the
> first of two beta preview releases of Python 3.2.
>
> Python 3.2 is a continuation of the efforts to
37 matches
Mail list logo
