Hi,
I'm trying to understand Python 3's comparisons.
class Eq:
def __init__(self, x=""):
self.x = x
def __str__(self):
return self.x
def __eq__(self, other):
return str(self) == str(other)
class Lt:
def __init__(self, x=""):
self.x = x
def __st
Right. Building Win98 or ME is insanity.
[double-takes]
Hey! Tim! Long time no see. Welcome back Don't be a stranger. :-)
We missed you.
--Guido
On Nov 15, 2007 5:22 PM, Tim Peters <[EMAIL PROTECTED]> wrote:
> [Paul Moore]
> >>From a quick look, rmpyc.py is deleting .pyc and .pyo files in .
[Paul Moore]
>>From a quick look, rmpyc.py is deleting .pyc and .pyo files in ..\Lib.
> This could be done (I believe) using simply
>
>cd ..\Lib
>del /S *.pyc *.pyo
>
> I haven't tested this (no time right now) but certainly on XP, the del
> command accepts a /S flag to delete recursively.
Today an user named weck has submitted three patches for VS 2005 support
[0]. In one of the replies Martin said that he likes to use the upcoming
VS2008 as new default compiler.
I've downloaded the Beta 2 of VS 2008 from [1] and played with it a bit.
It comes with most tools required to build Pyt
> Now, is it really necessary to install perl in order to compile python?
Yes, if you want OpenSSL support.
> Also note that the openssl distribution proposed in PCBuild8/readme.txt:
> svn export http://svn.python.org/projects/external/openssl-0.9.8a
> does not compile out of the box with vc2005.
On 15/11/2007, Guido van Rossum <[EMAIL PROTECTED]> wrote:
> Ideally, the clean step should not depend on Python existing. On Unix
> it doesn't need it!
>From a quick look, rmpyc.py is deleting .pyc and .pyo files in ..\Lib.
This could be done (I believe) using simply
cd ..\Lib
del /S *.pyc
> Now, is it really necessary to install perl in order to compile python?
This is a Windows thing? You don't need it on Unix systems, I believe.
Bill
___
Python-3000 mailing list
Python-3000@python.org
http://mail.python.org/mailman/listinfo/python-300
Hello,
I just saw the addition of the _ssl module:
http://svn.python.org/view?rev=58989&view=rev
I modified PCBuild8/pcbuild.sln to add the project to the solution file
(by hand: my version of vc2005 also changes everything in the file)
Now, is it really necessary to install perl in order to com
On Nov 15, 2007 12:14 PM, Thomas Heller <[EMAIL PROTECTED]> wrote:
> I'll make the change.
Thanks!
> And, btw: after a manual clean, the win64 buildbot compiles again.
Hm, how about running a cleanup step at the *start* of the build
instead of at the end? (Or at both ends if you want to reclaim
On Nov 15, 2007 1:03 PM, Thomas Heller <[EMAIL PROTECTED]> wrote:
> The *real* problem is that both the build and the clean step require
> Python to work. The former uses it to build _ssl, the latter starts rmpyc.py.
> Since the python30.dll was not built, starting python.exe displays a
> messageb
Guido van Rossum schrieb:
> On Nov 15, 2007 12:14 PM, Thomas Heller <[EMAIL PROTECTED]> wrote:
>> I'll make the change.
>
> Thanks!
>
>> And, btw: after a manual clean, the win64 buildbot compiles again.
>
> Hm, how about running a cleanup step at the *start* of the build
> instead of at the end
Guido van Rossum schrieb:
> On Nov 15, 2007 11:35 AM, Thomas Heller <[EMAIL PROTECTED]> wrote:
>> Guido van Rossum schrieb:
>> > Perhaps changing the remaining occurrences to PyObject_Str will fix this?
>>
>> If PyObject_Unicode is #defined for backwards compatibility then the
>> occurences
>> sho
Guido van Rossum schrieb:
> On Nov 15, 2007 11:22 AM, Thomas Heller <[EMAIL PROTECTED]> wrote:
>> The Win64 buildbot currently fails to link python30.dll and _testcapi.pyd
>> because of an unresolved symbol PyObject_Unicode:
>>
>> http://python.org/dev/buildbot/3.0/amd64%20XP%203.0/builds/242/step-
On Nov 15, 2007 11:35 AM, Thomas Heller <[EMAIL PROTECTED]> wrote:
> Guido van Rossum schrieb:
> > Perhaps changing the remaining occurrences to PyObject_Str will fix this?
>
> If PyObject_Unicode is #defined for backwards compatibility then the
> occurences
> should not be changed, imo.
Even if
On Nov 15, 2007 11:22 AM, Thomas Heller <[EMAIL PROTECTED]> wrote:
> The Win64 buildbot currently fails to link python30.dll and _testcapi.pyd
> because of an unresolved symbol PyObject_Unicode:
>
> http://python.org/dev/buildbot/3.0/amd64%20XP%203.0/builds/242/step-compile/0
>
> Does anyone have a
The Win64 buildbot currently fails to link python30.dll and _testcapi.pyd
because of an unresolved symbol PyObject_Unicode:
http://python.org/dev/buildbot/3.0/amd64%20XP%203.0/builds/242/step-compile/0
Does anyone have an idea why?
Thomas
___
Python-3
Bill Janssen wrote:
> is now on issue 1451.
>
> http://bugs.python.org/file8756/ssl.patch
I'm getting two warnings on Ubuntu 7.10, x86
gcc -pthread -fPIC -fno-strict-aliasing -g -Wall -Wstrict-prototypes -I.
-I/home/heimes/dev/python/py3k/./Include -I./Include -IInclude -I.
-I/usr/local/include
is now on issue 1451.
http://bugs.python.org/file8756/ssl.patch
Bill
___
Python-3000 mailing list
Python-3000@python.org
http://mail.python.org/mailman/listinfo/python-3000
Unsubscribe:
http://mail.python.org/mailman/options/python-3000/archive%40mail-
18 matches
Mail list logo
