Brett Cannon wrote:
> On 7/9/07, Nick Coghlan <[EMAIL PROTECTED]> wrote:
>> Given the above limitations, I propose that we document the new
>> attribute as follows:
>>
>> "If the module global __package__ exists when executing an import
>> statement, it is used to determine the base for relative im
Hello,
We recently had a production failure caused by the issue fixed in r53624
on the trunk [1]. I see that this patch has also been applied to
py3k-struni. Should this patch be merged to the release branches? In
the meantime we will have to patch subprocess.py ourselves.
[1]
http://mail
Aaron> We recently had a production failure caused by the issue fixed in
Aaron> r53624 on the trunk [1]. I see that this patch has also been
Aaron> applied to py3k-struni. Should this patch be merged to the
Aaron> release branches? In the meantime we will have to patch
Aaron
[EMAIL PROTECTED] wrote:
> Aaron> We recently had a production failure caused by the issue fixed in
> Aaron> r53624 on the trunk [1]. I see that this patch has also been
> Aaron> applied to py3k-struni. Should this patch be merged to the
> Aaron> release branches? In the meantime
One of the most daunting tasks remaining for Python 3.0a1 (to be
released by the end of August) is fixing the remaining failing unit
tests in the py3k-struni branch
(http://svn.python.org/view/python/branches/py3k-struni/).
This is the branch where I have started the work on the
string/unification
Guido van Rossum wrote:
> Please help!
I've made a meta patch that makes debugging the bugs a lot easier. It
replaces assert_(foo == bar) and failUnless(foo == bar) with
failUnlessEqual(foo, bar). failUnlessEqual shows the value of foo and
bar when they are not equal.
http://www.python.org/sf/175
On 7/10/07, Christian Heimes <[EMAIL PROTECTED]> wrote:
> Guido van Rossum wrote:
> > Please help!
>
> I've made a meta patch that makes debugging the bugs a lot easier. It
> replaces assert_(foo == bar) and failUnless(foo == bar) with
> failUnlessEqual(foo, bar). failUnlessEqual shows the value of
On 09/07/2007 21.23, Walter Dörwald wrote:
> >>> from ll.xist import parsers, xfind
> >>> from ll.xist.ns import html
> >>> e = parsers.parseURL("http://www.python.org";, tidy=True)
> >>> print e.walknode(html.h2 & xfind.hasclass("news"))[-1]
> Google Adds Python Support to Google Calendar Dev
Steven Bethard wrote:
> I'd probably go with something a little more restrictive, maybe:
>
> r'self.assert_\(\S+ == \S+\)'
>
> Something like that ought to have fewer false positives.
Woops! You are right. Even your pattern has caused some false positives
but I've reread the patch and remove
Please use self.assertEqual() instead of self.failUnlessEqual() -- the
assertEqual() form is much more common. Otherwise, good idea!
On 7/11/07, Christian Heimes <[EMAIL PROTECTED]> wrote:
> Steven Bethard wrote:
> > I'd probably go with something a little more restrictive, maybe:
> >
> > r'se
10 matches
Mail list logo
