New submission from Peter Eisentraut :
object.h contains an inline function that causes a -Wcast-qual warning from
gcc. Since this file ends up visible in third-party code that includes
Python.h, this makes it impossible to use -Wcast-qual in such code.
The problem is the change
Peter Eisentraut added the comment:
3.9.0a5 fixes my original issue. Thanks.
--
___
Python tracker
<https://bugs.python.org/issue39615>
___
___
Python-bug
Peter Eisentraut added the comment:
That's fair for code internal to CPython itself, but these are header files
included by third-party code that is embedding Python, so a bit more
flexibility and adaptability would be welcome
Change by Peter Eisentraut :
--
keywords: +patch
pull_requests: +17851
stage: -> patch review
pull_request: https://github.com/python/cpython/pull/18481
___
Python tracker
<https://bugs.python.org/issu
New submission from Peter Eisentraut :
Some inline functions use mixed declarations and code. These end up visible in
third-party code that includes Python.h, which might not be using a C99
compiler.
Example:
In file included from
/Users/peter/python-builds/3.9/include/python3.9
Peter Eisentraut added the comment:
I understand the reasoning here, but I want to say booh to this change in
3.6.0a2 because it breaks my tests. It used to be that type(x) returned a
predictable string, and that was an easy way to verify the result types of
things.
Perhaps a __str__
Peter Eisentraut added the comment:
The affected tar is indeed a BSD-ish tar (OS X). With GNU tar I can proceed.
It says "gtar: Removing leading `../' from member names".
So with that I agree that it's not worth rerolling th
New submission from Peter Eisentraut:
The file Python-3.6.0a2.tgz contains paths that start with "..", e.g.,
$ tar tf Python-3.6.0a2.tgz | head
../Python-3.6.0a2/
../Python-3.6.0a2/Doc/
../Python-3.6.0a2/Grammar/
../Python-3.6.0a2/Include/
../Python-3.6.0a2/LICENSE
../Python-3
Peter Eisentraut added the comment:
No, the second use should not be converted.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue11122
Changes by Peter Eisentraut pete...@gmx.net:
--
nosy: +petere
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue444582
___
___
Python-bugs-list
Peter Eisentraut added the comment:
I ran into a similar instance of this problem today and would like to add my
support for just getting rid of the rpm calls and just call rpmbuild in all
cases. The last release where rpm was used for building was more than 10
years ago.
--
nosy
New submission from Peter Eisentraut:
The documentation for the csv.DictReader constructor is
.. class:: DictReader(csvfile, fieldnames=None, restkey=None, restval=None,
dialect='excel', *args, **kwds)
but the implementation is
def __init__(self, f, fieldnames=None, restkey=None, restval
New submission from Peter Eisentraut pete...@gmx.net:
The environment variable PYTHONWARNINGS only works with the python interpreter
binary, but not with programs embedding libpython. This could be changed by
moving the code from Modules/main.c to Python/pythonrun.c. See attached patch
New submission from Peter Eisentraut pete...@gmx.net:
DeprecationWarning was disabled by default in Python 2.7, but the documentation
section Default Warning Filters does not list it as ignored. In the 3.x
branches, this was already fixed. Trivial patch attached.
--
assignee: docs
Peter Eisentraut pete...@gmx.net added the comment:
Attached is a test file. The key here is that I'm running the unittest suite
inside of a long-running server process, so there is no predictable point of
exit and cleanup. Therefore, the steps I show at the end of the file should be
run
New submission from Peter Eisentraut pete...@gmx.net:
I'm using the TextTestRunner class in unittest/runner.py with a special
file-like object passed in as stream. Doing this loses some output, because
the run() method (and some lower-level methods) don't always call flush() on
the stream
New submission from Peter Eisentraut pete...@gmx.net:
The existing documentation index entries for * and ** only point to their use
in function definitions but not to their use in function calls. I was looking
for the latter, and it was difficult to find without this. Here is a small
patch
New submission from Peter Eisentraut pete...@gmx.net:
It appears to be a pretty common mistake to think that the argument of
str.strip/lstrip/rstrip is a substring rather than a set of characters. To
allow a more clearer notation, it would be nice if these functions also
accepted an argument
Changes by Peter Eisentraut pete...@gmx.net:
--
nosy: +petere
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue12012
___
___
Python-bugs-list mailing
New submission from Peter Eisentraut pete...@gmx.net:
When setting Py_LIMITED_API, functions such as PyUnicode_Check() can no longer
be used. Example:
#define Py_LIMITED_API
#include Python.h
void foo()
{
PyObject *o;
PyUnicode_Check(o);
}
test.c: In function ‘foo’:
test.c:9
Peter Eisentraut pete...@gmx.net added the comment:
For what it's worth, the code in question is used here (using import
distutils instead of pass):
http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/config/python.m4?rev=1.15;content-type=text%2Fx-cvsweb-markup
This is obviously a completely
New submission from Peter Eisentraut pete...@gmx.net:
bash$ python3.1 -c 'pass' 2-
Aborted (core dumped)
(I verified, the core dump belongs to python.)
If you remove the redirection thingy at the end, it works.
Not sure why I ever wrote that code, but it has been working since
forever up
22 matches
Mail list logo
