Myron Walker added the comment:
I am adding a Github PR for this issue.
--
___
Python tracker
<https://bugs.python.org/issue47063>
___
___
Python-bugs-list m
New submission from Myron Walker :
SimpleHTTPRequestHandler has hard coded index page list in the send_head
method. The fixed hard-coded list means that if you want to have a custom
index page that is not named "index.htm" or "index.html" then you have to
override
Myron Walker added the comment:
Looks like this is fixed in the latest source code.
--
stage: -> resolved
status: open -> closed
___
Python tracker
<https://bugs.python.org/i
New submission from Myron Walker :
When you have an xml document like the one with a default namespace below.
When you try to lookup nodes in the document they are not found.
```
docTree.find("specVersion")
None
```
If you add a namespaces map with the '' key and the default names
New submission from Myron Walker:
The 'ast' module does not indicate the type of string, ''' or '"' or '"""',
that it has encountered when it parses a python document.
This prevents accurate reproduction of the original parsed document by a writer
walking over an instance
Myron Walker added the comment:
My thought on this is that a syntax tree needs to accurately represent parsed
syntax of the code. Two strings being concatenated contain syntax information
that is different from a single string.
"Hello" + " World"
Is not the same syntax
Myron Walker added the comment:
I am re-opening this as I believe this is an important issue for work I would
like to eventually push into the python core which is python code that recode
themselves as declarations or as instance representation.
"I don't see any benefit in suppo
New submission from Myron Walker:
ast module is combining string literals that are concatenated with plus
operator into a single string in the parsestrplus module rather than
maintaining the true syntax tree of the original document.
The fact that ast combines strings and does not maintain
Myron Walker added the comment:
The purpose of a syntax tree is to represent the syntax and not a final
processed result of processing of syntax. The current information stored for
strings is losing syntax information which seems to defeat the purpose of
offering the information in a syntax
Myron Walker added the comment:
Would it be prudent to add a Parse flag to the AST module that could provide
one of two types of AST's an optimized AST or a complete AST
--
___
Python tracker <rep...@bugs.python.org>
<http://bugs.p
Myron Walker added the comment:
Found this with code inspection
--
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/issue25716>
___
___
Myron Walker added the comment:
I think this usage of 'call_method' from typeobject.c would cause it to leak.
static PyObject*
slot_sq_slice(PyObject *self, Py_ssize_t i, Py_ssize_t j)
{
static PyObject *getslice_str;
if (PyErr_WarnPy3k("in 3.x, __getslice__ has been re
Myron Walker added the comment:
I'll file a seperate bug on 'countformat'
--
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/i
New submission from Myron Walker:
'countformat' does not appear to be handling the case where a format string is
passed with no parenthesis or brackets correctly. Here is an
example of a usage that might cause issues from typedobject.c:
static PyObject*
slot_sq_slice(PyObject *self, Py_ssize_t
Myron Walker added the comment:
There is not reproducer for this currently.
Its a case of implied or shared usage between a function and the code that uses
it. This function is only used in the Python core, so unless
it is used incorrectly, by a python extension or modification, it may never
Myron Walker added the comment:
There are format string like "O&" being passed in to Py_BuildValue
which eventually make their way to 'countformat'. It looks like it would just
break after the first & and not count anything else. So Im not sure it gives
Myron Walker added the comment:
Yes, there are some other cases that look odd to me as if the code is not up to
date though. I was looking at the documentation and it mentions format
character combinations like 'es' which contain two characters sequences. When
I look at this function
New submission from Myron Walker:
The 'call_method' and 'call_maybe' function in typeobject.c are leaking
a reference on 'func' in cases where 'args == NULL'. In this case both
of these functions exit like so:
if (args == NULL)
return NULL;
When they need to do:
if (args
Changes by Myron Walker <myron.wal...@gmail.com>:
--
versions: +Python 3.2, Python 3.3, Python 3.4, Python 3.5, Python 3.6
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python
19 matches
Mail list logo
