On 8 Aug 2013 02:48, "Larry Hastings" wrote:
>
> On 08/05/2013 09:59 PM, Nick Coghlan wrote:
>>>
>>> ___
>>> Question 2: Emit code for modules and classes?
>>>
>>> [...] Originally Clinic didn't ask for full class and module
informati
On 08/05/2013 09:59 PM, Nick Coghlan wrote:
___
Question 2: Emit code for modules and classes?
[...] Originally Clinic didn't ask for full class and module information, you
just
specified the full dotted path and that was that. Bu
On Mon, 05 Aug 2013 16:53:39 -0700
Larry Hastings wrote:
>
> On 08/05/2013 02:55 AM, Nick Coghlan wrote:
> > On 5 August 2013 18:48, Larry Hastings wrote:
> >> Question 0: How should we integrate Clinic into the build process?
> > Isn't solving the bootstrapping problem the reason for checking i
On Tue, Aug 6, 2013 at 12:59 AM, Nick Coghlan wrote:
> On 6 August 2013 09:53, Larry Hastings wrote:
> > On 08/05/2013 02:55 AM, Nick Coghlan wrote:
> > On 5 August 2013 18:48, Larry Hastings wrote:
> >
> > Question 0: How should we integrate Clinic into the build process?
> >
> > Isn't solving
On Mon, 05 Aug 2013 16:53:39 -0700, Larry Hastings wrote:
> Let me put it this way: Which is more surprising to the person
> unfamiliar with the code? That this __init__ doesn't get all the
> parameters, and the base class __init__ is getting called
> automatically? Or that this funny functio
On 6 August 2013 09:53, Larry Hastings wrote:
> On 08/05/2013 02:55 AM, Nick Coghlan wrote:
> On 5 August 2013 18:48, Larry Hastings wrote:
>
> Question 0: How should we integrate Clinic into the build process?
>
> Isn't solving the bootstrapping problem the reason for checking in the
> clinic-ge
On 08/05/2013 02:55 AM, Nick Coghlan wrote:
On 5 August 2013 18:48, Larry Hastings wrote:
Question 0: How should we integrate Clinic into the build process?
Isn't solving the bootstrapping problem the reason for checking in the
clinic-generated output? If there's no Python available, we buil
On 8/5/2013 1:48 AM, Larry Hastings wrote:
The impl should know whether or not it failed. So it's the
interface we're defining that forces it to throw away that
information. If we provided a way for it to return that
information, we could shave off some cycles. The problem
is, how do we do th
On 5 August 2013 18:48, Larry Hastings wrote:
> Question 0: How should we integrate Clinic into the build process?
>
> Clinic presents a catch-22: you want it as part of the build process,
> but it needs Python to be built before it'll run. Currently it
> requires Python 3.3 or newer; it might wo
Hi Larry,
On Mon, Aug 5, 2013 at 10:48 AM, Larry Hastings wrote:
> Question 4: Return converters returning success/failure?
The option generally used elsewhere is: if we throw an exception, we
return some special value; but the special value doesn't necessarily
mean by itself that an exception w
It's time to discuss Argument Clinic again. I think the
implementation is ready for public scrutiny.
(It was actually ready a week ago, but I lost a couple of
days to "make distclean" corrupting my hg data store--yes,
I hadn't upped my local clinic branch in a while. Eventually
I gave up on r
11 matches
Mail list logo
