has wrote:
> On 2 Apr 2007, at 09:21, Jack Jansen wrote:
>
> Yeah, cleaning up APIs and internals and writing good user docs is
> well and truly teh suk as jobs go. Without it though, I think you'll
> have a very tough time convincing others to help share the load.
I'm willing to contribut
On 2 Apr 2007, at 09:21, Jack Jansen wrote:
>> Furthermore, this stumbling block has a stumbling block of its own:
>> bgen. There's very few folk around who understand it at all, and no
>> documentation (AFAIK) for anyone else to make sense of it.
>
> I'm committed to bgen, for at least the next c
On 31-Mar-2007, at 19:58 , has wrote:
Furthermore, this stumbling block has a stumbling block of its own:
bgen. There's very few folk around who understand it at all, and no
documentation (AFAIK) for anyone else to make sense of it. Until
there's some sort of decision made about bgen's future
Ronald Oussoren wrote:
> One thing we (Jack and I) talked about is moving at least the
> Carbon modules to its own separate project instead of being part of
> the standard library. The most important reason for this is that
> the Carbon modules and Python itself should be on a different
>
On 31 Mar, 2007, at 1:49, Jack Jansen wrote:
On 30-Mar-2007, at 22:55 , Kevin Walzer wrote:
Looking at the "Macintosh Library" documentation that ships with
2.5, I
see a lot of outdated stuff: references to the old PythonIDE,
PackageManager, and so on. What is the process for updating the
On 31 Mar, 2007, at 5:41, Dethe Elza wrote:
> On 30-Mar-07, at 4:49 PM, Jack Jansen wrote:
>
>> Carbon itself should be fine. It is indeed undocumented within the
>> Python documentation, but the transformation from the official
>> Apple C documentation is pretty clear (I think).
>
> Is there any
Jack Jansen wrote:
> On 30-Mar-2007, at 22:55 , Kevin Walzer wrote:
>
>> Looking at the "Macintosh Library" documentation that ships with
>> 2.5, I
>> see a lot of outdated stuff: references to the old PythonIDE,
>> PackageManager, and so on. What is the process for updating these
>> docs,
>>
On 30-Mar-07, at 4:49 PM, Jack Jansen wrote:
> Carbon itself should be fine. It is indeed undocumented within the
> Python documentation, but the transformation from the official
> Apple C documentation is pretty clear (I think).
Is there anywhere that this mapping is specified? I've always
On 30-Mar-2007, at 22:55 , Kevin Walzer wrote:
Looking at the "Macintosh Library" documentation that ships with
2.5, I
see a lot of outdated stuff: references to the old PythonIDE,
PackageManager, and so on. What is the process for updating these
docs,
submitting a bug report, etc.?
Also
Looking at the "Macintosh Library" documentation that ships with 2.5, I
see a lot of outdated stuff: references to the old PythonIDE,
PackageManager, and so on. What is the process for updating these docs,
submitting a bug report, etc.?
Also, there appears to be a lot of modules in the "Macinto
10 matches
Mail list logo
