Guido van Rossum | 1 Jul 2000 01:02
Favicon

Re: Idle breakage

> confirmed.  SRE implements $ exactly as described in
> the library reference, RE doesn't ;-)

All this is done to match what Perl does. :-(

> patch coming within 30 minutes.

Saw it.  Thanks!

But I still get warnings in IDLE:

Failed to load extension 'ParenMatch'
Traceback (most recent call last):
  File "../Tools/idle/EditorWindow.py", line 529, in load_standard_extensions
    self.load_extension(name)
  File "../Tools/idle/EditorWindow.py", line 539, in load_extension
    mod = __import__(name, globals(), locals(), [])
  File "/projects/python/develop/guido/src/Tools/idle/ParenMatch.py", line 15, in ?
    import PyParse
  File "/projects/python/develop/guido/src/Tools/idle/PyParse.py", line 14, in ?
    _synchre = re.compile(r"""
  File "./../Lib/sre.py", line 54, in compile
    return _compile(pattern, flags)
  File "./../Lib/sre.py", line 86, in _compile
    p = sre_compile.compile(pattern, flags)
  File "./../Lib/sre_compile.py", line 217, in compile
    _compile(code, p.data, flags)
  File "./../Lib/sre_compile.py", line 121, in _compile
    emit(ATCODES[AT_MULTILINE[av]])
KeyError: at_boundary
(Continue reading)

Guido van Rossum | 1 Jul 2000 01:10
Favicon

Re: Oops on AIX

> After the CVS commit storm that occurred during the last 3 days,
> I wanted to validate the current build on AIX. And I am stalled.
> 
> I am not sure, but it seems like the errors I get relate with the
> latest 64-bit support patches, and I don't dare to suggest corrections
> in this area, so I welcome any help...

let me suggest patches...  If these work, please check them in:

>         xlc_r -O -I./../Include -I.. -DHAVE_CONFIG_H -c methodobject.c
> "methodobject.c", line 183.36: 1506-280 (E) Function argument assignment between types "void*" and
"struct _object*(*)(struct _object*,struct _object*)" is not allowed.

Index: methodobject.c
===================================================================
RCS file: /cvsroot/python/python/dist/src/Objects/methodobject.c,v
retrieving revision 2.28
diff -c -r2.28 methodobject.c
*** methodobject.c	2000/06/30 15:01:00	2.28
--- methodobject.c	2000/06/30 22:09:55
***************
*** 180,186 ****
  		if (x == -1)
  			return -1;
  	}
! 	y = _Py_HashPointer(a->m_ml->ml_meth);
  	if (y == -1)
  		return -1;
  	x ^= y;
--- 180,186 ----
(Continue reading)

Guido van Rossum | 1 Jul 2000 01:14
Favicon

Re: Hey! who changed sys.platform?!

> Not that I hope to override the heavy -1, but I don't agree with the second
> point.  It embodies a huge amount of knowledge that is needed to write
> portable code.  As such, IMO, it _does_ belong in the standard library.  How
> is it different in its nature from sys.platform, which is only a much weaker
> version of the same concept?

A more subtle way of stating my opinion could be: if we were to do
something in the standard distribution about the problems that this is
addressing, I think we would do it in a much more direct fashion,
e.g. by making the appropriate enquiry functions directly accessible.

--Guido van Rossum (home page: http://www.python.org/~guido/)

Fredrik Lundh | 1 Jul 2000 01:35
Picon

Re: Idle breakage

barry wrote:

> Go ahead and check it in.  I'll run idle and see wot hoppens.

well?  can I go to sleep now?  please?

</F>

Guido van Rossum | 1 Jul 2000 02:35
Favicon

Re: Idle breakage

> barry wrote:
> 
> > Go ahead and check it in.  I'll run idle and see wot hoppens.
> 
> well?  can I go to sleep now?  please?

Yes.  Thanks!

--Guido van Rossum (home page: http://www.python.org/~guido/)

Neil Schemenauer | 1 Jul 2000 01:41
Picon

Updating patches on SF

WTF is going on?  I did successfully update one of my patches but
now that feature no longer seems to work.  I get the message:

   Patch Uploaded Successfully Added Patch Could Not Send Patch Update 

and the old patch remains.

  Neil

Neil Schemenauer | 1 Jul 2000 01:46
Picon

Re: Updating patches on SF

Killing the disk and memory cache seemed to fix the problem.

  Neil

Vladimir Marangozov | 1 Jul 2000 02:13
Picon

test_array failure on AIX


Any advice as to where I should look at and/or how to try fixing this?

~/python/CVS> ./python Lib/test/test_array.py
****************************************
array after append:  array('c', 'c')
char array with 10 bytes of TESTFN appended:  array('c', 'cThe quick ')
char array with list appended:  array('c', 'cThe quick abc')
array of c after inserting another: array('c', 'ccThe quick abc')
array of c converted to a list:  ['c', 'c', 'T', 'h', 'e', ' ', 'q', 'u', 'i', 'c', 'k', ' ', 'a', 'b', 'c']
array of c converted to a string:  'ccThe quick abc'
****************************************
array after append:  array('b', [1])
array of b after inserting another: array('b', [1, 1])
array of b converted to a list:  [1, 1]
array of b converted to a string:  '\001\001'
overflow test: array('b', [-128L])
Traceback (most recent call last):
  File "Lib/test/test_array.py", line 137, in ?
    main()
  File "Lib/test/test_array.py", line 13, in main
    testtype(type, 1)
  File "Lib/test/test_array.py", line 132, in testtype
    testoverflow(type, signedLowerLimit, signedUpperLimit)
  File "Lib/test/test_array.py", line 25, in testoverflow
    raise TestFailed, "array(%s) overflowed assigning %s" %\
test_support -- test failed: array('b') overflowed assigning -128L

--

-- 
       Vladimir MARANGOZOV          | Vladimir.Marangozov <at> inrialpes.fr
(Continue reading)

Guido van Rossum | 1 Jul 2000 03:19
Favicon

Re: test_array failure on AIX

> Any advice as to where I should look at and/or how to try fixing this?
> 
> 
> ~/python/CVS> ./python Lib/test/test_array.py
> ****************************************
> array after append:  array('c', 'c')
> char array with 10 bytes of TESTFN appended:  array('c', 'cThe quick ')
> char array with list appended:  array('c', 'cThe quick abc')
> array of c after inserting another: array('c', 'ccThe quick abc')
> array of c converted to a list:  ['c', 'c', 'T', 'h', 'e', ' ', 'q', 'u', 'i', 'c', 'k', ' ', 'a', 'b', 'c']
> array of c converted to a string:  'ccThe quick abc'
> ****************************************
> array after append:  array('b', [1])
> array of b after inserting another: array('b', [1, 1])
> array of b converted to a list:  [1, 1]
> array of b converted to a string:  '\001\001'
> overflow test: array('b', [-128L])
> Traceback (most recent call last):
>   File "Lib/test/test_array.py", line 137, in ?
>     main()
>   File "Lib/test/test_array.py", line 13, in main
>     testtype(type, 1)
>   File "Lib/test/test_array.py", line 132, in testtype
>     testoverflow(type, signedLowerLimit, signedUpperLimit)
>   File "Lib/test/test_array.py", line 25, in testoverflow
>     raise TestFailed, "array(%s) overflowed assigning %s" %\
> test_support -- test failed: array('b') overflowed assigning -128L

Look at b_setitem() in arraymodule.c.

(Continue reading)

Greg Stein | 1 Jul 2000 02:32

proper CVS usage is a must! (was: CVS: python/dist/src/Objects unicodeobject.c,2.31,2.32)

On Fri, Jun 30, 2000 at 04:53:31PM +0200, M.-A. Lemburg wrote:
> > Why was the change that occurred in revision 2.31 reverted?  Accident?
> > 
> > The change log said:
> > Jack Jansen: Use include "" instead of <>; and staticforward declarations
> 
> Accident... I'll revert that change.

This is symptomatic of people not being careful with their CVS usage.

*ALWAYS* do a "cvs update" before any commits. If the file has changed while
you're working on it, CVS will merge the changes in with yours. You will be
notified if there were any conflicts.

But this is a MUST. We've seen this reversal of changes twice now. Only
through the careful eye of some -checkins watchers has that fact turned up.
If those people weren't watching, we'd be lost.

If you're going to commit changes to Python, then please take the
responsibility to use CVS correctly.

Thanks!
-g

--

-- 
Greg Stein, http://www.lyra.org/


Gmane