[issue4111] Add DTrace probes

2009-01-22 Thread Skip Montanaro
Skip Montanaro added the comment: So I completely dropped the ball on this. It appears we have some folks from Sun and Brett surmised that Ronald Oussoren would be the likely person to do the heavy lifting on the Apple side of things. Ronald, I've made you nosy. I will try to get the So

[issue4989] 'calendar' module is crummy and should be removed

2009-01-18 Thread Skip Montanaro
Skip Montanaro added the comment: Look at the oldest checkin comment for a line still in the module: r2166 | guido | 1990-10-13 14:23:40 -0500 (Sat, 13 Oct 1990) | 2 lines Initial revision In short, it's been there for a long, long time. Long before PEPs. Long before Tkinter.

[issue4753] Faster opcode dispatch on gcc

2009-01-16 Thread Skip Montanaro
Skip Montanaro added the comment: Antoine> (sorry, the patch is very long because it seems running Antoine> autoconf changes a lot of things in the configure script) Normal practice is to not include the configure script in such patches and indicate to people that they will need

[issue4896] Faster why variable manipulation in ceval.c

2009-01-11 Thread Skip Montanaro
Skip Montanaro added the comment: pybench comparison... % ./python.exe Tools/pybench/pybench.py -s stock.out -c why.out - -- PYBENCH 2.0

[issue4896] Faster why variable manipulation in ceval.c

2009-01-11 Thread Skip Montanaro
Skip Montanaro added the comment: Pystone results: apply why patch py3k% rm $TMPDIR/*.[coi] ; make python.exe && rm -f /tmp/trash ; ./python.exe Lib/test/pystone.py rm: /tmp/*.[coi]: No such file or directory make: `python.exe' is up to date. Pystone(1.1) time for 5 passes =

[issue4472] Is shared lib building broken on trunk for Mac OS X?

2009-01-10 Thread Skip Montanaro
Skip Montanaro added the comment: Works for me. Thanks Ronald. Closing... -- assignee: -> ronaldoussoren status: pending -> closed ___ Python tracker <http://bugs.python.org/

[issue4896] Faster why variable manipulation in ceval.c

2009-01-09 Thread Skip Montanaro
Skip Montanaro added the comment: >> I thought "why_not_here" was meaningful. Antoine> I don't know, when I see "goto why_not_here" it looks like a Antoine> joke to me :) Well, I think the enum name WHY_NOT is kind of a joke itself, but it's

[issue4896] Faster why variable manipulation in ceval.c

2009-01-09 Thread Skip Montanaro
Skip Montanaro added the comment: Antoine> The label "why_not_here" should be renamed to something more Antoine> meaningful IMO. Or you could just kill the label and use Antoine> "continue" instead. I thought "why_not_here" was meaningful. &qu

[issue4896] Faster why variable manipulation in ceval.c

2009-01-09 Thread Skip Montanaro
New submission from Skip Montanaro : The why_code enum in ceval.c has values which form a bit set. Comparison of the why variable against multiple values is going to be faster using bitwise operations instead of logical ones. For example, instead of why == WHY_RETURN || why

[issue4888] misplaced (or misleading) assert in ceval.c

2009-01-08 Thread Skip Montanaro
New submission from Skip Montanaro : There is what I believe is a misplaced - or at least misleading - assert in the while loop following the fast_block_end label. If why != WHY_YIELD before the loop starts I don't see how that relationship could change within the loop. Proposed patch ag

[issue4753] Faster opcode dispatch on gcc

2009-01-07 Thread Skip Montanaro
Skip Montanaro added the comment: Paolo> Various techniques allow to create binary code from the Paolo> interpreter binary, by just pasting together the code for the Paolo> common interpreters cases and producing calls to the other. But, Paolo> guess what, on most platf

[issue4863] deprecate/delete distutils.mwerkscompiler...

2009-01-06 Thread Skip Montanaro
New submission from Skip Montanaro : I was just poking around the distutils documentation and came across the distutils.mwerkscompiler module. Surely that can't be useful anymore, can it? The doc reads, in its entirety: Contains MWerksCompiler, an implementation of the abstract CCom

[issue4834] Trouble configuring with icc on Mac OS X 10.5

2009-01-04 Thread Skip Montanaro
Skip Montanaro added the comment: Martin> I don't think this is a bug. The change actually dates from Martin> r45800; I believe the intention is that the Python binaries work Martin> on 10.3 and newer, unless you use 10.2 or older to build them Martin> (in which ca

[issue4824] test_cmd_line failure on Mac OS X for py3k

2009-01-04 Thread Skip Montanaro
Skip Montanaro added the comment: Yeah, looks like it. Closing. -- resolution: -> duplicate status: open -> closed ___ Python tracker <http://bugs.python.org/

[issue4835] SIZEOF_SOCKET_T not defined

2009-01-04 Thread Skip Montanaro
New submission from Skip Montanaro : Compiling with Intel's icc I get lots of remarks like this: icc -c -fno-strict-aliasing -DNDEBUG -g -O3 -Wall -Wstrict-prototypes -I. -IInclude -I../Include -DPy_BUILD_CORE -o Parser/acceler.o ../Parser/acceler.c ../Include/longobject

[issue4834] Trouble configuring with icc on Mac OS X 10.5

2009-01-04 Thread Skip Montanaro
New submission from Skip Montanaro : I get this error when trying to configure with Intel's icc on my Mac (Intel, 10.5.6, Xcode 3.1.2): >> configure:10332: checking size of size_t >> configure:10637: icc -o conftest -g -O2 conftest.c >&5 >> ld:

[issue4753] Faster opcode dispatch on gcc

2009-01-04 Thread Skip Montanaro
Skip Montanaro added the comment: I'm sure this is the wrong place to bring this up, but I had a thought about simple JIT compilation coupled with the opcode dispatch changes in this issue. Consider this silly function: >>> def f(a, b): ... result = 0

[issue3783] dbm.sqlite proof of concept

2009-01-04 Thread Skip Montanaro
Skip Montanaro added the comment: Hopefully I'm not picking at a scab here. I updated the dbm.sqlite module in the sandbox. It now orders by rowid instead of by key. (I saw no performance penalty for the small table sizes I was using to ordering. I switched from ordering by key to ord

[issue4824] test_cmd_line failure on Mac OS X for py3k

2009-01-03 Thread Skip Montanaro
Skip Montanaro added the comment: Here is another data point. I added some print calls to the subprocess module and ran the key call from the interpreter: % ./python.exe Python 3.1a0 (py3k:68218, Jan 3 2009, 15:06:30) [GCC 4.0.1 (Apple Inc. build 5490)] on darwin Type "

[issue4824] test_cmd_line failure on Mac OS X for py3k

2009-01-03 Thread Skip Montanaro
New submission from Skip Montanaro : test_cmd_line.test_run_code fails for me on Mac OS X: % ./python.exe -bb Lib/test/regrtest.py -v test_cmd_line test_cmd_line test_directories (test.test_cmd_line.CmdLineTest) ... ok test_optimize (test.test_cmd_line.CmdLineTest) ... ok

[issue4753] Faster opcode dispatch on gcc

2009-01-02 Thread Skip Montanaro
Changes by Skip Montanaro : Added file: http://bugs.python.org/file12555/ceval.i.threaded ___ Python tracker <http://bugs.python.org/issue4753> ___ ___ Python-bugs-list m

[issue4753] Faster opcode dispatch on gcc

2009-01-02 Thread Skip Montanaro
Skip Montanaro added the comment: Alexandre's last comment reminded me I forgot to post the PPC assembler code. Next two files are the output as requested by Antoine. Added file: http://bugs.python.org/file12553/ceval.i.unthreaded ___ Python tracker

[issue4753] Faster opcode dispatch on gcc

2009-01-02 Thread Skip Montanaro
Skip Montanaro added the comment: Antoine> Ok, so the threaded version is actually faster by 20% on your Antoine> PPC, and slower by 5% on your Core 2 Duo. Thanks for doing the Antoine> measurements! Confirmed by pystone runs as well. Sorry for the earlier misdirecti

[issue4753] Faster opcode dispatch on gcc

2009-01-02 Thread Skip Montanaro
Skip Montanaro added the comment: The next is the result of running on my MacBook Pro (Intel Core 2 Duo). Added file: http://bugs.python.org/file12546/pybench.sum.Intel ___ Python tracker <http://bugs.python.org/issue4

[issue4753] Faster opcode dispatch on gcc

2009-01-02 Thread Skip Montanaro
Skip Montanaro added the comment: OK, I think I'm misreading the output of pybench. Let me reset. Ignore anything I've written previously on this topic. Instead, I will just post the output of my pybench comparison runs and let more expert people interpret as appropriate. The fir

[issue4810] timeit needs "official" '--' flag

2009-01-02 Thread Skip Montanaro
New submission from Skip Montanaro : Consider this timeit run: % python -m timeit '-1.0e-3 < -0.0001 < 1.0e-3' option -1 not recognized use -h/--help for command line help As it turns out this works: % python -m timeit -- '-1.0e-3 < -0.0001 < 1.0e-

[issue4753] Faster opcode dispatch on gcc

2009-01-02 Thread Skip Montanaro
Skip Montanaro added the comment: Antoine> I fear that with a configure option, disabled by default, the Antoine> code will get very poor testing and perhaps get broken in some Antoine> subtle way without anyone noticing. That can be fixed by enabling that option on the buildb

[issue4753] Faster opcode dispatch on gcc

2009-01-01 Thread Skip Montanaro
Skip Montanaro added the comment: Skip> You could backport it to 2.4 & 2.5 and just put it up on PyPI... Paolo> I was thinking to a private backport as well. I didn't know Paolo> about PyPI, it looks like PyPI is more for contributed modules Paolo> than for

[issue4753] Faster opcode dispatch on gcc

2008-12-31 Thread Skip Montanaro
Skip Montanaro added the comment: Paolo> (2.5 is in bugfix-only mode, and as far as I can see this patch Paolo> cannot be accepted there, sadly). You could backport it to 2.4 & 2.5 and just put it up on PyPI... ___ Python trac

[issue4753] Faster opcode dispatch on gcc

2008-12-31 Thread Skip Montanaro
Skip Montanaro added the comment: Antoine> You're sure you didn't compile in debug mode or something? Just Antoine> checking. There was a cut-n-paste error in that one which I noticed right after submitting (man, do I hate the crappy editing capability of widgets). I rem

[issue4753] Faster opcode dispatch on gcc

2008-12-31 Thread Skip Montanaro
Skip Montanaro added the comment: Works pretty well for me on my MacBook Pro, but on my G5 it performed abysmally. In fact, it ran so much worse that I cleaned up my sandbox and did both checks all over again to make sure I didn't mess something up. It looks like my MacBook Pro saw abou

[issue4753] Faster opcode dispatch on gcc

2008-12-31 Thread Skip Montanaro
Changes by Skip Montanaro : ___ Python tracker <http://bugs.python.org/issue4753> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/o

[issue4753] Faster opcode dispatch on gcc

2008-12-31 Thread Skip Montanaro
Skip Montanaro added the comment: Works pretty well for me on my MacBook Pro, but on my G5 it performed abysmally. In fact, it ran so much worse that I cleaned up my sandbox and did both checks all over again to make sure I didn't mess something up. It looks like my MacBook Pro saw ab

[issue4753] Faster opcode dispatch on gcc

2008-12-31 Thread Skip Montanaro
Changes by Skip Montanaro : -- nosy: +skip.montanaro ___ Python tracker <http://bugs.python.org/issue4753> ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue4472] Is shared lib building broken on trunk for Mac OS X?

2008-12-31 Thread Skip Montanaro
Skip Montanaro added the comment: The patch seemed to work for me. Should I worry that I don't see -fPIC or -fpic in the compile commands? Also, running "make test" before at least installing libpython2.7.dylib appears to be impossible: % otool -L python.exe python.exe:

[issue4472] Is shared lib building broken on trunk for Mac OS X?

2008-12-30 Thread Skip Montanaro
Changes by Skip Montanaro : -- title: Is shared lib building broken on trunk? -> Is shared lib building broken on trunk for Mac OS X? ___ Python tracker <http://bugs.python.org/iss

[issue4755] Common path prefix

2008-12-30 Thread Skip Montanaro
Skip Montanaro added the comment: I think we need to recognize the inherent limitations of what we can expect to do. It is perfectly reasonable for a user on Windows to import posixpath and call posixpath.commonpathprefix. The function won't have access to the actual filesystems

[issue4755] Common path prefix

2008-12-26 Thread Skip Montanaro
New submission from Skip Montanaro : os.path.commonprefix returns the common prefix of a list of paths taken character-by-character. This can return invalid paths. For example, os.path.commonprefix(["/export/home/dave", "/etc/passwd"]) will return "/e", which l

[issue3439] create a numbits() method for int and long types

2008-12-17 Thread Skip Montanaro
Changes by Skip Montanaro : -- nosy: -skip.montanaro ___ Python tracker <http://bugs.python.org/issue3439> ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue3439] create a numbits() method for int and long types

2008-12-16 Thread Skip Montanaro
Skip Montanaro added the comment: Regarding the last few posts: * Raymond's implementation, while ugly, provides a completely orthogonal way to test compute numbits, useful in unit tests if nothing else. * Using x >> 1 in a reference implementation is perfectly reasonable

[issue4575] Py_IS_INFINITY defect causes test_cmath failure on x86

2008-12-15 Thread Skip Montanaro
Skip Montanaro added the comment: Took me awhile to locate a SPARC C compiler on our dwindling set of Solaris/SPARC boxes at work, but I eventually found one and got Subversion trunk to compile. test_cmath and test_math both pass with the force_to_memory2 patch. I don't know if I mention

[issue4665] Failure to compile trunk on Solaris10/SPARC using C++ compiler

2008-12-14 Thread Skip Montanaro
New submission from Skip Montanaro : I don't know if the Python source is supposed to be compilable with a C++ compiler or not, but I'm having trouble finding a C compiler on the Solaris10/SPARC machines at work. I decided to give a C++ compiler a whirl: /opt/gnu/bin/c++ -c -

[issue4575] Py_IS_INFINITY defect causes test_cmath failure on x86

2008-12-14 Thread Skip Montanaro
Skip Montanaro added the comment: Mark> Skip, could you give it a try? Works for me on Solaris 10/x86. Based on Roumen's comment I am preparing to try it on Mac OS X/x86 and Solaris 10/sparc. Skip ___ Python tracker <http://bugs.python.or

[issue4620] Memory leak with datetime used with time.strptime

2008-12-11 Thread Skip Montanaro
Skip Montanaro <[EMAIL PROTECTED]> added the comment: A number of people on a number of platforms and versions can't reproduce this. -- resolution: -> works for me stage: -> committed/rejected status: open -> closed ___ Py

[issue3999] Real segmentation fault handler

2008-12-10 Thread Skip Montanaro
Changes by Skip Montanaro <[EMAIL PROTECTED]>: -- nosy: +skip.montanaro ___ Python tracker <[EMAIL PROTECTED]> <http://bugs.python.org/issue3999> ___ __

[issue4620] Memory leak with datetime used with time.strptime

2008-12-10 Thread Skip Montanaro
Skip Montanaro <[EMAIL PROTECTED]> added the comment: Can you reproduce this with a script that does nothing more than while True: myDate = datetime.datetime(*(time.strptime("2008-12-10T14:00:03", "%Y-%m-%dT%H:%M:%S")[:6])) I tried with both Python 2.4.5 on Solaris

[issue4604] close() seems to have limited effect

2008-12-09 Thread Skip Montanaro
Skip Montanaro <[EMAIL PROTECTED]> added the comment: Amaury> - It should use Amaury>self._checkClosed() Amaury> which already raises the same exception with the same message. I think some other places will need this change then. Note that I don't know the io

[issue4587] Need to rework the dbm lib/include selection process

2008-12-09 Thread Skip Montanaro
Skip Montanaro <[EMAIL PROTECTED]> added the comment: Thanks Roumen. Can I get a verdict on this approach from one of the main Python developers? I'm thinking a better way to control this would be to add a --flag to the build command to control the search order.

[issue4604] close() seems to have limited effect

2008-12-09 Thread Skip Montanaro
Changes by Skip Montanaro <[EMAIL PROTECTED]>: -- stage: needs patch -> patch review ___ Python tracker <[EMAIL PROTECTED]> <http://bugs.py

[issue4604] close() seems to have limited effect

2008-12-09 Thread Skip Montanaro
Changes by Skip Montanaro <[EMAIL PROTECTED]>: Removed file: http://bugs.python.org/file12305/iobug.diff ___ Python tracker <[EMAIL PROTECTED]> <http://bugs.pytho

[issue4604] close() seems to have limited effect

2008-12-09 Thread Skip Montanaro
Skip Montanaro <[EMAIL PROTECTED]> added the comment: Here's a minimal patch to BufferedReader.read() which causes the test to pass. I will leave it for smarter people to decided whether or not all the other read() methods need the same test. Added file: http://bugs.python.or

[issue4604] close() seems to have limited effect

2008-12-09 Thread Skip Montanaro
Skip Montanaro <[EMAIL PROTECTED]> added the comment: fixed patch. I'm still a bit clumsy with the assertRaises stuff. Added file: http://bugs.python.org/file12306/iobug.diff ___ Python tracker <[EMAIL PROTECTED]> <http://bugs.

[issue4604] close() seems to have limited effect

2008-12-09 Thread Skip Montanaro
Changes by Skip Montanaro <[EMAIL PROTECTED]>: -- stage: test needed -> needs patch ___ Python tracker <[EMAIL PROTECTED]> <http://bugs.py

[issue4604] close() seems to have limited effect

2008-12-09 Thread Skip Montanaro
Skip Montanaro <[EMAIL PROTECTED]> added the comment: Here's a test case (diff against Lib/test/test_io.py). This fails for me on OS X 10.5.5 with the tip of the py3k branch. -- keywords: +patch Added file: http://bugs.python.org/file12305

[issue4604] close() seems to have limited effect

2008-12-08 Thread Skip Montanaro
New submission from Skip Montanaro <[EMAIL PROTECTED]>: Seems like file.close() in 3.0 isn't much of a barrier to further reading: % python3.0 Python 3.0rc3+ (py3k:67338M, Nov 22 2008, 06:47:23) [GCC 4.0.1 (Apple Inc. build 5465)] on darwin Type "help", "copyright&qu

[issue4587] Need to rework the dbm lib/include selection process

2008-12-08 Thread Skip Montanaro
Changes by Skip Montanaro <[EMAIL PROTECTED]>: Removed file: http://bugs.python.org/file12275/setup.diff ___ Python tracker <[EMAIL PROTECTED]> <http://bugs.pytho

[issue4587] Need to rework the dbm lib/include selection process

2008-12-08 Thread Skip Montanaro
Skip Montanaro <[EMAIL PROTECTED]> added the comment: Roumen> I confirm my expectation: Roumen> in case 'elif cand == "gdbm":' the if statement for "gdbm.h" has to be Roumen> removed. This header don't provide dbm/ndbm compatible

[issue4587] Need to rework the dbm lib/include selection process

2008-12-07 Thread Skip Montanaro
Skip Montanaro <[EMAIL PROTECTED]> added the comment: Roumen, can you take a look at (and try) the attached patch? It uses an environment variable, PYDBMLIBORDER to define the order of libraries to check for dbm build suitability. If not specified it defaults to "nd

[issue4483] Error to build _dbm module during make

2008-12-07 Thread Skip Montanaro
Skip Montanaro <[EMAIL PROTECTED]> added the comment: Skip> I'm beginning to think this area needs more work. Let's leave Skip> this ticket closed. I'll open a new one so we can figure out the Skip> best way to tackle this. http://b

[issue4587] Need to rework the dbm lib/include selection process

2008-12-07 Thread Skip Montanaro
Changes by Skip Montanaro <[EMAIL PROTECTED]>: -- components: +Build nosy: +rpetrov priority: -> normal type: -> behavior versions: +Python 2.6, Python 2.7, Python 3.0, Python 3.1 ___ Python tracker <[EMAIL PROTECTED]> <h

[issue4587] Need to rework the dbm lib/include selection process

2008-12-07 Thread Skip Montanaro
New submission from Skip Montanaro <[EMAIL PROTECTED]>: Fixing issue4483 resulted in adding an extra header file check for gdbm-based header files when the gdbm library was found. This caused problems for Roumen Petrov. In considering the problems he encountered I decided we probably n

[issue4483] Error to build _dbm module during make

2008-12-07 Thread Skip Montanaro
Skip Montanaro <[EMAIL PROTECTED]> added the comment: Roumen> The old if statement was "flat": ... Okay, I understand now. Roumen> The new if statement contain nested if: Roumen> Now the second case is only "self.compiler.find_library_file(lib_dirs

[issue4483] Error to build _dbm module during make

2008-12-07 Thread Skip Montanaro
Skip Montanaro <[EMAIL PROTECTED]> added the comment: Roumen> I'm not sure that recent commits in trunk are correct. Roumen> Please confirm that build of dbm module with "Berkeley DB" is Roumen> deprecated. Can you explain how you think they are incorre

[issue4483] Error to build _dbm module during make

2008-12-06 Thread Skip Montanaro
Skip Montanaro <[EMAIL PROTECTED]> added the comment: Roumen> may be patch is not applied correctly : Roumen> http://svn.python.org/view/python/trunk/setup.py?rev=67614&view=auto Roumen> libraries = gdbm_libs ) ) Roumen> ? exts.append( Extensio

[issue4506] 3.0 make test failures on Solaris 10

2008-12-06 Thread Skip Montanaro
Skip Montanaro <[EMAIL PROTECTED]> added the comment: > can you come up with a configure patch that would allow isinf to be > detected on Solaris? The plot thickens. I know squat about autoconf sorts of things so I asked on the autoconf mailing list. Eric Drake responded (in p

[issue4483] Error to build _dbm module during make

2008-12-06 Thread Skip Montanaro
Skip Montanaro <[EMAIL PROTECTED]> added the comment: Fix checked in for py3k (r67612), release26-maint (r67613), release30-maint (r67615) branches as well as trunk (r67614). -- resolution: -> fixed status: open -> closed ___ Python tra

[issue3167] math test fails on Solaris 10

2008-12-06 Thread Skip Montanaro
Skip Montanaro <[EMAIL PROTECTED]> added the comment: Mark> Could you try the attached patch to see if it fixes the math.log Mark> and math.log10 test failures. (The patch is generated against the Mark> trunk, but should apply cleanly to py3k or either of the 2.6 o

[issue4506] 3.0 make test failures on Solaris 10

2008-12-05 Thread Skip Montanaro
Skip Montanaro <[EMAIL PROTECTED]> added the comment: Mark> 1. What happens if you build with the '-ffloat-store' option to Mark>gcc? Doesn't quite work: % ./python Python 3.0 (r30:67503, Dec 5 2008, 09:48:42) [GCC 4.2.2] on sunos5 Type &q

[issue4483] Error to build _dbm module during make

2008-12-04 Thread Skip Montanaro
Skip Montanaro <[EMAIL PROTECTED]> added the comment: Andrew> ImportError: No module named math Andrew> make: *** [sharedmods] Error 1 Andrew> The has_function source in Lib/distutils/ccompiler.py has this Andrew> comment: Andrew> # this can't b

[issue4483] Error to build _dbm module during make

2008-12-04 Thread Skip Montanaro
Skip Montanaro <[EMAIL PROTECTED]> added the comment: Here's a new version of the patch for Python 3.0. It appends gdbm_compat to the gdbm libs if that's where dbm_firstkey is defined. Please back out the previous patch against setup.py and Modules/_dbmmodule.c and apply t

[issue4483] Error to build _dbm module during make

2008-12-04 Thread Skip Montanaro
Skip Montanaro <[EMAIL PROTECTED]> added the comment: Andrew> I'm running the same distro as Leger and I was having the same Andrew> problem. Now I've applied dbm.diff and with a clean build I'm Andrew> seeing this: ... Andrew> *** WARNING: r

[issue4506] 3.0 make test failures on Solaris 10

2008-12-04 Thread Skip Montanaro
Skip Montanaro <[EMAIL PROTECTED]> added the comment: Mark> Thanks for the assembly code---you're running Solaris on x86! Why Mark> didn't you say so before? :) I'm failry sure I can find a SPARC here to run it on as well. They are rather few an

[issue4506] 3.0 make test failures on Solaris 10

2008-12-04 Thread Skip Montanaro
Changes by Skip Montanaro <[EMAIL PROTECTED]>: Added file: http://bugs.python.org/file12220/cmathmodule.S.printf ___ Python tracker <[EMAIL PROTECTED]> <http://bugs.pytho

[issue4506] 3.0 make test failures on Solaris 10

2008-12-04 Thread Skip Montanaro
Skip Montanaro <[EMAIL PROTECTED]> added the comment: Mark, I trimmed down cmathmodule.c to just contain c_exp then generated assembler files for the non-printf and printf cases. Perhaps that will help you see what's going on. Skip Added file: http://bugs.python.org/file12219/cm

[issue4506] 3.0 make test failures on Solaris 10

2008-12-04 Thread Skip Montanaro
Skip Montanaro <[EMAIL PROTECTED]> added the comment: Mark> If you have time, could you try the attached patch and report what Mark> gets printed when cmath.exp(710+1.5j) is called? On my machine, I Mark> get: ... Looks similar here: % ./python Python 3.0

[issue4507] 3.0 test failure on Mac OS X 10.5.5

2008-12-03 Thread Skip Montanaro
New submission from Skip Montanaro <[EMAIL PROTECTED]>: After seeing test failures on Solaris 10 (issue4506) I decided to give Mac OS X a whirl. Got one test failure: test test_cmd_line failed -- Traceback (most recent call last): File "/Users/skip/src/Python-3

[issue4506] 3.0 make test failures on Solaris 10

2008-12-03 Thread Skip Montanaro
Skip Montanaro <[EMAIL PROTECTED]> added the comment: Mark> I think you brought up the math and cmath errors before, and I Mark> never managed to get to the bottom of the problem. I'll have Mark> another go. I vaguely remember something about that. If I can be a

[issue4506] 3.0 make test failures on Solaris 10

2008-12-03 Thread Skip Montanaro
New submission from Skip Montanaro <[EMAIL PROTECTED]>: I downloaded the 3.0 tarfile and did a straightforward configure make make test on Solaris 10 and got several test failures: 290 tests OK. 4 tests failed: test_cmath test_math test_posix test_subp

[issue4483] Error to build _dbm module during make

2008-12-02 Thread Skip Montanaro
Skip Montanaro <[EMAIL PROTECTED]> added the comment: Frederic> From the tar 3.0rc3 I apply the patch (dbm.diff). Configure Frederic> ... and make. But the result is always wrong : > "Failed to build these modules: > _dbm" Why does it fail? Is there

[issue4483] Error to build _dbm module during make

2008-12-02 Thread Skip Montanaro
Skip Montanaro <[EMAIL PROTECTED]> added the comment: Leger> - I modify your dbm2.diff because the module name is Leger> "_dbmmodule.c" and not "dbmmodule.c". I think you missed the point of the dbm2.diff file. It should be applied to the Python 2.x code,

[issue4483] Error to build _dbm module during make

2008-12-01 Thread Skip Montanaro
Skip Montanaro <[EMAIL PROTECTED]> added the comment: Here's a similarly untested patch for Python 2.x. Can you try it as well? Added file: http://bugs.python.org/file12182/dbm2.diff ___ Python tracker <[EMAIL PROTECTED]> <http://bugs.

[issue4483] Error to build _dbm module during make

2008-12-01 Thread Skip Montanaro
Skip Montanaro <[EMAIL PROTECTED]> added the comment: Can you try the attached patch and let us know if it works for you? -- assignee: -> skip.montanaro keywords: +easy, patch Added file: http://bugs.python.org/file12181/dbm.diff ___ Pytho

[issue4483] Error to build _dbm module during make

2008-12-01 Thread Skip Montanaro
Skip Montanaro <[EMAIL PROTECTED]> added the comment: Patching _dbmmodule.c alone isn't sufficient. At minimum setup.py would have to be adjusted to detect the presence of the odd ndbm.h file. -- nosy: +skip.montanaro ___ Python trac

[issue4477] Speed up PyEval_EvalFrameEx when tracing is off.

2008-12-01 Thread Skip Montanaro
Changes by Skip Montanaro <[EMAIL PROTECTED]>: -- nosy: +skip.montanaro ___ Python tracker <[EMAIL PROTECTED]> <http://bugs.python.org/issue4477> ___ __

[issue4472] Is shared lib building broken on trunk?

2008-11-30 Thread Skip Montanaro
New submission from Skip Montanaro <[EMAIL PROTECTED]>: I have tried several different combinations of configure args on my Mac in the past couple days in a so far fruitless attempt to generate a libpython.2.7.dylib file. All it will ever generate is a .a file. I've come to the conc

[issue3799] Byte/string inconsistencies between different dbm modules

2008-11-24 Thread Skip Montanaro
Skip Montanaro <[EMAIL PROTECTED]> added the comment: Brett> I still need a review for doc_dbm_strings.diff, though, which Brett> clarifies the docs, fixes one oversight in dbm.dumb, and extends Brett> testing to make sure strings can be accepted. Was my co

[issue4409] Dangling asterisks in Python 3.0 subprocess docs

2008-11-24 Thread Skip Montanaro
New submission from Skip Montanaro <[EMAIL PROTECTED]>: Georg, I just noticed that there are asterisks in a couple places in the subprocess module documentation which don't appear to have corresponding footnotes. All the way at the bottom are subsections called Replaci

[issue4194] default subprocess.Popen buffer size

2008-11-24 Thread Skip Montanaro
Skip Montanaro <[EMAIL PROTECTED]> added the comment: Victor> About Python3, os.popen() is more than two times faster (0.20 Victor> sec vs 0.50 sec) than subprocess.Popen()! It's amazing because Victor> popen() opens the standard output as unicode file whereas Vic

[issue3799] Byte/string inconsistencies between different dbm modules

2008-11-22 Thread Skip Montanaro
Skip Montanaro <[EMAIL PROTECTED]> added the comment: py3k patched with specify_open_encoding.diff passes test_dbm_dumb on my Mac (Leopard, Intel). Might as well assign this to Brett. He seems to be doing all the heavy lifting anyway. ;-) Skip -- assignee: -> bre

[issue3799] Byte/string inconsistencies between different dbm modules

2008-11-21 Thread Skip Montanaro
Skip Montanaro <[EMAIL PROTECTED]> added the comment: One doc nit: There is still reference to ``gdbm`` and Dbm (or dbm) objects when they should probably use ``dbm.gnu`` and ``dbm.ndbm``, respectively. I'm confused by the encoding="Latin-1" args to _io.open for dbm.dumb.

[issue3799] Byte/string inconsistencies between different dbm modules

2008-11-21 Thread Skip Montanaro
Skip Montanaro <[EMAIL PROTECTED]> added the comment: Brett> In other words I think my solution works and pickle is the Brett> trouble-maker in all of this. I can buy that. Should pickle map "copy_reg" to "copyreg"? Is that the only incompatibility? Actua

[issue3799] Byte/string inconsistencies between different dbm modules

2008-11-21 Thread Skip Montanaro
Changes by Skip Montanaro <[EMAIL PROTECTED]>: Added file: http://bugs.python.org/file12096/mydb3read.py ___ Python tracker <[EMAIL PROTECTED]> <http://bugs.pytho

[issue3799] Byte/string inconsistencies between different dbm modules

2008-11-21 Thread Skip Montanaro
Skip Montanaro <[EMAIL PROTECTED]> added the comment: damn... my cc to [EMAIL PROTECTED] didn't work. Here's the recap (message to python-checkins): me> ... I thought Guido was of the opinion that the 3.0 version should me> be able to read dumb dbms written by e

[issue2306] Update What's new in 3.0

2008-11-21 Thread Skip Montanaro
Changes by Skip Montanaro <[EMAIL PROTECTED]>: -- nosy: +skip.montanaro ___ Python tracker <[EMAIL PROTECTED]> <http://bugs.python.org/issue2306> ___ __

[issue1108] Problem with doctest and decorated functions

2008-11-18 Thread Skip Montanaro
Changes by Skip Montanaro <[EMAIL PROTECTED]>: -- stage: patch review -> committed/rejected ___ Python tracker <[EMAIL PROTECTED]> <http://bugs.py

[issue1108] Problem with doctest and decorated functions

2008-11-18 Thread Skip Montanaro
Skip Montanaro <[EMAIL PROTECTED]> added the comment: I applied this patch to my trunk sandbox. It seems to solve the problem I just encountered where doctests are hidden in decorated functions & tests pass. Checked in as r67277. Should be backported to 2.6 and forward por

[issue4111] Add DTrace probes

2008-11-13 Thread Skip Montanaro
Skip Montanaro <[EMAIL PROTECTED]> added the comment: Brett> http://www.opensource.apple.com/darwinsource/10.5.5/python-30.1.2/ ... Brett> http://cvs.opensolaris.org/source/xref//jds/spec-files/trunk/patches/Python-07-dtrace.diff Thanks for the pointers. I'll work on

[issue4111] Add DTrace probes

2008-11-12 Thread Skip Montanaro
Skip Montanaro <[EMAIL PROTECTED]> added the comment: Brett> They have released the changes, that's what my patch (attached to Brett> the issue) is based on. I see the reference to Apple in your original post, but can't find anything related to dtrace & python star

[issue4111] Add DTrace probes

2008-11-12 Thread Skip Montanaro
Skip Montanaro <[EMAIL PROTECTED]> added the comment: It appears that Apple has dtracified their Python exeutable in Leopard. Any chance that they can be persuaded to release a patch? I'm working on a patch (based on some work from a friend at work), but it seems like Apple already

[issue4111] Add DTrace probes

2008-11-12 Thread Skip Montanaro
Changes by Skip Montanaro <[EMAIL PROTECTED]>: -- nosy: +skip.montanaro ___ Python tracker <[EMAIL PROTECTED]> <http://bugs.python.org/issue4111> ___ __

<    1   2   3   4   5   6   7   8   9   >