Martin v. Löwis wrote:
>> We should also start to discuss how to address some Windows problems.
>> Amaury has brought up some important points and I like to get some
>> feedback on the default compiler topic. Are we going to drop VS 2003
>> after the 3.0a2 release and use VS 2008 as the default com
> We should also start to discuss how to address some Windows problems.
> Amaury has brought up some important points and I like to get some
> feedback on the default compiler topic. Are we going to drop VS 2003
> after the 3.0a2 release and use VS 2008 as the default compiler?
We cannot use that
>> a) changes that apply to 2.6 as well should be done there *first*, and
>>then merged to 3.x (although there are few of them), and
>
> Ah, I've just read PEP11 - and windows9x is indeed officially not
> supported since 2.6.
> However, python 2 must still compile without Py_USING_UNICODE. So
Amaury Forgeot d'Arc wrote:
> command.com does exists on my windows XP box, but is it really used?
> Anyway I will do some tests.
Are people still using 4Dos? :)
Christian
___
Python-3000 mailing list
Python-3000@python.org
http://mail.python.org/mailm
"Martin v. Löwis" wrote:
> > Python 3.0 has already dropped support for Windows 9x in several
> > places, and is now expected to only work with the NT family.
> >
> > I propose to remove the remaining code specific to windows 9x/ME.
> >
> > This includes:
> > - Py_WIN_WIDE_FILENAMES is always defin
On Nov 19, 2007 3:58 PM, Christian Heimes <[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 like to have the bugs w/o priority or high and important priority
> reviewed
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 like to have the bugs w/o priority or high and important priority
reviewed before we release 3.0a2.
http://bugs.python.org/[EMAIL
PROTECTED],id,activity
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.python.org/issue1460 .
> It's
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.python.org/issue1460 .
It's a problem in the utf-7 decoder (there is no such function
PyUnicode_DecodeUTF7Statef
Jeffrey Yasskin wrote:
> For Python, I think I favor reviving __cmp__ for totally ordered
> types, and asking that partially ordered ones return NotImplemented
> from it explicitly.
Returning NotImplemented already means "I don't recognise the other
type". A fully implemented partial ordering is
On Nov 19, 2007 12:47 PM, Christian Heimes <[EMAIL PROTECTED]> wrote:
> Do you have a schedule for the release of the next alpha? If I recall
> correctly the alpha 2 is planed for end of November.
Indeed. I think we can still make that goal; there isn't anything big
that I really want in the relea
> This may well be wrong, since we're supposed to accept Unicode
> everywhere. I don't know why that variable was introduced.
To control running test_pep277. The variable should only be set to true,
if the following strings are all valid file names:
filenames = [
'abc',
'ascii',
'Gr\x
> Python 3.0 has already dropped support for Windows 9x in several
> places, and is now expected to only work with the NT family.
>
> I propose to remove the remaining code specific to windows 9x/ME.
>
> This includes:
> - Py_WIN_WIDE_FILENAMES is always defined
> - when given a unicode string, t
Hi Guido!
Do you have a schedule for the release of the next alpha? If I recall
correctly the alpha 2 is planed for end of November.
Christian
___
Python-3000 mailing list
Python-3000@python.org
http://mail.python.org/mailman/listinfo/python-3000
Unsubs
Next update:
I've done some more work on the PCbuild9 directory. I've removed the
ReleaseAMD64 solution and replaced it with platform x64. I've also taken
some effort to get the 64bit builds of the dependencies ready and
integrate them in the build process.
The openssl package required some hard
Joe Smith wrote:
> Ok. Your nasm workaround is fine, but ML.exe is definately intended to ship
> with VS 2008.
>
> For the record:
> The ml.exe is apparently included in the team edition of the beta, if you
> wanted it, but microsoft has messed up here. Alternatively, one could
> extract versio
On Nov 19, 2007 8:05 AM, Amaury Forgeot d'Arc <[EMAIL PROTECTED]> wrote:
> Another question:
> I noticed that open() and other functions accept bytes objects. Is it
> intended?
> There is no test for this in the test suite. I will add some when I
> know what is needed.
Wasn't intended. We haven't
Hello,
Python 3.0 has already dropped support for Windows 9x in several
places, and is now expected to only work with the NT family.
I propose to remove the remaining code specific to windows 9x/ME.
This includes:
- Py_WIN_WIDE_FILENAMES is always defined
- when given a unicode string, try to al
On 11/17/07, Greg Ewing <[EMAIL PROTECTED]> wrote:
> Martin v. Löwis wrote:
> > or __cmp__ would
> > have to be extended to support "unordered" as a result.
>
> That's what I think should be done.
Note that this would make it slightly easier to pass a custom sort
function that forced everything to
" A team leader exists (Brett Cannon), a seed for a plan exists (PEP
3108) and the mailing list is [EMAIL PROTECTED] Don't be shy!!!
- Guido van Rossum "
I read this, so I'm not being shy, and posted some Python generated
visual thoughts on the sorts of things Python needs in its libraries
one day
20 matches
Mail list logo
