On 20/11/2007, "Martin v. Löwis" <[EMAIL PROTECTED]> wrote:
> I think the concern is also about shells other than command.com,
> such as 4NT (can you set COMSPEC to the PowerShell?). If you google
> for it, you find that people do use 4NT, and apparently also make
> COMSPEC point to it.
I certainl
On 20/11/2007, Christian Heimes <[EMAIL PROTECTED]> wrote:
> Are we going to drop VS 2003 after the 3.0a2 release and use VS 2008 as
> the default compiler once it has been released, too?
>
> In other words: Do we want to support outdated compilers for legacy
> reasons or can we stick to 2005 as th
Paul Moore wrote:
> On 20/11/2007, Christian Heimes <[EMAIL PROTECTED]> wrote:
> > Are we going to drop VS 2003 after the 3.0a2 release and use VS 2008 as
> > the default compiler once it has been released, too?
> >
> > In other words: Do we want to support outdated compilers for legacy
> > reasons
On 20/11/2007, Amaury Forgeot d'Arc <[EMAIL PROTECTED]> wrote:
> Am I missing something? Should we lift the restrictions we impose on
> compilers of extension modules? Can we carefully design the Python API
> to accept different compilers/runtime?
I have done similar experiments in the past. There
Paul Moore wrote:
> On 20/11/2007, Amaury Forgeot d'Arc <[EMAIL PROTECTED]> wrote:
>> Am I missing something? Should we lift the restrictions we impose on
>> compilers of extension modules? Can we carefully design the Python API
>> to accept different compilers/runtime?
>
> I have done similar exp
On 20/11/2007, Paul Moore <[EMAIL PROTECTED]> wrote:
> PPS I *will* see what the current status of msvcr8/9 support in the
> Mingw project is, but I'm not too hopeful - mingw is currently
> undergoing a change of maintainers and progress has slowed a lot.
Apologies. I had an out of date mingw runt
On 20/11/2007, Nick Coghlan <[EMAIL PROTECTED]> wrote:
> If someone already understands the rules for mixing CRT's and has a
> reason to do it then more power to them (I do it at work all the time
> due to toolset limitations). On the other hand, if someone doesn't
> understand the restrictions, th
Guido van Rossum wrote:
> On Nov 19, 2007 3:06 PM, Amaury Forgeot d'Arc <[EMAIL PROTECTED]> wrote:
>> Guido van Rossum wrote:
>>> Is there anything that you (or anyone else!) would really like to see
>>> added to or fixed in 3.0a2? Now's the time!
>> I am currently having a look at http://bugs.pyth
hi
the new i/o pep (3116) says the following:
> In order to put an object in object in non-blocking mode, the user
> must extract the fileno and do it by hand.
i remember the discussions of the subject, but it seems wrong to me.
there are (only?) two common use cases for async IO: sockets and
pip
> The only question remaining is: do we need the streamreader classes at all.
And if we do, perhaps it simply indicates a limitation of the IO
wrapper classes which should be fixed.
Bill
___
Python-3000 mailing list
Python-3000@python.org
http://mail.py
(top-posting to shorten the reading time)
Note that in 2.5
>>> Eq("b") < Eq("a")
True
Your Eq class didn't define a __lt__, so in 2.5, it inherits the
default method, and ends up (in CPython) looking at the object's
address, so the first-created object will be less. In this case, it
see
Paul Moore wrote:
[snip]
> I will help in addressing this issue, but I am limited in my ability
> to do so, as I cannot build Python itself (that *does* need full VS
> 2005/2008, as I understand it) and so all I have to go with is the
> snapshot builds (which use VS 2003, and so don't help...)
>
>
> Are we going to drop VS 2003 after the 3.0a2 release and use VS 2008 as
> the default compiler once it has been released, too?
Ah, that. I would certainly hope so - although we may see 3.0a3 first,
as VS 2008 is planned for February.
> In other words: Do we want to support outdated compilers fo
> I would strongly advise against going back to the days where a paid MS
> compiler was the only way to build extensions for Windows.
Certainly. If Microsoft follows its recent tradition, they will continue
to publish an "express" version of VS 2008 (and then take the "express"
version of VS 2005
> It seems that the restriction that forces you to use the same compiler
> for core python and extension modules does not stand.
>
> Of course, you cannot do everything: for example, FILE* pointers
> cannot be exchanged between different instances of the C runtime.
I wouldn't call that "it works",
> I believe Martin has always been the strongest advocate of the "CRT
> must match exactly" position (apologies, Martin, if I've
> misremembered). Maybe he could comment.
See my other comment. For the "unwashed masses", this statement (CRT
must absolutely match), is certainly my recommendation. Fo
> If someone already understands the rules for mixing CRT's and has a
> reason to do it then more power to them (I do it at work all the time
> due to toolset limitations). On the other hand, if someone doesn't
> understand the restrictions, then it isn't our (or the c.l.p crowd's)
> job to tea
> I'd be happy enough for the diistutils --compiler=mingw option to
> remain the "free" route, but if that means using msvcr71 (because
> mingw doesn't support msvcr 8 or 9)
I think it's a bit to early to claim that mingw doesn't support
mvcr 9 - that library hasn't even been released yet. When it
> Whether that counts as an argument for sticking with VS 2005, I don't
> know. I doubt it, realistically. But it *may* constitute an argument
> for not going to VS 2008 until it's actually released
Of course, I won't ship any VS 2008 binaries until VS 2008 is released -
not just because of MingW,
> I'm not sure but I strongly believe that the express edition is able to
> build 32bit builds of Python. As far as I know the express edition can't
> build PGO and 64bit builds. Please correct me if I'm wrong.
I haven't actually tried, but it may be that you can build 64-bit
binaries if you also
Martin v. Löwis wrote:
> We keep the build files around for a while in the PC subdirectory.
> Sometimes, people contribute patches to keep them working, and as
> long as there are users, I see no reason to drop the build files.
>
> Python should *definitely* continue to compile with older compiler
On 20/11/2007, Christian Heimes <[EMAIL PROTECTED]> wrote:
> Paul Moore wrote:
> [snip]
> > I will help in addressing this issue, but I am limited in my ability
> > to do so, as I cannot build Python itself (that *does* need full VS
> > 2005/2008, as I understand it) and so all I have to go with is
Paul Moore wrote:
> I fear that without
> some free toolset being an option in distutils, the level of
> availability of Windows binaries will drop again.
I think it's important that some truly free toolset such as
mingw remains an option. In fact I think it's even more important
than the free MS
Martin v. Löwis wrote:
> Of course, I won't ship any VS 2008 binaries until VS 2008 is released -
> not just because of MingW, but also because the license agreement on
> the VS 2008 betas disallows such releases.
Martin,
Not that it changes anything, but VS 2008 it was released today.
Cheers,
S
> Not that it changes anything, but VS 2008 it was released today.
> Cheers,
Nice :)
You can get more information at
http://msdn2.microsoft.com/en-us/vstudio/products/default.aspx
The express edition is available at
http://www.microsoft.com/express/download/
Christian
__
25 matches
Mail list logo
