[issue13829] exception error in _scproxy.so

2013-02-18 Thread Julian Scheid
Julian Scheid added the comment: FWIW, I've run into the same issue in a homegrown application with 2.6.8, 2.7.2 and 2.7.3 (these were the only versions I've tested). Looking around a little bit, I suspect this might be a bug in SCDynamicStoreCopyProxies that's only present o

[issue7490] IGNORE_EXCEPTION_DETAIL should ignore the module name

2010-04-15 Thread Julian Scheid
Julian Scheid added the comment: Hmm, wait. Here's a variation of your suggestion that works OK-ish even as an example: >>> try: ...# ... code that fails ... ... except mypkg.MyException, e: ...print(str(e)) Expected error message. This works because it omits the exc

[issue7490] IGNORE_EXCEPTION_DETAIL should ignore the module name

2010-04-15 Thread Julian Scheid
Julian Scheid added the comment: Thank you for the suggestion but in my mind that's not a viable workaround, and not just because of uglyness: I'm using doctest to validate code examples, which are included in the documentation and are meant to be educational. If I'd change

[issue7490] IGNORE_EXCEPTION_DETAIL should ignore the module name

2010-04-15 Thread Julian Scheid
Julian Scheid added the comment: Ah, right... so there is no easy workaround at present? -- ___ Python tracker <http://bugs.python.org/issue7490> ___ ___ Pytho

[issue7490] IGNORE_EXCEPTION_DETAIL should ignore the module name

2010-04-15 Thread Julian Scheid
Julian Scheid added the comment: Here's a better example that you can cut and paste. import optparse def foo(): """ >>> foo() #doctest: +ELLIPSIS Traceback (most recent call last): . . . ...OptionError: option bar: foo "&quo

[issue7490] IGNORE_EXCEPTION_DETAIL should ignore the module name

2010-04-15 Thread Julian Scheid
Julian Scheid added the comment: Having this in 2.6/2.7 would be great. I don't think the ELLIPSIS workaround suggested by Barry works, have you actually tried it? Below is an example where ELLIPSIS doesn't seem to help (run in 2.6.5). I have also tried "...Error:" a

[issue3646] MacOS X framework install to non-standard directory fails

2009-04-09 Thread Julian Scheid
Julian Scheid added the comment: On second thought, are you sure that's how fullinstall is meant to work? If I use frameworkinstall I get the following message at the end: * Note: not installed as 'python'. * Use 'make fullinstall' to install as 'python'

[issue3646] MacOS X framework install to non-standard directory fails

2009-04-09 Thread Julian Scheid
Julian Scheid added the comment: Ah, that makes sense - thanks for clarifying. And I was mistaken about 2.6, the no-suffix symlinks are there in $PREFIX/bin so all is good. Let me know what you think of the patch when you get a chance to look at it

[issue3646] MacOS X framework install to non-standard directory fails

2009-04-09 Thread Julian Scheid
Julian Scheid added the comment: I was a bit surprised myself but I've just double-checked and it seems to work fine. I started with a freshly unpacked 3.0.1 tarball and used the following command: ./configure --enable-toolbox-glue --enable-universalsdk --enable-framework=/tmp/python-

[issue3646] MacOS X framework install to non-standard directory fails

2009-04-09 Thread Julian Scheid
Julian Scheid added the comment: I had a hunch that might be the case. I'm still planning to upload them here for the benefit of others who, like me, have to maintain those versions as framework installs. Is that OK? -- ___ Python tracker

[issue3646] MacOS X framework install to non-standard directory fails

2009-04-09 Thread Julian Scheid
Julian Scheid added the comment: Attached a fix for release26-maint branch. I've tested this as follows: ./configure --enable-toolbox-glue --enable-universalsdk --enable-framework=/tmp/python-2.6-maint-install/Library/Framework --prefix=/tmp/python-2.6-maint-install && mak

[issue3646] MacOS X framework install to non-standard directory fails

2009-04-09 Thread Julian Scheid
Julian Scheid added the comment: Actually this seems to be fixed in 3.0.1 - yay! -- versions: -Python 3.0 ___ Python tracker <http://bugs.python.org/issue3

[issue3646] MacOS X framework install to non-standard directory fails

2009-04-09 Thread Julian Scheid
Julian Scheid added the comment: The same issue is present in 2.4 and 2.5 as well as 3.0 so I'm updating this issue accordingly (haven't tried 2.7 or 3.1). I've been working around this issue with some success and will be posting patches shortly. -- nosy: +julians37 ve