"Martin v. Löwis" <[EMAIL PROTECTED]> writes:
> Can you elaborate? To me, that problem only originates from
> the OS lack of support for deleting open files. If you could
> delete a shared libary that is still in use (as you can on
> Unix), the put the new version of the DLL in the place, (...)
N
"Robin Becker" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]
> Cameron Laird wrote:
> There was no rational reason
> for me to upgrade to VC 7.x, but now I'm forced to by my preferred
language.
> --
> Robin Becker
That's the way I feel about it too. Actually, I'm getting pushed to
Cameron Laird wrote:
Part of the trick is that it demands deep understanding
to detect the antisynergies that arise from the interac-
tions of the DLL, registry, and filesystem schemes. I
know it was only this year that I realized the whole
installation-requires-reboot absurdity is a consequence
o
Jive wrote:
But it makes no difference, no? The problem is that both Python.exe and the
extensions are *compiled* to link with a *particular* crt.
No, that is not (really) the case. They are compiled to link with
msvcrt.lib, which could, at link time, then become msvcrt.dll,
msvcrt40.dll, or msvc
Cameron Laird wrote:
.
.
Part of the trick is that it demands deep understanding
to detect the antisynergies that arise from the interac-
tions of the DLL, registry, and filesystem schemes. I
know it was only this year that I realized the whole
installation-requires-reb
"Martin v. Löwis" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]
> It's not hard-coded in the linker, but hard-coded in the import library.
> So if you link with msvcrt.lib (which might not be the precise name
> of the import library - I cannot look up the precise name right now),
> m
In article <[EMAIL PROTECTED]>,
Jive <[EMAIL PROTECTED]> wrote:
.
.
.
>Bit by bit, I am remembering now just how stupifyingly brain-dead the MS DLL
>scheme is.
.
.
"Cameron Laird" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]
> Tcl went through this epiphany a few years, and has largely,
> though not exclusively, committed to use of the once-more-
> redirected API called Stubs http://wiki.tcl.tk/stubs >.
> Some Tcl-ers are orgasmic about the wo
In article <[EMAIL PROTECTED]>,
Jive <[EMAIL PROTECTED]> wrote:
.
.
.
>Doesn't Microsoft have an answer for that? There are (at last count) nine
>skillion ActiveX
>components in the wild. Surely Microsoft didn't blast them in
In article <[EMAIL PROTECTED]>,
John Machin <[EMAIL PROTECTED]> wrote:
>Jive wrote:
>> "Martin v. Löwis" <[EMAIL PROTECTED]> wrote in message
>> news:[EMAIL PROTECTED]
>> > OTOH, people who only have VC6 just need to buy VS.NET 2003,
>> > which is still available.
>>
>> I don't even know how to do
In article <[EMAIL PROTECTED]>,
Nick Coghlan <[EMAIL PROTECTED]> wrote:
>Jive wrote:
>> Can someone explain to me why Python 2.4 on MS Windows has these backward
>> compatibility problems? What am I missing?
>
>The problem is the Python C/API. At the moment, it exposes things
>directly (like
>da
Jive wrote:
Well, ain't that enough to gag a maggot? I was aware that DLL's don't
really link dynamically. I was not aware that the crt dll file name was
hard-coded into the linker. But I looked on the link line and, sure enough,
that particular dll was not listed among the others.
It's not hard
"Martin v. Löwis" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]
> Jive wrote:
> >>Either VS.NET 2003 or VC++ .NET 2003 should do (although I don't know
> >>anybody who owns the latter to be sure). The core issue is that it needs
> >>a "native" C++ compiler (ie. not just managed C++),
Jive wrote:
Either VS.NET 2003 or VC++ .NET 2003 should do (although I don't know
anybody who owns the latter to be sure). The core issue is that it needs
a "native" C++ compiler (ie. not just managed C++), and that it needs
mscvcr71.dll.
Sorry if I'm being dense. If I had that DLL, why couldn't
"Martin v. Löwis" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]
> Either VS.NET 2003 or VC++ .NET 2003 should do (although I don't know
> anybody who owns the latter to be sure). The core issue is that it needs
> a "native" C++ compiler (ie. not just managed C++), and that it needs
>
Jive wrote:
I don't even know how to do that! :-) What's the difference between VC++
.net Standard and Visual Studio .net Pro? (Besides $370?) Is the former
C++ only, but with the IDE, and the later the whole shebang with SourceSafe,
VBASIC, and all that?
According to
http://msdn.microsoft.com/h
On Sat, 11 Dec 2004 01:28:45 -0600, Mike Meyer wrote:
> Actually, there's a problem on Unix that may not exist on
> Windows. Python is installed in /lib/python/. This
> lets us have multiple versions of Python installed at the same time,
> which is a good thing.
> ...
> The real solution is...
Int
It's me wrote:
My answer is simple: If there are more then 24 hours to a day, I definitely
would...
Can we get a patch in for this?
>>> datetime.timedelta(hours=24) + datetime.timedelta(hours=1)
datetime.timedelta(1)
would be much preferable to the current:
>>> datetime.timedelta(hours=24) + dateti
On the other hand, it can be annoying.
I can't use Python 2.4 right now because NumPy won't run. So, I need to
wait for NumPy to get updated.
Of course, one would say: but NumPy is open source, go build it yourself.
My answer is simple: If there are more then 24 hours to a day, I definitely
wou
Jive wrote:
> "Martin v. Löwis" <[EMAIL PROTECTED]> wrote in message
> news:[EMAIL PROTECTED]
> > OTOH, people who only have VC6 just need to buy VS.NET 2003,
> > which is still available.
>
> I don't even know how to do that! :-) What's the difference between
VC++
> .net Standard and Visual Studi
"Martin v. Löwis" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]
> OTOH, people who only have VC6 just need to buy VS.NET 2003,
> which is still available.
I don't even know how to do that! :-) What's the difference between VC++
.net Standard and Visual Studio .net Pro? (Besides $3
Jive wrote:
The other
issue is that the interpreter and the extensions may be linked to
different versions of the Microsoft runtime.
Doesn't Microsoft have an answer for that?
Microsoft's answer to this question is: don't do that. Never
mix different versions of the CRT in a single application.
Th
Jive wrote:
Why won't extensions compiled to run with 2.3 also work with 2.4?
I believe nobody has answered *this* question, yet:
Python extensions built for 2.3 link with python23.dll, Python
extensions build for 2.4 link with python24.dll.
pythonxy.dll has global variables, e.g. the pointers to
"Jive" <[EMAIL PROTECTED]> writes:
> "Nick Coghlan" <[EMAIL PROTECTED]> wrote in message
> news:[EMAIL PROTECTED]
>> To this date, no-one has cared enough about the problem to put in the
> effort
>> required to make the C API version agnostic. Given that the API almost
> always
>> remains *source*
Jive schreef:
> P.s. Does anyone know how to make Outlook Express leave my damned
> line-ends alone? If I want line-ends. I know where to find the ENTER
> key.
Google for "oe-quotefix", but the best solution is to use a proper
newsreader. ;-)
--
JanC
"Be strict when sending and tolerant
P.s. Does anyone know how to make Outlook Express leave my damned line-ends
alone? If I want line-ends. I know where to find the ENTER key.
--
http://mail.python.org/mailman/listinfo/python-list
"Nick Coghlan" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]
> Jive wrote:
> > Can someone explain to me why Python 2.4 on MS Windows has these
backward
> > compatibility problems? What am I missing?
>
> The problem is the Python C/API. At the moment, it exposes things directly
(lik
Jive wrote:
Can someone explain to me why Python 2.4 on MS Windows has these backward
compatibility problems? What am I missing?
The problem is the Python C/API. At the moment, it exposes things directly (like
data structures) that may change size between major version releases. The other
issue
Hi !
But, if Python is as much sensitive to the passage of an external software,
version 6 (obsolete) with a version 7 (obsolete also), it is worrying.
Michel Claveau
--
http://mail.python.org/mailman/listinfo/python-list
VS7 is a really a vastly different beastie than VS6.
On 12/10/04 9:31 PM, in article [EMAIL PROTECTED],
"Jive" <[EMAIL PROTECTED]> wrote:
> Can someone explain to me why Python 2.4 on MS Windows has these backward
> compatibility problems? What am I missing? Why won't extensions compiled
> to
Can someone explain to me why Python 2.4 on MS Windows has these backward
compatibility problems? What am I missing? Why won't extensions compiled
to run with 2.3 also work with 2.4? Why does it matter whether a component
was compiled with VC++ 6.0 or 7.1? I've been using MS stuff for 6 years.
31 matches
Mail list logo
