Hi Fredrik,
On Fri, Oct 13, 2006 at 11:22:09AM +0200, Fredrik Lundh wrote:
> > > static PyTypeObject NoddyType;
> > static PyTypeObject *NoddyType;
>
> yeah, that's a silly typo.
Ah, then ignore my previous remark.
Armin
___
Python-Dev maili
Martin v. Löwis wrote:
> Steve Holden schrieb:
>
The other thing to watch out for is that I (or whoever) can still do local
work on a bunch of different files
>>>
>>>the point of my previous post is that you *shouldn't* have to edit a
>>>bunch of different files to make a new release.
>>
Hello. I noticed VisualC++6 support came back. I'm glad with that, but still
it seems
incomplete. (for example, _sqlite3 support) Maybe does this patch help
process? On
my machine, testcases other than distutils runs fine.
http://sourceforge.net/tracker/?func=detail&aid=1457736&group_id=5470&atid=
On Sunday 15 October 2006 21:23, Steve Holden wrote:
> Martin v. Löwis wrote:
> > Steve Holden schrieb:
> The other thing to watch out for is that I (or whoever) can still do
> local work on a bunch of different files
> >>>
> >>>the point of my previous post is that you *shouldn't* have to
Anthony Baxter schrieb:
> Subsequent release. This is still largely a manual process - I search for all
> the references to the previous release, update them, then read through it for
> missed bits. I then update the text bits that need to be changed. There's all
> sorts of minor variations ther
ocean schrieb:
> Hello. I noticed VisualC++6 support came back. I'm glad with that,
> but still it seems incomplete. (for example, _sqlite3 support) Maybe
> does this patch help process?
These changes were all contributed by Larry Hastings. For some reason,
I missed/forgot about your patch. Can yo
Fredrik Lundh schrieb:
> but given that the format *has* been stable for many years, surely it
> would make more sense to just codify that fact, rather than developing
> Yet Another Serialization Format instead?
There have been minor changes over time, e.g. r26146 (gvanrossum)
introduced TYPE_TR
In Python 2.5.0 and earlier, it is not possible to modify
the time stamps of a directory (mtime and atime) on Windows.
The reason is that you cannot "open" (CreateFile) a
directory.
On W9x, it isn't possible, period. On WNT+, it's possible
if you pass FILE_FLAG_BACKUP_SEMANTICS to CreateFile.
I ju
On Sun, Oct 15, 2006, "Martin v. L?wis" wrote:
>
> Should I backport the patch to 2.5, as it is a bug that you can modify
> the time stamps of regular files but not directories? Or should I
> not backport as it is a new feature that you can now adjust the time
> stamps of a directory, and couldn't
On Sunday 15 October 2006 23:35, Aahz wrote:
> On Sun, Oct 15, 2006, "Martin v. L?wis" wrote:
> > Should I backport the patch to 2.5, as it is a bug that you can modify
> > the time stamps of regular files but not directories? Or should I
> > not backport as it is a new feature that you can now adj
This may be down to my lack of knowledge of Mac OS X development.
I want to build my python extension for Python 2.3, 2.4 and 2.5 on
the same Mac.
Build Python 2.3 and Python 2.4 has been working well for a long
time. But
after I installed Python 2.5 it seems that I can no longer link a
agai
On 10/15/06, Barry Scott <[EMAIL PROTECTED]> wrote:
> This may be down to my lack of knowledge of Mac OS X development.
>
> I want to build my python extension for Python 2.3, 2.4 and 2.5 on
> the same Mac.
> Build Python 2.3 and Python 2.4 has been working well for a long
> time. But
> after I ins
On Oct 15, 2006, at 9:41 PM, Bob Ippolito wrote:
On 10/15/06, Barry Scott <[EMAIL PROTECTED]> wrote:
This may be down to my lack of knowledge of Mac OS X development.
I want to build my python extension for Python 2.3, 2.4 and 2.5 on
the same Mac.
Build Python 2.3 and Python 2.4 has been work
Patch / Bug Summary
___
Patches : 431 open ( +3) / 3425 closed ( +8) / 3856 total (+11)
Bugs: 916 open (-23) / 6273 closed (+44) / 7189 total (+21)
RFE : 244 open ( +4) / 240 closed ( +1) / 484 total ( +5)
New / Reopened Patches
__
typo in P
14 matches
Mail list logo
