You can subscribe to this list here.
2001 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(39) |
---|---|---|---|---|---|---|---|---|---|---|---|---|
2002 |
Jan
(37) |
Feb
(35) |
Mar
(23) |
Apr
(14) |
May
(2) |
Jun
(7) |
Jul
|
Aug
(5) |
Sep
(10) |
Oct
|
Nov
(4) |
Dec
|
2003 |
Jan
(5) |
Feb
(5) |
Mar
(2) |
Apr
|
May
(7) |
Jun
(8) |
Jul
(16) |
Aug
(8) |
Sep
(15) |
Oct
(4) |
Nov
|
Dec
(3) |
2004 |
Jan
|
Feb
|
Mar
(1) |
Apr
(3) |
May
(2) |
Jun
(12) |
Jul
(8) |
Aug
(13) |
Sep
|
Oct
(9) |
Nov
|
Dec
(1) |
2005 |
Jan
(2) |
Feb
|
Mar
(6) |
Apr
(1) |
May
|
Jun
|
Jul
(1) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2006 |
Jan
(1) |
Feb
(2) |
Mar
(2) |
Apr
(1) |
May
(3) |
Jun
(2) |
Jul
(3) |
Aug
(1) |
Sep
|
Oct
(4) |
Nov
(11) |
Dec
(20) |
2007 |
Jan
(11) |
Feb
|
Mar
|
Apr
|
May
(1) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2009 |
Jan
(1) |
Feb
(1) |
Mar
(5) |
Apr
(4) |
May
(6) |
Jun
|
Jul
(25) |
Aug
|
Sep
(2) |
Oct
|
Nov
|
Dec
|
2010 |
Jan
|
Feb
|
Mar
|
Apr
(1) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
From: friendDigg <glh...@op...> - 2006-12-05 11:26:44
|
68794 |
From: Armin R. <ar...@tu...> - 2006-11-29 02:52:31
|
Hi Jon, hi all, On Tue, Nov 28, 2006 at 09:20:15PM +0000, Jon Foster wrote: > The file you've got is corrupt. Resending - see attachment. Thanks Jon for this update to the Win32 installer. Sorry all for the trouble, the updated version now replaces the broken one on SourceForge's dowload page at http://sourceforge.net/project/showfiles.php?group_id=41036 For reference the md5 of the file should be: > '14194043a1488c7a33ad7f4ba7c2171c' A bientot, Armin |
From: Armin R. <ar...@tu...> - 2006-11-27 19:41:50
|
Hi Philip, On Sun, Nov 26, 2006 at 08:52:57AM -0000, Philip Smith wrote: > The win32 installer for above version appears to be broken - I have > downloaded from several different mirrors. Have others reported this? Yes, you are the 2nd person reporting this. I have asked the provider of the installer to check if his upload is not corrupted... A bientot, Armin |
From: Alberto Di M. <Alb...@ce...> - 2006-11-22 22:48:13
|
Hi Armin, thanks for the suggestion. It works fine. And I must say the result is pretty amazing. I had some code that was taking several minutes to complete and with Psyco takes a few seconds. Incredible. For the moment I can probably include a patched copy of traceback.py with my code, but let me know if you manage to push a fix into Psyco. Merci beaucoup! Alberto > -----Original Message----- > From: Armin Rigo [mailto:ar...@tu...] > Sent: Wednesday, 22 November 2006 22:37 > To: Alberto Di Meglio > Cc: psy...@li... > Subject: Re: [Psyco-devel] Psyco and log4py in the same module > > Hi, > > On Wed, Nov 22, 2006 at 02:01:08PM +0100, Alberto Di Meglio wrote: > > is it possible to use psyco and log4py together? If psyco is used, > > log4py has problems. To exemplify, the following pretty dumb code > > produces an exception in log4py: > > Thanks for the note. I didn't notice so far that the > traceback.py module of the standard library uses a strange > old way to access the current frame stack. I need to look > more, but it's possible that there would be a way for Psyco > to support that; in the meantime you can patch traceback.py > to replace the 3 occurrences of code like: > > try: > raise ZeroDivisionError > except ZeroDivisionError: > f = sys.exc_info()[2].tb_frame.f_back > > with: > > f = sys._getframe(1) > > which Psyco (mostly) supports. I also realized that the > frame-related problems seem to be the main reason why pdb > doesn't work with Psyco. I think it should be possible for > me to fix this too... > > > A bientot, > > Armin > |
From: Armin R. <ar...@tu...> - 2006-11-22 21:34:37
|
Hi, On Wed, Nov 22, 2006 at 02:01:08PM +0100, Alberto Di Meglio wrote: > is it possible to use psyco and log4py together? If psyco is used, log4py > has problems. To exemplify, the following pretty dumb code produces an > exception in log4py: Thanks for the note. I didn't notice so far that the traceback.py module of the standard library uses a strange old way to access the current frame stack. I need to look more, but it's possible that there would be a way for Psyco to support that; in the meantime you can patch traceback.py to replace the 3 occurrences of code like: try: raise ZeroDivisionError except ZeroDivisionError: f = sys.exc_info()[2].tb_frame.f_back with: f = sys._getframe(1) which Psyco (mostly) supports. I also realized that the frame-related problems seem to be the main reason why pdb doesn't work with Psyco. I think it should be possible for me to fix this too... A bientot, Armin |
From: Alberto Di M. <Alb...@ce...> - 2006-11-22 13:02:21
|
Hi, is it possible to use psyco and log4py together? If psyco is used, log4py has problems. To exemplify, the following pretty dumb code produces an exception in log4py: --------------------- import psyco import log4py psyco.full() logger = log4py.Logger() logger.info('got here') ------------------- [glbuild@lxb2072 glite]$ python psyco-test.py Traceback (most recent call last): File "psyco-test.py", line 8, in ? logger.info('got here') File "/tmp/repository/externals/log4py/1.3.0/noarch/log4py-1.3/log4py.py", line 355, in info self.__Logger_showmessage(message, MSG_INFO) File "/tmp/repository/externals/log4py/1.3.0/noarch/log4py-1.3/log4py.py", line 482, in __Logger_showmessage self.__Logger_tracestack() File "/tmp/repository/externals/log4py/1.3.0/noarch/log4py-1.3/log4py.py", line 366, in __Logger_tracestack self.__Logger_module = stack[-4][0] IndexError: list index out of range ----------------- I'm using psyco 1.5.2 and log4py 1.3 Thanks, Alberto |
From: Armin R. <ar...@tu...> - 2006-11-07 01:44:21
|
Hi Pete, On Mon, Nov 06, 2006 at 08:33:33AM -0800, Pete Shinners wrote: > Is there an easy way to test if a function is wrapped by a psyco? > Since the function attrs get modified in place, it looks like more than > a simple isinstance()? > Given a psyco'd function, is there a way to get at the original > func_code object? Yes, there is an (internal) function that you can use to check if a function's func_code was wrapped by Psyco, and retrieve a function object that looks like the original one: >>> help(psyco._psyco.unproxycode) Help on built-in function unproxycode in module psyco._psyco: unproxycode(...) unproxycode(code) -> function object Return a new copy of the original function that was used to build the given proxy code object. Raise psyco.error if code is not a proxy. A bientot, Armin |
From: Pete S. <pe...@sh...> - 2006-11-06 16:33:30
|
Two questions. Is there an easy way to test if a function is wrapped by a psyco? Since the function attrs get modified in place, it looks like more than a simple isinstance()? Given a psyco'd function, is there a way to get at the original func_code object? |
From: Pete S. <pe...@sh...> - 2006-11-06 16:25:27
|
Two questions. Is there an easy way to test if a function is wrapped by a psyco proxy? Since this function attrs get modified in place, it looks like more than a simple isinstance() Given a psyco proxied function, is there a way to get at the original func_code object? |
From: Simone V. <tjn...@ba...> - 2006-10-24 08:26:03
|
The only thing to do in tuesday is to get in on EQTD. It will RISE up next days. There will be at least 100% appreciation within the first few hours, so do it fast . With oil markets retreating, big traders are turning to gold, driving it to levels never before seen. EQTD has made an advertisement of staggering proportions related to a recent survey on one of their gold ownership. The inside scoop is that we will be looking at a quadrupling of share price once the public takes notice: CHICAGO, ILLINOIS-(MARKETWIRE)-Oct 23, 2006 - Equal trading is pleased to announce announcement results which have far exceeded expectations. The results from our British Columbia property show 58,000 ounce potential. Plans are already underway for pressing development. We look forward to this remarkable discovery bringing value to our stockholder. At 600$ an ounce this discovery is worth 34.8 mil$. With 865mil shares outstanding, this would give us a book value of 0.04 (last price is under 1 cent). Don't miss this one. The value and the opportunity are there. Nowadays is the lowest price it can be. It's high time to buy in! The profitable moment to invest! Good PR will help you to sell it with higher price later. |
From: <koi...@ez...> - 2006-10-23 15:53:22
|
突然すみません。竹中 眞子と申します。結婚して12年未だに子供が出来ません。何かにつけてその事に関して姑にいやみを言われます、しかも夫は外に女がいるようで最近はほとんど相手にしてくれません。そこで、どなたか私に精子を提供してくださいませんでしょうか?中だしで構いません。お礼もさせていただきます。一切ご迷惑はお掛けしません。子供さえ出来れば全てうまくいくと思うんです。 No,278392に電話番号を載せましたの、連絡下さい。どうか宜しくお願いします。 http://vlzh.com/?nh05 |
From: Phil E. <id...@ba...> - 2006-10-23 07:30:09
|
The great anticipations are drawn up. The increase is up to 70% lately. (MXXR) is the gainful deal and those who knows it is making money. The drilling results of this highly capable oil company exceeded all its expectations. Once this fact hits the street there will be no stopping this one. today it's around 0.022 but we are expecting it to triple. Once the announcement is made and the PR gets into full brandish. Don't lose moment and miss out. We counsel you to buy today. The key is getting in early and the time is pressing. They say that Monday is the day this one will blast off. Take your place before that happens. |
From: <psy...@ps...> - 2006-08-29 20:42:06
|
Psycowin agradece su interés en nuestros productos y servicios. En breve, uno de nuestros ejecutivos estará en contacto para atender sus requerimientos. Le recordamos que también contamos con servicios de consultoria en Recursos Humanos como: * Diseño organizacional * Diagnóstico de clima laboral * Evaluación multidimensional 360 * Capacitación en psicometría y competencias * Outsourcing de Reclutamiento y Selección para el noreste del país PSW Global Solutions SA de CV +52 (81) 1158 5900 www.psycowin.com |
From: <psy...@ps...> - 2006-07-28 01:55:58
|
The message you sent requires that you verify that you are a real live human being and not a spam source. To complete this verification, simply reply to this message and leave the subject line intact. The headers of the message sent from your address are show below: >From psy...@li... Wed Jul 26 02:22:15 2006 Received: from brenox by server2.aquabeam.com.br with local-bsmtp (Exim 4.52) id 1G5bqT-0004fw-JT for psy...@ps...; Wed, 26 Jul 2006 02:22:14 -0300 Received: from localhost by server2.aquabeam.com.br with SpamAssassin (version 3.1.3); Wed, 26 Jul 2006 02:22:14 -0300 From: "psy...@li..." <psy...@li...> To: psy...@ps... Subject: [SPAM] Changing careers but lack the right Degree? Date: Wed, 26 Jul 2006 20:19:07 -0300 Message-Id: qt5...@li... X-Spam-Flag: YES X-Spam-Checker-Version: SpamAssassin 3.1.3 (2006-06-01) on server2.aquabeam.com.br X-Spam-Level: ******************* X-Spam-Status: Yes, score=19.5 required=5.0 tests=BAYES_99,FORGED_RCVD_HELO, HTML_40_50,HTML_MESSAGE,HTML_MIME_NO_HTML_TAG,INVALID_MSGID, MIME_HTML_ONLY,RCVD_IN_BL_SPAMCOP_NET,RCVD_IN_NJABL_DUL, RCVD_IN_WHOIS_BOGONS,RCVD_IN_WHOIS_INVALID,RCVD_IN_XBL, UNPARSEABLE_RELAY,UPPERCASE_25_50 autolearn=spam version=3.1.3 MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----------=_44C6FC06.13459B9D" |
From: Armin R. <ar...@tu...> - 2006-07-06 10:47:14
|
Hi, On Wed, Jul 05, 2006 at 12:02:55AM -0400, Jeffrey O'Neill wrote: > ppp.sort(lambda a, b: cmp(total[b], total[a])) This line is the problem (or one of them, possibly). The lambda is based on accessing the 'total' variable from the parent function's scope. It makes whole parent function un-Psyco-ifiable. Try: ppp.sort(lambda a, b, total=total: cmp(total[b], total[a])) Note that the sort itself will be rather slow in psyco.full() mode. A bientot, Armin |
From: Jeffrey O'N. <jc...@co...> - 2006-07-05 04:02:57
|
Dear List, My attempts to use psyco have been very succesful, and most of my code has seen 2-4 times speed improvement. One stubborn section, however, doesn't improve much: 22 seconds without psyco and 20 seconds with psyco. I was wondering if anyone would mind eyeballing the code below to see if anything strikes you as being the culprit. Whatever is causing the problem is probably in the snippet below as all the functions called are used in other places and do not cause problems. I ran the python profiler both with and without psyco. With both the methods below, mostLast() and Count(), there was only marginal improvement with psyco. best regards, Jeff O'Neill ################################################################## class Coombs(Election): """Conduct an election with the Coombs method. Coombs is like IRV except that the candidate receiving the most last place votes is eliminated at each round. Coombs has no options.""" def __init__(self, b, title="", verbose=1, breakTies="random"): Election.__init__(self, b, title, verbose, breakTies) self.method = "Coombs" self.dispPrec = 0 ### def mostLast(self): # Count last place votes per candidate total = [0] * self.b.nCand for i in range(len(self.b.packed)): nUnranked = len(self.unranked[i]) # If no unranked cands, last place candidate gets the vote if nUnranked == 0: ballot = self.b.packed[i][:] ballot.reverse() for c in ballot: if c in self.purgatory: break total[c] += self.b.weight[i] # Otherwise unranked cands share the last place vote else: share = 1.0 * self.b.weight[i] / nUnranked for c in self.unranked[i]: total[c] += share for c in self.purgatory: self.msg[-1] += "Candidate %s has %f last place votes.\n" % (self.b.name[c], total[c]) # Resolve ties ppp = self.purgatory[:] ppp.sort(lambda a, b: cmp(total[b], total[a])) c0 = ppp[0] numTied = total.count(total[c0]) if numTied > 1: c0 = self.strongTieBreak(ppp[:numTied]) # Update data structures for i in range(len(self.b.packed)): if c0 in self.unranked[i]: self.unranked[i].remove(c0) return c0 ### def Count(self): "Does a Coombs election." if not self.minRequirements(): return False self.printBegin() self.count.append([0] * self.b.nCand) self.exhausted.append(0) # Create data structures for speeding up mostLast() self.unranked = [] for i in range(len(self.b.packed)): self.unranked.append([]) for c in self.purgatory: if c in self.b.packed[i]: continue self.unranked[i].append(c) # Count first place votes. for i in range(len(self.b.packed)): c = self.topChoice(self.b.packed[i], self.purgatory) if c == None: self.exhausted[0] += self.b.weight[i] else: self.votes[c].append(i) self.count[0][c] += self.b.weight[i] self.msg.append("Count of first place rankings.\n") self.printRound(0) # Sequentially eliminate candidates with most last place votes while (not self.electionOver()): self.r += 1 self.msg.append("") self.action.append(("eliminate", [])) # Get candidate with most last place votes c0 = self.mostLast() self.newLoser(c0) # Transfer that candidate's votes to their next choices self.count.append(self.count[-1][:]) self.exhausted.append(self.exhausted[-1]) for i in self.votes[c0]: c = self.topChoice(self.b.packed[i], self.purgatory) if c == None: self.exhausted[-1] += self.b.weight[i] else: self.votes[c].append(i) self.count[-1][c] += self.b.weight[i] self.votes[c0] = [] self.count[-1][c0] = 0 self.printRound(self.r) self.nRounds = self.r + 1 self.printEnd() |
From: Armin R. <ar...@tu...> - 2006-06-20 20:24:21
|
Hi Alexandre, On Mon, Jun 19, 2006 at 10:52:04AM +0200, Alexandre Fayolle wrote: > Maybe you could ask/suggest Armin a amd64 port. If it's only about > compiling issues on that plattform I could help but otherwise I > couldn't. That's unlikely to be ever done, by myself or someone else, as I explain at http://psyco.sf.net/ (24th Sep 2005 entry). A bientot, Armin |
From: Alexandre F. <afa...@de...> - 2006-06-19 08:51:12
|
Hello everyone, I'm forwarding a request I received as maintainer for Psyco in Debian.=20 ----- Forwarded message from Andr=E9 W=F6bbeking <Woe...@we...> ----- =46rom: Andr=E9 W=F6bbeking <Woe...@we...> X-Spambayes-Classification: ham; 0.00 To: Alexandre Fayolle <afa...@de...> Date: Mon, 19 Jun 2006 10:15:19 +0200 Subject: Accepted psyco 1.5-3 (source i386) Hi Alexandre, thanks for your very detailed answer! On Wednesday 14 June 2006 13:32, Alexandre Fayolle wrote: > On Wed, Jun 14, 2006 at 01:08:21PM +0200, Andr=E9 W=F6bbeking wrote: > > Hi Alexandre, > > Hi Andr=E9 > > > is there any chance for an amd64 package? > > To my best knowledge, amd64 is not supported upstream, and I do not > have the knowledge nor the time to port psyco to amd64.=20 me neither :-( > I think it is=20 > possible to use psyco on an amd64 box, but you need to compile python > in 32bit mode, which is not the case for the interpreter shipped in > Debian, as far as I know. > > Now, if you have time and knowledge, and can come up with a patch, > I'll be sure to integrate it and push it to Armin Rigo (upstream) who > is a very nice chap and will certainly accept the patch, and may even > help you come up with one. You may also consider sponsoring him, if > amd64 support is important to you or your company, although he is > currenlty very busy working on the Pypy project. > > I'm sorry not to be able to be more helpful on this. I used it on i386 to compile KDE with unsermake and was impressed about=20 the speedup and was just missing it on amd64. Maybe you could ask/suggest Armin a amd64 port. If it's only about=20 compiling issues on that plattform I could help but otherwise I=20 couldn't. Cheers, Andr=E9 ----- End forwarded message ----- --=20 Alexandre Fayolle LOGILAB, Paris (France) Formations Python, Zope, Plone, Debian: http://www.logilab.fr/formations D=E9veloppement logiciel sur mesure: http://www.logilab.fr/services Informatique scientifique: http://www.logilab.fr/science |
From: Armin R. <ar...@tu...> - 2006-05-03 07:15:16
|
Hi John, On Wed, May 03, 2006 at 09:02:07AM +1000, John Machin wrote: > Does this mean that psyco is not tested on Windows? No, I've tested it with Python 2.4. I distribute this binary on the web site too. > >important note: on Windows you have to compile extension modules with > >the same compiler as the one that compiled the Python DLL itself. > > Here's a tip: don't believe everything you read on the Internet. Yes, I know more precisely what will or will not work if you mix compilers. As for whether Psyco will work if you do that, I have no clue: Psyco in general is using quite a number of tricks and depends on quite a number of very precise details, so I definitely recommend care :-) > In file included from C:/python21/Include/Python.h:24, > from c/psyco.h:9, > from c/psyco.c:1: > C:/python21/Include/config.h:293: error: conflicting types for 'intptr_t' > c:/MinGw/bin/../lib/gcc/mingw32/3.4.5/../../../../include/stdint.h:60: > error: previous declaration of 'intptr_t' was here > C:/python21/Include/config.h:294: error: conflicting types for 'uintptr_t' > c:/MinGw/bin/../lib/gcc/mingw32/3.4.5/../../../../include/stdint.h:61: > error: previous declaration of 'uintptr_t' was here Looks like all Python extension modules would have the same problem on migwg32 with Python 2.1. As I said I cannot be of any help here, but I'm sure the problem is reported somewhere (google...). A bientot, Armin. |
From: John M. <sjm...@le...> - 2006-05-02 23:02:21
|
On 3/05/2006 7:52 AM, Armin Rigo wrote: > Hi John, > > On Mon, May 01, 2006 at 07:27:37AM +1000, John Machin wrote: >> Is it a reasonable expectation that I should be able to do a "setup.py >> build_ext -i" using the Borland compiler? Alternatively, how can I >> acquire the 5 binaries? > > I have no experience with the various C compilers for Windows, apart > from the fact that they seem prone to internal limits, against which I > don't feel like fighting too much. Does this mean that psyco is not tested on Windows? > You could try a few tricks like > splitting the expressions; no idea if it helps, and indeed what > precisely is "too long". It turns out that "too long" means > 4096 bytes. > > There is a free compiler from Microsoft which compiles Psyco. Yes, and I understand that setting it up involves massive downloads and many arcane incantations :-( > An > important note: on Windows you have to compile extension modules with > the same compiler as the one that compiled the Python DLL itself. Here's a tip: don't believe everything you read on the Internet. As an *unqualifed* statement it is [trying to keep myself polite here] utterly incorrect. On *ANY* operating system, if you do something silly like open() a file with one runtime and read() it with another, or malloc() with one runtime and free() with another, you will deservedly crash. Both the Borland and MinGW compilers can be used quite successfully to compile most sensibly-written extensions on Windows. I have been doing this for years, including before distutils came out. See http://docs.python.org/dev/inst/tweak-flags.html#SECTION000620000000000000000 AFAIR, any problems have been due to my own stupidity and easily corrected once they manifested. See also below. It is *not* necessary to bow down, either in the house of Rimmon or in the house of Redmond. Resistance is *not* futile. > You > can recompile your own Python DLL, of course, but the one distributed on > python.org was compiled as follows: for Python <= 2.3 it's some older > Visual C++ and for Python >= 2.4 it's a Visual C++ with which this free > compiler is compatible. > > I cannot provide more assistance in getting hold of Windows binaries, > sorry... I hope this helps. After nudging by Clemens Eisserer on this mailing list, I have set myself up to be able to compile Python extensions with MinGW for Python versions 2.1 to 2.5 inclusive. Results with psyco: for versions 2.2 to 2.5 inclusive, doing "setup.py install" proceeds OK with a couple of warnings, and *preliminary* indications are that it is working OK. With 2.1, it firstly says: *** NOTE: it is recommended to use Psyco with Python 2.2.2 or above *** then later there are two conflicting declaration errors: In file included from C:/python21/Include/Python.h:24, from c/psyco.h:9, from c/psyco.c:1: C:/python21/Include/config.h:293: error: conflicting types for 'intptr_t' c:/MinGw/bin/../lib/gcc/mingw32/3.4.5/../../../../include/stdint.h:60: error: previous declaration of 'intptr_t' was here C:/python21/Include/config.h:294: error: conflicting types for 'uintptr_t' c:/MinGw/bin/../lib/gcc/mingw32/3.4.5/../../../../include/stdint.h:61: error: previous declaration of 'uintptr_t' was here I am strongly inclined to follow the recommendation, rather than trying to sort out conflicts between stdint.h and an antique Python.h :-) Cheers, John |
From: Armin R. <ar...@tu...> - 2006-05-02 21:51:39
|
Hi John, On Mon, May 01, 2006 at 07:27:37AM +1000, John Machin wrote: > Is it a reasonable expectation that I should be able to do a "setup.py > build_ext -i" using the Borland compiler? Alternatively, how can I > acquire the 5 binaries? I have no experience with the various C compilers for Windows, apart from the fact that they seem prone to internal limits, against which I don't feel like fighting too much. You could try a few tricks like splitting the expressions; no idea if it helps, and indeed what precisely is "too long". There is a free compiler from Microsoft which compiles Psyco. An important note: on Windows you have to compile extension modules with the same compiler as the one that compiled the Python DLL itself. You can recompile your own Python DLL, of course, but the one distributed on python.org was compiled as follows: for Python <= 2.3 it's some older Visual C++ and for Python >= 2.4 it's a Visual C++ with which this free compiler is compatible. I cannot provide more assistance in getting hold of Windows binaries, sorry... I hope this helps. A bientot, Armin |
From: John M. <sjm...@le...> - 2006-04-30 21:27:45
|
Hello, I'm interested in getting Windows binaries for Psyco 1.5.1 for each Python version 2.1 to 2.5 inclusive. [Background: I support a pure-Python module for extracting data from Microsoft Excel files (see "xlrd" in the Cheese Shop). It works on Python 2.1 to 2.4. A large part of testing involves extracting data from a long list of test files and checking that different Python versions produce consistent results. Checking the extract against COM results is also done. Using psyco speeds up this testing by a factor of 2 or 3.] I don't have the MS compiler(s). I've tried using the free Borland 5.5 compiler (which I've been using happily for some years for my own C extensions). This gives 4 errors, all relating to one statement at the very end of one file: Error E2222 c\Objects/pclassobject.c 174: Macro expansion too long Error E2222 c\Objects/pclassobject.c 174: Macro expansion too long Error E2322 c\Objects/pclassobject.c 175: Incorrect number format Error E2188 c\Objects/pclassobject.c 175: Expression syntax in function psy_clasobject_init [This was using Python 2.4 on the contents of the .tar.gz obtained from Sourceforge] Before I start digging into the Borland docs to find out what "too long" means, and reading the macro itself, I thought it might be an idea if I did a reality check: Is it a reasonable expectation that I should be able to do a "setup.py build_ext -i" using the Borland compiler? Alternatively, how can I acquire the 5 binaries? Thanks in advance, John |
From: <ne...@ci...> - 2006-02-09 23:17:42
|
DQobJEJGTUEzJE4lYSE8JWskRz89JDdMdSQ0JDYkJCReJDskcyEjO2QkTyU7JWwlVjZmM1pJdCRI JCQkJkE0OXFFODMrJE4jMyMwQmUwSj5lJE40ezonPFQkLD04JF4kayEiJTMlXyVlJUslRiUjJHJF fTNnJDckRiQkJGtCdDBmOSVIfiRIPz0kNyReJDkhIzRKQzEkS0BiTEAkJCQ/JDckXiQ5JEghIj9N OkokTj13QC0kLDAmP00kckM1JDklMyVfJWUlSyVGJSMkRyQ5ISMkPSROJGgkJiRKNFg3OCRLNj1M IyROJCIka0NLQC0kTyUzJUElaSReJEclIiUvJTslOSQ3JEYyPCQ1JCQbKEIgGyRCJTMlQSVpISEb KEJodHRwOi8vYXdnLndlYmNodS5jb20vY2FzYW5vdmEvPzE5MzQbJEIhISRHJTslbBsoQiANChsk QiVWNmYzWkl0JEg4ITp3JDckRiRiJGkkKCRsJFA9d0AtJE40aTxMPz9JVSQtJE4lVyVtJVUlIyE8 JWskSE8iTW1AaCRyOCskazt2JCwkRyQtJF4kOSEjJCpCVCRBJDckRiQqJGokXiQ5ISMbKEINCg0K DQoNCg0KLy8vLy8vLy8vLy8vLy8vLy8vLy8vLy8vLy8vLy8vLy8vDQobJEIlYSE8JWtJVE1XJE5K fSRPJDMkQSRpJEslYSE8JWskciItGyhCDQpjb25jZXB0M19uZXRAeWFob28uY2ENCg0KDQo= |
From: <in...@ra...> - 2006-02-05 11:02:43
|
$B!!(B_/$B!'(B_/*_/$B!'(B_/*_/$B!'(B_/*_/$B!'(B_/*_/$B!'(B_/*_/$B!'(B $B!!FM(-F}(-!*(-#H(-$J(-$*(-$M(-$'(-$5(-$s(-(B $B!!(,(0(,(0(,(0(,(0(,(0(,(0(,(0(,(0(,(0(,(0(B $B!!(B_/*_/$B!'(B_/*_/$B!'(B_/*_/$B!'(B_/*_/$B!'(B_/*_/$B!'(B_/* $B!|KE9-9pBeM}E9$K6P$a$k<+>N%+%j%9%^1D6H%^%s!X#0;a!Y$,(B $B7+$j9-$2$k>W7b$N<rCSFyNSNx0&3(4,%l%]!<%H(B!! $B$G$-$k$@$199?7$7$F%3%C%A4X78$N(B $B1D6HJs9p=qBe$o$j$K8x3+$7$F$$$/$D$b$j$J%V%m%0(B!! $B!X2G$K$_$D$+$i$J$$$h$&$K!#!#!#(B $B$_$D$+$C$?$i;&$5$l$A$c$&$s$@$m$&$J!!26#w#w!Y(B $B(,(,(,(,(,(,(,(,(,(,(,(,(,(,(,(,(,(,(,(,(,(,(,(,(,(,(,(B $B!y!z!y!!(Bhttp://rabbitlove.info/lvc/$B!!!y!z!y(B $B(,(,(,(,(,(,(,(,(,(,(,(,(,(,(,(,(,(,(,(,(,(,(,(,(,(,(,(B $B"#"#"#"#"#"#"#"#"#"#"#"#"#"#"#"#"#"#"#"#"#"#"#"#"#"#"#(B --------------------------------------------- $B$*CN$i$;%a!<%k<u?.5qH]$N>l9g$O2<5-%"%I%l%9$K$4JV?.$/$@$5$$!#(B in...@ok... ---------------------------------------------> |
From: <con...@uu...> - 2006-01-13 11:24:24
|
$B5.J}MM$H2q$$$?$$$H$$$&=w@-2q0wMM$,$*$j$^$9!#(B $B"'$*JV;v$3$A$i$+$i"'(B http://211.aboy.info/kanzen_muryo.php?id=35q76jhfgd8gl7yjs $B$$$D$b$4MxMQD:$$$F@?$KM-Fq$&8f:B$$$^$9!#(B $B%5%$%H%j%K%e!<%"%k$KH<$$!":FEPO?<jB3$-$,I,MW$G$9!#(B $B$^$?!"#1#0#0#0#01_J,$NL5NA%]%$%s%H$b$4MQ0U$7$F$*$j$^$9$N$G$<$R:FEPO?<jB3$-$r:Q$^$;$F$/$@$5$$!#(B http://211.aboy.info/kanzen_muryo.php?id=i479fgd8glfgh75kwhg $B"(%o%s%/%j%C%/!&ITEv@A5aEy$G$O$"$j$^$;$s$N$G!"0B?4$7$F$4MxMQ$/$@$5$$!#(B $B:FEPO?$,I,MW$N$J$$J}$O(B con...@uu... |