Re: [Python-Dev] FreeBSD test suite failure -> curses

[Jeroen Ruigrok van der Werven]

-On [20080309 23:59], "Martin v. Löwis" ([EMAIL PROTECTED]) wrote:
>So this now *is* a FreeBSD/ncurses expert's question.
>I don't think this is supposed to happen; newscr should
>become non-NULL when initscr is called, and should remain
>that way throughout.

Looking at the other FreeBSD build it seems to pass the tests. It's
6.2-RELEASE box. So right now I am getting my VMWare 6.2-R up and running
and seeing if I also get the same results. At least that narrows my search
to the point of my 6.3-STABLE from the 6.2-RELEASE date.

-- 
Jeroen Ruigrok van der Werven  / asmodai
イェルーン ラウフロック ヴァン デル ウェルヴェン
http://www.in-nomine.org/ | http://www.rangaku.org/
Alas! The world is full of enormous lights and mysteries, and man shuts
them from himself with one small hand! 
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com

[Python-Dev] Proxy form not getting through

[Greg Ewing]

I'm trying to send a proxy form, but all my mail to
[EMAIL PROTECTED] or [EMAIL PROTECTED] is getting bounced.

Is there another address I can send it to that goes
through a different mail server?

-- 
Greg
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com

Re: [Python-Dev] FreeBSD test suite failure -> curses

[Andrew MacIntyre]

Jeroen Ruigrok van der Werven wrote:
> -On [20080309 23:59], "Martin v. Löwis" ([EMAIL PROTECTED]) wrote:
>> So this now *is* a FreeBSD/ncurses expert's question.
>> I don't think this is supposed to happen; newscr should
>> become non-NULL when initscr is called, and should remain
>> that way throughout.
> 
> Looking at the other FreeBSD build it seems to pass the tests. It's
> 6.2-RELEASE box. So right now I am getting my VMWare 6.2-R up and running
> and seeing if I also get the same results. At least that narrows my search
> to the point of my 6.3-STABLE from the 6.2-RELEASE date.

test_curses on its own passes on my FreeBSD 6.3 box.  It segfaults when
run in the context of a full regression test though.

I've tried libthr instead of libpthread (via libmap.conf), and it
also fails only in the full regression test.  The backtrace from the
coredump is different from the libpthread case though...

libthr:
===
#0  0x2849513c in wecho_wchar () from /lib/libncursesw.so.6
#1  0x28496a89 in wecho_wchar () from /lib/libncursesw.so.6
#2  0x28497e62 in wecho_wchar () from /lib/libncursesw.so.6
#3  0x2849b134 in doupdate () from /lib/libncursesw.so.6
#4  0x287cf247 in PyCurses_doupdate (self=0x0)
 at /home/andymac/build/python-svn/trunk/Modules/_cursesmodule.c:182
#5  0x080c602e in PyEval_EvalFrameEx (f=0x93cbc0c, throwflag=0)
 at Python/ceval.c:3620
#6  0x080c6269 in PyEval_EvalFrameEx (f=0x93cba0c, throwflag=0)
 at Python/ceval.c:3722
#7  0x080c6269 in PyEval_EvalFrameEx (f=0x935b40c, throwflag=0)
 at Python/ceval.c:3722
#8  0x080c6eda in PyEval_EvalCodeEx (co=0x9b5bb60, globals=0x284c117c,
 locals=0x6e, args=0x817002c, argcount=0, kws=0x0, kwcount=0, defs=0x0,
 defcount=0, closure=0x0) at Python/ceval.c:2908
#9  0x080c702e in PyEval_EvalCode (co=0x9b5bb60, globals=0x93fb4f4,
 locals=0x93fb4f4) at Python/ceval.c:495
#10 0x080d938a in PyImport_ExecCodeModuleEx (
 name=0xbfbfdc60 "test.test_curses", co=0x9b5bb60,
 pathname=0xbfbfd2e0 
"/home/andymac/build/python-svn/trunk/Lib/test/test_curses.pyc") at 
Python/import.c:680
#11 0x080d97f3 in load_source_module (name=0xbfbfdc60 "test.test_curses",
 pathname=0xbfbfd2e0 
"/home/andymac/build/python-svn/trunk/Lib/test/test_curses.pyc", 
fp=0x282801d8) at Python/import.c:968
---Type  to continue, or q  to quit---

libpthread:
===
#0  0x281a655b in pthread_testcancel () from /lib/libpthread.so.2
#1  0x2819eeec in pthread_mutexattr_init () from /lib/libpthread.so.2
#2  0x28166450 in ?? ()


This is with a checkout updated to r61352.

Andrew.

-- 
-
Andrew I MacIntyre "These thoughts are mine alone..."
E-mail: [EMAIL PROTECTED]  (pref) | Snail: PO Box 370
[EMAIL PROTECTED] (alt) |Belconnen ACT 2616
Web:http://www.andymac.org/   |Australia
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com

Re: [Python-Dev] Proxy form not getting through

[Aahz]

On Thu, Mar 13, 2008, Greg Ewing wrote:
>
> I'm trying to send a proxy form, but all my mail to
> [EMAIL PROTECTED] or [EMAIL PROTECTED] is getting bounced.
> 
> Is there another address I can send it to that goes
> through a different mail server?

What's the error message?  I can relay it for you if you want, dunno
about other options for mailservers.  I think further discussion should
go on psf-members.
-- 
Aahz ([EMAIL PROTECTED])   <*> http://www.pythoncraft.com/

"All problems in computer science can be solved by another level of 
indirection."  --Butler Lampson
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com

Re: [Python-Dev] Complexity documentation request

[Adam Olsen]

On Mon, Mar 10, 2008 at 12:05 PM, Daniel Stutzbach
<[EMAIL PROTECTED]> wrote:
> On Sun, Mar 9, 2008 at 9:22 AM, Aahz <[EMAIL PROTECTED]> wrote:
>  >  There probably would be some value in a wiki page on python.org that
>  >  provides this information, particularly across versions.  You may be
>  >  able to find volunteers to help on comp.lang.python.
>
>  I just created a very basic one at
>  http://wiki.python.org/moin/TimeComplexity?action=show
>
>  I'm not that familiar with the Wiki syntax, so the tables are kind of
>  ugly at the moment.
>
>  I wasn't sure about many of the set() operations, so I didn't include those.

For python's purposes, I think it's simpler to classify an operation
as either "linear" or "near constant", then have an explanation that
"near constant" is only the typical performance (it doesn't make
guarantees about worst case behaviour), may include O(log n)
implementations, etc.  That suffices to distinguish use cases, and
anything more specific may be dominated by constant factors anyway.

Something like sort is a special case.  I don't think the languages
needs to guarantee any particular performance, yet it's worth
documenting that CPython has a rather good implementation.

-- 
Adam Olsen, aka Rhamphoryncus
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com

Re: [Python-Dev] Complexity documentation request

[Dimitrios Apostolou]

Daniel Stutzbach wrote:
> I just created a very basic one at
> http://wiki.python.org/moin/TimeComplexity?action=show

Hi,

Just one quick note. What exactly do you mean by "Amortized worst case"? 
Shouldn't it just be "Worst case"? I think that the word "amortized" 
better describes the time complexity of specific operations.

For example  I think that the insertion in a dictionary should be noted 
as "O(1) amortized" for the average case meaning that when doing 
infinite random insertions, the time asymptotically tends to be 
constant. And worst case is simply O(n), not amortized. Am I missing 
something?


Thanks,
Dimitris


___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com

Re: [Python-Dev] Complexity documentation request

[Daniel Stutzbach]

On Wed, Mar 12, 2008 at 2:52 PM, Dimitrios Apostolou <[EMAIL PROTECTED]> wrote:
>  Just one quick note. What exactly do you mean by "Amortized worst case"?
>  Shouldn't it just be "Worst case"? I think that the word "amortized"
>  better describes the time complexity of specific operations.

http://en.wikipedia.org/wiki/Amortized_analysis

-- 
Daniel Stutzbach, Ph.D.President, Stutzbach Enterprises LLC
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com

Re: [Python-Dev] Python XML Validator

[Ronald Oussoren]

On 11 Mar, 2008, at 18:01, Stefan Behnel wrote:


Mike Meyer wrote:
On Tue, 11 Mar 2008 14:55:04 +0100 Stefan Behnel  
<[EMAIL PROTECTED]> wrote:

(weird places these threads come up at, but now that it's here...)
Mike Meyer wrote:

On Tue, 04 Mar 2008 15:44:32 -0800 Ned Deily <[EMAIL PROTECTED]> wrote:

In article <[EMAIL PROTECTED]>,
Mike Meyer <[EMAIL PROTECTED]> wrote:

On Thu, 28 Feb 2008 23:42:49 + (UTC) Medhat Gayed
<[EMAIL PROTECTED]> wrote:
lxml is good but not written in python and difficult to  
install and didn't

work on MacOS X.


Please note that this original complaint is *not* mine. However...


Due to a design problem in MacOS-X, not a problem in lxml.


I didn't find it noticeably harder to install lxml on MacOS-X than
most other systems.


It seems to be for a number of people, though, who turn up on the  
mailing list

complaining about just that.


What can make life a bit harder on OSX is universal binaries, although  
those aren't too hard either.


BTW. Which design problem?

BTW2. Discusion of problems with building lxml on OSX are better  
suited for the pythonmac-sig list (or the lxml one of course).




Yes, but the proposal was to include it in the Python standard
library. Software that doesn't work on popular target platforms
without updating a standard system library isn't really suitable for
that.


Hmm, coming somewhat back on-topic: how does Python currently handle  
its
dependencies under MacOS-X? SQLite, for example? Does it use system  
libraries
only, or are there libraries it ships with? (The MacOS distro is  
much bigger,
but that might be due to the universal build - although that  
suggests that

MacOS-X users do not care about disk space or download size anyway)


The .dmg on python.org includes it's own copies of sqlite, ncurses and  
berkeley db. That's mostly needed to be able to run on 10.3.9 or  
later. My guess is that the size difference with other binary  
distributions is mostly due to universal binaries, those double the  
size of executables.  This might get worse in the future, I hope to  
find some time go make the python framework 4-way universal (32-bit  
and 64-bit code on PPC and Intel).


Ronald

smime.p7s
Description: S/MIME cryptographic signature
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com

Re: [Python-Dev] FreeBSD test suite failure -> curses

[Jeroen Ruigrok van der Werven]

-On [20080312 13:30], Andrew MacIntyre ([EMAIL PROTECTED]) wrote:
>test_curses on its own passes on my FreeBSD 6.3 box.  It segfaults when
>run in the context of a full regression test though.

So it does for my 6.3-STABLE.

But 6.2-RELEASE goes through the entire regression though. I need to check,
but I think in between 6.2-R and 6.3-R Rong-En Fan made the switch to a
newer ncurses for the wide character support.

-- 
Jeroen Ruigrok van der Werven  / asmodai
イェルーン ラウフロック ヴァン デル ウェルヴェン
http://www.in-nomine.org/ | http://www.rangaku.org/
My name is Legion: for we are many...
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com

[Python-Dev] Why .index() is not a method of all sequence types ?

[Joost Behrends]

Hello,

hopefully this mailing list is the right address for the following.

Since there is a huge gap in performance between tuple(cur.execute(...))
and list(cur.execute(...)) - i saw a factor in the magnitude of 50 once -
the first has always to be chosen when sufficient. Even if that difference
would be smaller - you also document the resulting sequence as read-only
in your code. I also use deque( ... some generator ... ) frequently
(And i think, that this should have more room in tutorials for
beginners - some of them have no idea, what tuples are for).

With such a tuple tp i tried 'ix = tp.index(...)' recently and was
astonished to learn, that this doesn't work. Since we have '... in tp'
for me it seems, that it should make very little difference in 
the interpreter's code, if .index() would be a method of any sequence, 
mutable or not. Such a small difference, that this minor change wouldn't
deserve a PEP.

Do i overlook something here ?

Kind regards, Joost Behrends
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com

[Python-Dev] Request for another build slave

[Trent Nelson]

Can someone set me up with a build slave for an x86 FreeBSD box (6.2-STABLE, 
although we'll be migrating to 7.x in a week or so)?  Thanks.

[Suggestion: perhaps we could set up a [EMAIL PROTECTED] list for discussing 
buildbot administrative minutiae, rather than polluting python-dev?]

Trent.
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com

Re: [Python-Dev] Why .index() is not a method of all sequence types ?

[Terry Reedy]

"Joost Behrends" <[EMAIL PROTECTED]> wrote in message 
news:[EMAIL PROTECTED]
| With such a tuple tp i tried 'ix = tp.index(...)' recently and was
| astonished to learn, that this doesn't work. Since we have '... in tp'
| for me it seems, that it should make very little difference in
| the interpreter's code, if .index() would be a method of any sequence,
| mutable or not. Such a small difference, that this minor change wouldn't
| deserve a PEP.

I believe .index() is part of the 3.0 sequence protocol and hence has been 
added to tuples for 3.0.  Don't know if has been or will be backported to 
2.6. 



___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com

[Python-Dev] Python 2.5.1 error when running cvs2svn [SEC=UNCLASSIFIED]

[James, Paul]

Hello python-dev,
 
We are trying to run the cvs2svn utility and get an execution problem
coming from Python. 
The version of Python we have installed on a solaris sparc10 machine is
2.5.1.
 
The error trace is below, the error is at end in blue-
 
 
Traceback (most recent call last):
  File "/usr/local/bin/cvs2svn", line 27, in 
from cvs2svn_lib.main import main
  File "/usr/local/lib/python2.5/site-packages/cvs2svn_lib/main.py",
line 31, in 
from cvs2svn_lib.run_options import RunOptions
  File
"/usr/local/lib/python2.5/site-packages/cvs2svn_lib/run_options.py",
line 41, in 
from cvs2svn_lib.svn_output_option import DumpfileOutputOption
  File
"/usr/local/lib/python2.5/site-packages/cvs2svn_lib/svn_output_option.py
", line 42, in 
from cvs2svn_lib.svn_repository_mirror import SVNRepositoryMirror
  File
"/usr/local/lib/python2.5/site-packages/cvs2svn_lib/svn_repository_mirro
r.py", line 34, in 
from cvs2svn_lib.serializer import MarshalSerializer
  File
"/usr/local/lib/python2.5/site-packages/cvs2svn_lib/serializer.py", line
24, in 
import zlib
ImportError: ld.so.1: python: fatal: relocation error: file
/usr/local/lib/python2.5/lib-dynload/zlib.so: symbol inflateCopy:
referenced symbol not found
 
 
 
-The zlib.so file exisits on our machine at the specified path.
We are using Python 2.5.1. If possible, could you provide advice on
where the problem is occuring?
 
Thanks,
 
Paul James
 
[EMAIL PROTECTED]  




**
This email and any files transmitted with it are confidential and
intended solely for the use of the individual or entity to whom they are
addressed. If you are not the intended recipient, you are notified that
any use or dissemination of this communication is prohibited. If you
receive this transmission in error, please notify us immediately by
telephone on +61 2 62795000 and delete all copies of this transmission
together with any attachments.
**___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com