Mailman 3 July 2004 - pypy-dev

Re: [pypy-dev] src/pypy/translator/test and src/pypy/tool/test
by Laura Creighton July 5, 2004

July 5, 2004

In a message of Tue, 06 Jul 2004 00:00:22 +0200, holger krekel writes: >[Laura Creighton Mon, Jul 05, 2004 at 11:33:52PM +0200] >> These tests are failing because they are looking for std/path >> >> i.e. >> >> Traceback (most recent call last): >> File "test_sourcegen.py", line 4, in ? >> from pypy.tool.udir import udir >> File "/home/lac/src/pypy/trunk/src/pypy/tool/udir.py", line 3, in ? >> from std.path import local >&… [View More]

2 1

src/pypy/translator/test and src/pypy/tool/test
by Laura Creighton July 5, 2004

July 5, 2004

These tests are failing because they are looking for std/path i.e. Traceback (most recent call last): File "test_sourcegen.py", line 4, in ? from pypy.tool.udir import udir File "/home/lac/src/pypy/trunk/src/pypy/tool/udir.py", line 3, in ? from std.path import local ImportError: No module named std.path what should they be saying instead? Laura

2 1

pow and complex object
by Ben Young July 5, 2004

July 5, 2004

Hi, I found a few weirdities in pos and complex. I tries to fix them by putting debugging print statements in complexobject.py in appspace but these did not seem to be picked up. Is this the right place to do this or does complex exist somewhere else? (All this is in std object space) pow(2j, 2) => (1+3.4247374308419473e-311j) should be (-4 + 0j) pow(2j, "fde") => 0j should be type error Cheers, Ben ---

2 10

Modifying sys.modules while importing
by Seo Sanghyeon July 5, 2004

July 5, 2004

Consider following setup: mkdir a mkdir b cat >a/__init__.py <<END import sys, b sys.modules[__name__] = b END touch b/__init__.py touch b/c.py Now run "import a.c". CPython imports okay, PyPy raises ImportError. This breaks xml package when PyXML is installed. Read Lib/xml/__init__.py for details. Bye,

1 0

I am about ready to feed all of the src-utest branch of pypy to utestconverter.
by Laura Creighton July 2, 2004

July 2, 2004

How do we want to do this? Make a 'new' directory in each dir and put the new version of each file in the equivalently-named place there? How do we want, beyond eyeballing it, to check to see that the script works? The only thing left to do, as far as I can tell, is to add the option parsing. Do we want this to read from stdin? Do we want it to take a filename? I figure stdin to stdout is what we want, but optionally let it take a file name. But other tastes may vary. Opinions? Laura

2 1

Re: [pypy-dev] PyPy site suggestions
by Laura Creighton July 2, 2004

July 2, 2004

In a message of Fri, 02 Jul 2004 21:43:46 +0200, holger krekel writes: >Hi Terry, > >[Terry Reedy Thu, Jul 01, 2004 at 12:54:33PM -0400] >> I have a couple of suggestions for the PyPy site, but could not find a >> 'contact webmaster' link or button, hence this post. >> >> 0. Add such to your standard page template. > >ok, added right of the top-level menu. I think that in the end the >'lists' page should be renamed to 'contact', 'talk' or some such … [View More]

2 1

PyPy site suggestions
by Terry Reedy July 2, 2004

July 2, 2004

I have a couple of suggestions for the PyPy site, but could not find a 'contact webmaster' link or button, hence this post. 0. Add such to your standard page template. 1. The standard left side bar, under 'sprintinfo', has a link to the Amsterdam announcement, which in now rather useless, but lacks a link to the report thereupon, http://codespeak.net/pipermail/pypy-dev/2003q4/002495.html which still is useful. Suggestion: replace former with latter. 2. The mail archive contains a lot of … [View More]

2 1

[FW: Re: [pypy-dev] Patches?]
by Seo Sanghyeon July 2, 2004

July 2, 2004

Oops, replied in private by mistake... ----- Forwarded message from tinuviel ----- To: Ben Young <ben(a)transversal.com> Subject: Re: [pypy-dev] Patches? On Wed, Jun 30, 2004 at 11:08:38AM +0100, Ben Young wrote: > Hi, > > I have been following the pypy-dev mailing list for some time, as well as > maintaining a anon svn checkout of the pypy source and am really excited by > this project (in fact it has inspired me to write my own experimental > language in python … [View More]

3 2

utest conversion tool question
by Laura Creighton July 1, 2004

July 1, 2004

I am still dizzy and sick, but I am trying to get something done anyhow. I have this question. If you start with self.assertEquals(f(x) + g(x) == q(x), 'Message to print when the assertion fails') you would like things to come back as assert f(x) +\ g(x) == q(x), 'Message to print when the assertion fails' It is the last, optional message which is the sticky part, otherwise you could say, just keep the original parentheses. But this does not work, as … [View More]

5 8

Re: [pypy-dev] utest conversion tool question
by Laura Creighton July 1, 2004

July 1, 2004

In a message of Wed, 30 Jun 2004 20:55:34 +0200, holger krekel writes: >Hey Laura, > >[Laura Creighton Wed, Jun 30, 2004 at 04:43:25PM +0200] >> I am still dizzy and sick, but I am trying to get something done anyhow >. I have >> this question. > >ups, didn't know you were ill, but you seem to have fun recovering :-) > >> If you start with >> >> self.assertEquals(f(x) + >> g(x) == q(x), 'Message to print when the … [View More]assertion fa >ils') > >Oh, ^^^^ you mean a comma here, i guess?! Yes. silly me. >> you would like things to come back as >> >> assert f(x) +\ >> g(x) == q(x), 'Message to print when the assertion fai >ls' > >actually i'd prefer > > assert f(x) + g(x) == q(x), 'Message to print when the assertion fails' > >Because i think the output logic should just format it so that it looks >nice (e.g. less < 76 characters per line) and retain the correct >semantics of the original statement. I wouldn't worry about the >original input format, though. If this proves too hard then maybe blame >Armin who suggested the 'comma'-try-parsing-withought-understanding-the >expression-tricks :-) It is not too hard, but at some point you have to face the 'my input is more than 76 chars long' problem. I thought it would be better to preserve the spacing written by the original unittest user, breaking it wherever they did if possible. There is no problem in stripping out the newlines, and seeing if what you get is smaller than 78 chars, but what shall we do if the answer is 'no'? Adding parenthesis will work. see: ython 2.3.4 (#2, May 29 2004, 03:31:27) [GCC 3.3.3 (Debian 20040417)] on linux2 Type "help", "copyright", "credits" or "license" for more information. >>> import unittest >>> class Testit(unittest.TestCase): ... def test(self): ... self.assertEquals(1 + 2 + 3 + 4 + 5 + 6 + 7 + 8 + 9 + 10 ... + 11, 0, '''A huge US Style disclaimer to print when ... we fail. You can't sue me even if this program makes your computer ... explode, and gives your dogs fleas.''') ... >>> unittest.main() F ====================================================================== FAIL: test (__main__.Testit) ---------------------------------------------------------------------- Traceback (most recent call last): File "<stdin>", line 6, in test File "/usr/lib/python2.3/unittest.py", line 302, in failUnlessEqual raise self.failureException, \ AssertionError: A huge US Style disclaimer to print when we fail. You can't sue me even if this program makes your computer explode, and gives your dogs fleas. ---------------------------------------------------------------------- Ran 1 test in 0.001s FAILED (failures=1) At any rate, if you think the output isn't pretty enough, there will be plenty of time to criticise ... Laura, brain still full of high pitched squeals. (Tintinitus is very interesting, but I've satisfied my curiosity about it for a while ... :-) ) [View Less]

1 0