Hey everybody,
I need help/advice for this JyNI-related issue:
https://github.com/Stewori/JyNI/issues/4
Especially I need advice from someone familiar with TCL and TK internals,
preferably also Tkinter.
The issue is rather strange in the sense that it works well on Linux, while the
program hang
On Mon, 4 Apr 2016 at 14:05 Terry Reedy wrote:
> On 3/29/2016 7:30 PM, Martin Panter wrote:
> > For the last ~36 hours I have stopped receiving emails for messages
> > posted in the bug tracker. Is anyone else having this problem? Has
> > anything changed recently?
>
> My udel dot edu account is
On 3/29/2016 7:30 PM, Martin Panter wrote:
For the last ~36 hours I have stopped receiving emails for messages
posted in the bug tracker. Is anyone else having this problem? Has
anything changed recently?
My udel dot edu account is handled by google. I am also not getting
anything at all, not
Agreed, let's go with two macros. The time discussing this further
could be spent more productively.
On Mon, Apr 4, 2016 at 2:35 AM, Victor Stinner wrote:
> If some dev don't want to use the single macro for good or bad reasons, it's
> maybe better to have two macros to generalize their usage. Th
On 4 April 2016 at 20:04, Robert Collins wrote:
> I'm working on teaching funcsigs - the backport of inspect.signature -
> better handling for wrapped functions, and the key enabler to do that
> is capturing the wrapped function in __wrapped__. I'm wondering what
> folks thoughts are on backportin
I'm working on teaching funcsigs - the backport of inspect.signature -
better handling for wrapped functions, and the key enabler to do that
is capturing the wrapped function in __wrapped__. I'm wondering what
folks thoughts are on backporting that to 2.7 - seems cleaner than
monkeypatching functoo
If some dev don't want to use the single macro for good or bad reasons,
it's maybe better to have two macros to generalize their usage. The macro
makes to C code shorter and easier to review.
Victor
___
Python-Dev mailing list
Python-Dev@python.org
https
On 3 April 2016 at 17:32, Serhiy Storchaka wrote:
> Originally I proposed a pair of macros for safe reference replacing to
> reflects the duality of Py_DECREF/Py_XDECREF. [1], [2] The one should use
> Py_DECREF and the other should use Py_XDECREF.
>
> But then I got a number of voices for the sin
