Change by Yannick Jadoul :
--
nosy: +YannickJadoul
___
Python tracker
<https://bugs.python.org/issue43367>
___
___
Python-bugs-list mailing list
Unsubscribe:
Change by Yannick Jadoul :
--
nosy: +YannickJadoul
___
Python tracker
<https://bugs.python.org/issue43145>
___
___
Python-bugs-list mailing list
Unsubscribe:
Change by Yannick Jadoul :
--
nosy: +YannickJadoul
___
Python tracker
<https://bugs.python.org/issue42961>
___
___
Python-bugs-list mailing list
Unsubscribe:
Yannick Jadoul added the comment:
Wow, that was fast! Thanks!
I tried this out locally, and all pybind11's tests pass now. We can try again
once there's a nightly build or new alpha :-)
--
___
Python tracker
<https://bugs.python.org/issue42
New submission from Yannick Jadoul :
Issue detected in the embedding tests of pybind11, running on the latest alpha
of 3.10: https://github.com/pybind/pybind11/issues/2774
I have reduced the weird issue/crash to a minimal reproducer, which
consistently reproduces the crash on my Linux
Yannick Jadoul added the comment:
Yes, sorry for the delay; I got caught up in something else.
Meanwhile, https://github.com/python/cpython/pull/22670 should solve our
issues. I think Henry confirmed this locally?
--
___
Python tracker
<ht
Change by Yannick Jadoul :
--
keywords: +patch
pull_requests: +21643
stage: -> patch review
pull_request: https://github.com/python/cpython/pull/22670
___
Python tracker
<https://bugs.python.org/issu
New submission from Yannick Jadoul :
In Python 3.9, the line `Py_XDECREF(PyCFunction_GET_CLASS(m));` was added to
`meth_dealloc` (in `methodobject.c`). Unfortunately for pybind11, it's inserted
exactly two lines too low, since it accesses the `PyMethodDef` and we store the
`PyMethodDef
Yannick Gingras added the comment:
Raymond, I would love to submit the PR if we reach a consensus on what the new
message should be. I'm a bit out of touch with how things work these days. Is
Github the best place to submit the PR?
Paul, very good digging! Reading the coding and running
New submission from Yannick Gingras :
In argparse.rst, while documenting ArgumentParser.add_subparsers, ``prog`` is
described on line 1630 as:
usage information that will be displayed with sub-command help,
by default the name of the program and any positional arguments
before
New submission from Yannick :
Python version: 3.5
Tested with VS Studio 2017 in an C-API extension.
When you have a UTF-8 encoded char buffer which is filled with a 0 or empty,
and you youse the PyUnicode_FromString() method on this buffer, you will get a
PyObject*. The content looks good
New submission from Yannick Brehon:
If one defines a mock for a function, using autospec=True, then the mock will
correctly support assert_called_once_with(), among others, but not
assert_called_once, assert_called, and assert_not_called.
The attached file contains a fix for the issue
Yannick Duchêne added the comment:
The documentation says:
> Reset the instance. Loses all unprocessed data.
How can parsing go ahead with all unprocessed data lost? This is the “Loses all
unprocessed data” which made me believe it is to stop it.
May be the documentation is uncl
Yannick Duchêne added the comment:
`reset` is called to stop the parser.
If really `reset` should not be called during parser hooks execution, then the
documentation should says so and an error should be raised when `reset` is
invoked
Yannick Duchêne added the comment:
Thanks Xiang, for the clear explanations.
So an error should be triggered when `reset` is invoked while it should not.
And remains the issue about how to stop the parser: should an exception be
raised and caught at an outer invocation level? Something like
Yannick Duchêne added the comment:
> And I don't see how to stop the process either.
I just did it with `raise StopIteration`, caught at a proper place (in the
procedure which invokes `feed` and `close`), and it seems to be fine, I have no
more strange behaviours. At least, I cannot
Yannick Duchêne added the comment:
I'm closing this issue, as the the issue http://bugs.python.org/issue26210 is
the real one and this one seems to be a variant of the former.
--
status: open -> closed
___
Python tracker <rep...@bugs.pyth
Changes by Yannick Duchêne <yannick_duch...@yahoo.fr>:
--
nosy: +ezio.melotti
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python
New submission from Yannick Duchêne:
`HTMLParser.handle_data` may be invoked although `HTMLParser.reset` was
invoked. This occurs at least when `HTMLParser.reset` was invoked during
`HTMLParser.handle_endtag`.
According to the documentation, `HTMLParser.reset` discard all data, so it
should
New submission from Yannick Duchêne:
Using HTMLParser on the attached file, I got this:
File "/usr/lib/python3.5/html/parser.py", line 111, in feed
self.goahead(0)
File "/usr/lib/python3.5/html/parser.py", line 171, in goahead
k = self.parse_st
Yannick Duchêne added the comment:
Better at least two, if I'm not wrong: the innermost scope may be the module's
scope. So there is always at least the module scope and the built‑ins scope, at
least two up to four.
(if I have not overlooked something)
--
nosy: +Hibou57
New submission from Yannick Duchêne:
`make test` fails with Python 3.4.1 on Ubuntu 12.04 Intel 32 bits.
The single `./configure` option used, was `--prefix=$HOME/.local`.
As attached file, an archive containing both standard output and standard error
outputs.
Not some important error
Yannick Gingras yging...@ygingras.net added the comment:
The attached patch is a proof of concept for throwing an exception.
As discussed on the mailing list [1], it has some shortcomings that
should be addressed before it is merged.
[1]: http://mail.python.org/pipermail/python-dev/2009
New submission from Yannick Gingras [EMAIL PROTECTED]:
EnvironmentError and its subclass OSError add the value of errno in
their error message. This value is an integer but the specific value
in an implementation detail and the C runtime recommends that
programmers use the symbolic values
24 matches
Mail list logo
