[issue7330] PyUnicode_FromFormat: implement width and precision for %s, %S, %R, %V, %U, %A

2011-10-09 Thread lekma
Changes by lekma : -- nosy: +lekma ___ Python tracker <http://bugs.python.org/issue7330> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.pyth

[issue10271] warnings.showwarning should allow any callable object

2011-07-20 Thread lekma
lekma added the comment: Thank you very much for your help -- ___ Python tracker <http://bugs.python.org/issue10271> ___ ___ Python-bugs-list mailing list Unsub

[issue10271] warnings.showwarning should allow any callable object

2010-10-31 Thread lekma
New submission from lekma : Overriding warnings.showwarning() with a c/python module function (from a c/python module) doesn't work because warn_explicit() only allow PyFunction or PyMethod objects to be called (unfortunately c/python module functions are of type PyCFunction). Sugg

[issue10271] warnings.showwarning should allow any callable object

2011-04-17 Thread lekma
lekma added the comment: - split the patch between the actual fix and the test - rewrote the test a little bit (I'm not sure it's even needed, hence the split) - rediff against 3.3 (should still apply cleanly on top of 3.2 (modulo offset)) -- versions: +Python 3.3 Added

[issue10271] warnings.showwarning should allow any callable object

2011-04-17 Thread lekma
Changes by lekma : Added file: http://bugs.python.org/file21695/Issue10271.33.test.diff ___ Python tracker <http://bugs.python.org/issue10271> ___ ___ Python-bugs-list m

[issue10271] warnings.showwarning should allow any callable object

2011-05-18 Thread lekma
lekma added the comment: Is there anything else I should be doing? -- ___ Python tracker <http://bugs.python.org/issue10271> ___ ___ Python-bugs-list mailin

[issue10271] warnings.showwarning should allow any callable object

2011-05-20 Thread lekma
lekma added the comment: how should we go about that? -- ___ Python tracker <http://bugs.python.org/issue10271> ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue10271] warnings.showwarning should allow any callable object

2011-02-02 Thread lekma
Changes by lekma : -- keywords: +patch Added file: http://bugs.python.org/file20647/Issue10271.diff ___ Python tracker <http://bugs.python.org/issue10271> ___ ___

[issue10271] warnings.showwarning should allow any callable object

2011-02-04 Thread lekma
lekma added the comment: brett, is there any chance for this to make it in? -- ___ Python tracker <http://bugs.python.org/issue10271> ___ ___ Python-bugs-list m

[issue32414] PyCapsule_Import fails when name is in the form 'package.module.capsule'

2018-04-30 Thread lekma
lekma added the comment: thinking out loud here: maybe both behavior can be exposed, i.e. a PyCapsule_Import that would expect a valid import statement and a Py_GetCapsule that would behave more like getattr? -- ___ Python tracker <ht

[issue33391] leak in set_symmetric_difference?

2018-04-30 Thread lekma
New submission from lekma : shouldn't otherset be decrefed before returning on error in set_symmetric_difference? if not, what am I missing? -- components: Interpreter Core files: setobject.c.diff keywords: patch messages: 315945 nosy: lekma priority: normal severity: normal s

[issue33391] leak in set_symmetric_difference?

2018-04-30 Thread lekma
Change by lekma : -- pull_requests: +6365 stage: -> patch review ___ Python tracker <https://bugs.python.org/issue33391> ___ ___ Python-bugs-list mai

[issue33391] leak in set_symmetric_difference?

2018-04-30 Thread lekma
lekma added the comment: > Good catch! Do you mind to create a pull request on GitHub? done -- ___ Python tracker <https://bugs.python.org/issue33391> ___ _

[issue33391] leak in set_symmetric_difference?

2018-05-01 Thread lekma
Change by lekma : -- pull_requests: +6366 ___ Python tracker <https://bugs.python.org/issue33391> ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue33391] leak in set_symmetric_difference?

2018-05-01 Thread lekma
Change by lekma : -- pull_requests: +6367 ___ Python tracker <https://bugs.python.org/issue33391> ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue32414] PyCapsule_Import fails when name is in the form 'package.module.capsule'

2017-12-23 Thread lekma
New submission from lekma : When capsule name is in the form 'package.module.capsule', PyCapsule_Import fails with an AttributeError (module is never an attribute of package). -- components: Interpreter Core messages: 308950 nosy: lekma priority: normal severity: normal st

[issue32414] PyCapsule_Import fails when name is in the form 'package.module.capsule'

2017-12-24 Thread lekma
lekma added the comment: > PR 4988 will break the case 'module.attr.capsule' if 'module.attr' is > not a module. you are right, but is that a case you would expect in an import statement? -- ___ Python tracker <https

[issue33659] leak in pythonrun.c?

2018-05-27 Thread lekma
New submission from lekma : Am I wrong in thinking 'filename_obj' should be decrefed before the last two return statements in set_main_loader()? If yes, what am I missing? -- components: Interpreter Core messages: 317789 nosy: lekma priority: normal severity: normal status:

[issue33659] leak in pythonrun.c?

2018-05-27 Thread lekma
lekma added the comment: sorry, my mistake, I missed the format specifier in PyObject_CallFunction() sorry for the noise -- resolution: -> not a bug stage: -> resolved status: open -> closed ___ Python tracker <https://bugs.python.or

[issue15870] PyType_FromSpec should take metaclass as an argument

2013-01-14 Thread lekma
Changes by lekma : -- nosy: +lekma ___ Python tracker <http://bugs.python.org/issue15870> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.pyth

[issue7033] C/API - Document exceptions

2009-10-02 Thread lekma
New submission from lekma : It would be nice to have an obvious/simple way to document C exceptions (especially when using the autoexception feature from Sphinx). Something along: PyObject *PyErr_Create(char *name, const char *doc) Creates and returns a new exception object. This

[issue7033] C/API - Document exceptions

2009-10-02 Thread lekma
lekma added the comment: First attempt at implementing this. Diff is against trunk. -- keywords: +patch Added file: http://bugs.python.org/file15021/issue7033_trunk.diff ___ Python tracker <http://bugs.python.org/issue7

[issue7033] C/API - Document exceptions

2009-10-02 Thread lekma
lekma added the comment: The same against py3k -- Added file: http://bugs.python.org/file15022/issue7033_py3k.diff ___ Python tracker <http://bugs.python.org/issue7

[issue7033] C/API - Document exceptions

2009-10-04 Thread lekma
lekma added the comment: Even though I don't fully agree with your comments here is a second attempt addressing them, against trunk. For the record, I think that the signature difference is enough to warrant a name that is a clear cut from PyErr_NewException. And in the spirit o

[issue7033] C/API - Document exceptions

2009-10-04 Thread lekma
lekma added the comment: Same as previous against py3k -- Added file: http://bugs.python.org/file15036/issue7033_py3k_2.diff ___ Python tracker <http://bugs.python.org/issue7

[issue3605] Py_FatalError causes infinite loop

2009-10-22 Thread lekma
Changes by lekma : -- nosy: +lekma ___ Python tracker <http://bugs.python.org/issue3605> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.pyth

[issue7523] add SOCK_NONBLOCK and SOCK_CLOEXEC to socket module

2009-12-16 Thread lekma
New submission from lekma : It would be nice to have those. See http://udrepper.livejournal.com/20407.html for background. -- components: Library (Lib) messages: 96482 nosy: lekma severity: normal status: open title: add SOCK_NONBLOCK and SOCK_CLOEXEC to socket module type: feature

[issue7523] add SOCK_NONBLOCK and SOCK_CLOEXEC to socket module

2009-12-16 Thread lekma
lekma added the comment: First attempt, against trunk. -- keywords: +patch Added file: http://bugs.python.org/file15573/Issue7523.diff ___ Python tracker <http://bugs.python.org/issue7

[issue7523] add SOCK_NONBLOCK and SOCK_CLOEXEC to socket module

2009-12-16 Thread lekma
lekma added the comment: better patch (mainly test refactoring). still against trunk. should I provide one against py3k? -- components: +IO Added file: http://bugs.python.org/file15578/Issue7523_2.diff ___ Python tracker <http://bugs.python.

[issue7523] add SOCK_NONBLOCK and SOCK_CLOEXEC to socket module

2009-12-17 Thread lekma
lekma added the comment: > - when importing fcntl, bear in mind that some systems don't have this > module (e.g. Windows), so you should catch and silence the ImportError would something like the following be ok?: try: import fcntl except ImportError: fcntl = False an

[issue7523] add SOCK_NONBLOCK and SOCK_CLOEXEC to socket module

2009-12-19 Thread lekma
lekma added the comment: > It would be better to use test skipping: (eg: @unittest.SkipUnless > before the test class). I didn't know about this feature, thanks for the tip. Now I wonder if it would be better to do it this way: @unittest.SkipUnless(hasattr(socket, "SOCK_CLO

[issue7523] add SOCK_NONBLOCK and SOCK_CLOEXEC to socket module

2009-12-20 Thread lekma
lekma added the comment: this one addresses Antoines's comments (with the help of R. David Murray). -- Added file: http://bugs.python.org/file15621/Issue7523_3.diff ___ Python tracker <http://bugs.python.org/i

[issue7033] C/API - Document exceptions

2009-12-20 Thread lekma
lekma added the comment: Is there any chance that this will make it in? -- ___ Python tracker <http://bugs.python.org/issue7033> ___ ___ Python-bugs-list mailin

[issue7033] C/API - Document exceptions

2009-12-21 Thread lekma
lekma added the comment: patch against trunk: - fix tabs issue (I hope) - add test -- Added file: http://bugs.python.org/file15645/issue7033_trunk_3.diff ___ Python tracker <http://bugs.python.org/issue7

[issue7033] C/API - Document exceptions

2009-12-21 Thread lekma
lekma added the comment: The same with a simpler test. I leave it up to you guys to choose which one is the best. -- Added file: http://bugs.python.org/file15646/issue7033_trunk_3_alt_test.diff ___ Python tracker <http://bugs.python.org/issue7

[issue7033] C/API - Document exceptions

2009-12-28 Thread lekma
lekma added the comment: > Thanks for the patch! I rewrote the C function a bit to also take a dict > argument, and added a test for that. Committed in r77088. Will merge > to py3k. Great! Thanks to all for the help! -- ___ Python track

[issue7033] C/API - Document exceptions

2009-12-29 Thread lekma
lekma added the comment: > lekma, this patch is now listed in the 2.7 "what's new" document as > contributed by "the lekma user", please tell us if you want your name > there. Nope, that's ok (it's perfect). -- _

[issue7523] add SOCK_NONBLOCK and SOCK_CLOEXEC to socket module

2010-01-13 Thread lekma
lekma added the comment: > lekma, do you have a real name that we should add to the ACKS file? no, lekma is fine (that's a nick I carry since childhood) > Looking at it again, there's the question of accept() behaviour. [...] Sorry for not having seen that earlier and thanks

[issue5585] implement initializer for multiprocessing.BaseManager.start()

2009-03-28 Thread lekma
New submission from lekma : It would be useful to have the ability to run arbitrary code before a manager's server subprocess is started (I'd use this feature to install signal handlers for example). -- components: Library (Lib) messages: 84302 nosy: lekma severity: normal st

[issue5585] implement initializer for multiprocessing.BaseManager.start()

2009-03-28 Thread lekma
lekma added the comment: here is a patch doing just that (against trunk). ps: this is my first bug report and contribution to Python, please, be gentle :) -- keywords: +patch Added file: http://bugs.python.org/file13438/Issue5585.patch ___ Python

[issue5585] implement initializer for multiprocessing.BaseManager.start()

2009-03-29 Thread lekma
lekma added the comment: AFAIK there is no equivalent to the managers api in threading. As for the tests, what kind of tests would you like to see? Jesse, some thoughts on that? -- ___ Python tracker <http://bugs.python.org/issue5

[issue5585] implement initializer for multiprocessing.BaseManager.start()

2009-03-30 Thread lekma
lekma added the comment: > Right, it's just the Thread/Process API equivalance. I'm not saying > it's a stopper, but the docs would probably need to be modified > accordingly. I'm a bit confused here. The patch only adds a small feature to BaseManager and subtyp

[issue5585] implement initializer for multiprocessing.BaseManager.start()

2009-03-31 Thread lekma
lekma added the comment: The same against py3k. Jesse, is there any chance that this will make it in, or should I just go and implement a local solution? -- Added file: http://bugs.python.org/file13508/Issue5585_2_py3k.patch ___ Python tracker

[issue5585] implement initializer for multiprocessing.BaseManager.start()

2009-03-31 Thread lekma
lekma added the comment: > I'm thinking about it and plan on discussing it with other core devs > today. Altering the Api is not something done lightly yep. Thanks for considering it. -- ___ Python tracker <http://bugs.python

[issue5585] implement initializer for multiprocessing.BaseManager.start()

2009-04-01 Thread lekma
lekma added the comment: thanks guys -- ___ Python tracker <http://bugs.python.org/issue5585> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.pyth