On 4/24/07, Neal Norwitz <[EMAIL PROTECTED]> wrote:
> On 4/23/07, Yaakov Nemoy <[EMAIL PROTECTED]> wrote:
> > Hi List,
> >
> > i want to post a little bit of something I've been working on. Before
> > I post it, i want to know if I'm allowed to post it as an attachment.
> > Coming up, some work on
On 4/23/07, Yaakov Nemoy <[EMAIL PROTECTED]> wrote:
> Hi List,
>
> i want to post a little bit of something I've been working on. Before
> I post it, i want to know if I'm allowed to post it as an attachment.
> Coming up, some work on ASTVisitor in the compiler module.
Hi Yaakov.
If you'd like t
I posted about this on python-ideas, and didn't get any objections
about the idea itself, so I took the opportunity to dive into the C
API and get my hands dirty. I posted the idea and patch as a report on
SF (1706256). For anyone interested at least to look over, I'm also
just including the small
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Apr 23, 2007, at 8:39 PM, Collin Winter wrote:
> Fast and simple: I want all stdlib test cases to stop subclassing
> unittest.TestCase and start subclassing test_support.TestCase.
>
> So: any objections to making this change?
Please use the absolu
Hi List,
i want to post a little bit of something I've been working on. Before
I post it, i want to know if I'm allowed to post it as an attachment.
Coming up, some work on ASTVisitor in the compiler module.
Cheers,
Yaakov
___
Python-Dev mailing list
P
On 4/23/07, Collin Winter <[EMAIL PROTECTED]> wrote:
> Fast and simple: I want all stdlib test cases to stop subclassing
> unittest.TestCase and start subclassing test_support.TestCase.
Go for it!
n
___
Python-Dev mailing list
Python-Dev@python.org
http
At 04:23 PM 4/23/2007 -0700, Brett Cannon wrote:
>On 4/23/07, Phillip J. Eby <[EMAIL PROTECTED]> wrote:
> > At 03:16 PM 4/23/2007 -0700, Brett Cannon wrote:
> > >The PEP does not explicitly state how to signal that a loader cannot
> > >load a module it is asked to. This could happen if someone cal
Fast and simple: I want all stdlib test cases to stop subclassing
unittest.TestCase and start subclassing test_support.TestCase.
Why: With a single parent class common to the entire stdlib, adding
new functionality/testing instruments to *every single test at once*
becomes trivial. One example wou
On 4/23/07, Phillip J. Eby <[EMAIL PROTECTED]> wrote:
> At 03:16 PM 4/23/2007 -0700, Brett Cannon wrote:
> >The PEP does not explicitly state how to signal that a loader cannot
> >load a module it is asked to. This could happen if someone called a
> >loader without consulting its respective import
At 03:16 PM 4/23/2007 -0700, Brett Cannon wrote:
>The PEP does not explicitly state how to signal that a loader cannot
>load a module it is asked to. This could happen if someone called a
>loader without consulting its respective importer. I would want to
>add something like:
>"""
>If the loader
On 4/23/07, Phillip J. Eby <[EMAIL PROTECTED]> wrote:
> At 02:01 PM 4/23/2007 -0700, Brett Cannon wrote:
> >For PEP 302, a loader should raise ImportError if load_module fails
> >w/o an explicit exception being raised.
>
> I'm not sure I understand this; could you point to the relevant part of the
At 02:01 PM 4/23/2007 -0700, Brett Cannon wrote:
>For PEP 302, a loader should raise ImportError if load_module fails
>w/o an explicit exception being raised.
I'm not sure I understand this; could you point to the relevant part of the
PEP and what you would be adding? Thanks.
(The rest of your
After my import rewrite, I discovered some things that were left out
of both PEP 302 (import hooks) and PEP 328 (absolute/relative
imports). I wanted to run them by everyone before I made the
subsequent changes to the PEPs.
For PEP 302, a loader should raise ImportError if load_module fails
w/o a
Someone should just take down that styleguide, or *replace* it with a
link (and only a link) to PEP 8. I can't do that myself, it's in the
hands of the webmasters.
On 4/23/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> On Mon, Apr 23, 2007 at 09:25:48AM -0700, Brett Cannon wrote:
> > I persona
On Mon, Apr 23, 2007 at 09:25:48AM -0700, Brett Cannon wrote:
> I personally think the style guide should just go and/or redirect to
> PEP 8. I didn't even know it existed until this email. And I only
> know of people updated PEP 8.
The top of the style guide basically does that:
This style g
On 4/23/07, Darren Dale <[EMAIL PROTECTED]> wrote:
> I was recently searching for some guidance on how to name packages and
> modules, and discovered an inconsistency in the style guides published at
> www.python.org. http://www.python.org/doc/essays/styleguide.html
> says "Module names can be eith
I was recently searching for some guidance on how to name packages and
modules, and discovered an inconsistency in the style guides published at
www.python.org. http://www.python.org/doc/essays/styleguide.html
says "Module names can be either MixedCase or lowercase." That
page also refers to PEP 8
OK, here's the patch I'd like to direct attention to:
http://python.org/sf/1704134
[ 1704134 ] minidom Level 1 DOM compliance
This is only the first step toward DOM Level 1 compliance. It fixes
the stuff that's easy to fix.
Here are the patch reviews. I put more detailed comments in the SF
18 matches
Mail list logo
