-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Jan 4, 2007, at 2:36 PM, Ronald Oussoren wrote:
> On 4 Jan, 2007, at 17:56, Fred L. Drake, Jr. wrote:
>
>> On Thursday 04 January 2007 11:33, Martin v. Löwis wrote:
>>> For the python subdirectory, there is the issue that the framework
>>> includes
On 4 Jan, 2007, at 17:56, Fred L. Drake, Jr. wrote:
On Thursday 04 January 2007 11:33, Martin v. Löwis wrote:
For the python subdirectory, there is the issue that the framework
includes in OSX magically look for python.framework when searching
for
python/foo.h, which they find, so that may
On Thursday 04 January 2007 11:33, Martin v. Löwis wrote:
> For the python subdirectory, there is the issue that the framework
> includes in OSX magically look for python.framework when searching for
> python/foo.h, which they find, so that may get us the wrong version.
> Somebody would have to
Barry Warsaw schrieb:
> I agree. I don't mind if Python.h is just a wrapper around #includes
> from python/*.h. I think we should add structmember.h and structseq.h
> to Python.h and perhaps move everything else into a 'python' subdirectory.
For the python subdirectory, there is the issue that t
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Jan 4, 2007, at 4:17 AM, Martin v. Löwis wrote:
> As specified, above, it is incompatible with the current API. I think
>
> #include
>
> should be preserved. I personally see no problem with a single header
> file, and would prefer that include to
Neal Norwitz schrieb:
> I'm a Python embedder and I want to know what's available to me. I
> look in Include and see a ton of header files. Do I need all these?
> What do I *need* and what can I *use*? I only want to see the public
> stuff that is available to me. Thus I want anything that has
On 1/3/07, "Martin v. Löwis" <[EMAIL PROTECTED]> wrote:
> Neal Norwitz schrieb:
> > By private, I mean internal only to python and don't need to prefix
> > their identifiers with Py and are subject to change without backwards
> > compatibility. Include/graminit.h is one example of what I mean.
> >
Neal Norwitz schrieb:
> By private, I mean internal only to python and don't need to prefix
> their identifiers with Py and are subject to change without backwards
> compatibility. Include/graminit.h is one example of what I mean.
> Some others are: bitset.h, grammar.h, opcode.h, metagrammar.h,
>
