Stefan Krah added the comment:
I understand that both of you are in favor of #19521 (the patch of
which I have not tried yet).
Can we close this as a duplicate? Please just reopen if you disagree.
--
nosy: +skrah
resolution: -> duplicate
stage: patch review -> resolved
status
Change by Stefan Krah :
--
versions: +Python 3.10 -Python 2.7, Python 3.2, Python 3.3, Python 3.4, Python
3.5, Python 3.6, Python 3.7
___
Python tracker
<https://bugs.python.org/issue19
Change by Stefan Krah :
--
nosy: +BTaskaya, Michael.Felt, kadler, skrah
___
Python tracker
<https://bugs.python.org/issue19521>
___
___
Python-bugs-list mailin
Stefan Behnel added the comment:
> This has to be in a PEP
No, the bug tracker seems fine for this.
--
nosy: +scoder
resolution: not a bug ->
stage: resolved -> needs patch
status: closed -> open
type: -> performance
___
Python
Stefan Behnel added the comment:
What about building the library? The readme says it needs nasm? That's not a
standard dependency for the CPython build currently, which relies solely on a C
compiler.
--
___
Python tracker
&
Stefan Behnel added the comment:
> libdeflate and isa-l use different compression ratio's for the levels.
I don't see why these would need to translate 1:1. The zlib module is a Python
API wrapper, it can do its own mapping here, or use the libraries selectively
only for som
Stefan Krah added the comment:
> That's probably due to a very small size of the Paging Space of the AIX
> machine you used for testing.
That is the case, the machine has 160GB of memory and 1GB of paging space. I
guess it is configured specifically for not freezing.
> About
Stefan Krah added the comment:
Well, I misunderstood this sentence then, so it's just for testing. :)
> Our customers should use it or use ulimit -d.
One will hit this issue also when following the MAX_PREC section
in the FAQ, but that is a rare case:
https://docs.python.org/3.10
Stefan Krah added the comment:
The original patch is a bit dated, do we still need the export symbol
generation?
https://www.ibm.com/support/knowledgecenter/en/SSGH3R_16.1.0/com.ibm.xlcpp161.aix.doc/proguide/compiling_shared_aix.html
"Use the -G option to create a shared library fro
Stefan Behnel added the comment:
> On the whole I think the arguments to make a module are very strong. So I
> think that is the appropriate way forward.
If you take this route, please don't write it directly against the CPython
C-API (as you would for a CPython stdlib module).
Change by Stefan Krah :
--
pull_requests: +21103
stage: -> patch review
pull_request: https://github.com/python/cpython/pull/21997
___
Python tracker
<https://bugs.python.org/issu
Stefan Krah added the comment:
Okay, thanks. The -G option is of course attractive for Linux projects
because it requires minimal changes in the build machinery.
I've added support for libmpdec/libmpdec++ (next release) for AIX-style
shared libraries (shr.o inside libmpdec.a). Th
Stefan Krah added the comment:
I can't find the reason for:
if test -z "$EXPORTSYMS"; then
EXPORTSYMS="Modules/python.exp"
fi
Modules/python.exp is hardcoded elsewhere, and I'd rather set
EXPORTSYMS unconditionally on AIX and un
Stefan Krah added the comment:
New changeset e6dcd371b2c54a94584dd124e8c592a496d46a47 by Stefan Krah in branch
'master':
bpo-19521: Fix parallel build race condition on AIX (GH-21997)
https://github.com/python/cpython/commit/e6dcd371b2c54a94584dd124e8c592
Stefan Krah added the comment:
New changeset 88b86a9752afc2c50ca196f6ba1a8d62d71cf398 by Miss Islington (bot)
in branch '3.9':
bpo-19521: Fix parallel build race condition on AIX (GH-22001)
https://github.com/python/cpython/commit/88b86a9752afc2c50ca196f6ba1a8d
Stefan Krah added the comment:
This is in master and 3.9.1. I'll not backport to 3.8 because a release
candidate is imminent.
--
resolution: -> fixed
stage: patch review -> resolved
status: open -> closed
type: -> behavior
vers
Stefan Krah added the comment:
If nothing has been diagnosed, I suggest closing this.
--
status: open -> pending
___
Python tracker
<https://bugs.python.org/issu
Change by Stefan Krah :
--
title: Decimal divisions sometimes 10x or 100x too large -> small_ints[]
modified (third party C-extension?)
___
Python tracker
<https://bugs.python.org/issu
Change by Stefan Krah :
--
nosy: David.Edelsohn, skrah
priority: normal
severity: normal
status: open
title: xlc: add -qalias=noansi -qmaxmem=-1
___
Python tracker
<https://bugs.python.org/issue41
Change by Stefan Krah :
--
keywords: +patch
pull_requests: +21183
stage: -> patch review
pull_request: https://github.com/python/cpython/pull/22096
___
Python tracker
<https://bugs.python.org/issu
New submission from Stefan Krah :
At least the xlc version on AIX 7.1 has aggressive optimizations even
with -O:
#include
#include
static int
f(long *a, long long *b)
{
int t = *a;
*b = 0; // cannot
Stefan Krah added the comment:
We would also need -fwrapv to be safe, but I cannot find an equivalent
option for xlc.
The Intel compiler had a similar failure to #40244 that was resolved
by -fwrapv (see #40223).
--
___
Python tracker
<ht
Stefan Krah added the comment:
-qmaxmem=-1 is added to disable verbose remarks.
--
___
Python tracker
<https://bugs.python.org/issue41721>
___
___
Python-bug
Stefan Krah added the comment:
New changeset 84a7917b4c9afec07575065cffa143b91fe98c14 by Stefan Krah in branch
'master':
bpo-41721: Add xlc options (GH-22096)
https://github.com/python/cpython/commit/84a7917b4c9afec07575065cffa143
Stefan Krah added the comment:
The code example is for 64-bit Linux with sizeof(long) == sizeof(long long).
It also works on 32-bit xlc with int/long.
--
___
Python tracker
<https://bugs.python.org/issue41
Stefan Krah added the comment:
New changeset fb050d0d60f38dc9b6c30df1864020a92981be5b by Miss Islington (bot)
in branch '3.9':
bpo-41721: Add xlc options (GH-22097)
https://github.com/python/cpython/commit/fb050d0d60f38dc9b6c30df1864020
Change by Stefan Krah :
--
resolution: -> fixed
stage: patch review -> resolved
status: open -> closed
___
Python tracker
<https://bugs.python.or
Stefan Krah added the comment:
I think this is a duplicate of #41401.
--
nosy: +skrah
resolution: -> duplicate
stage: -> resolved
status: open -> closed
superseder: -> Using non-ascii that require UTF-8 breaks AIX testing
___
Py
Stefan Krah added the comment:
memoryview can store anything, but only access and display
the native format. The reason is that conversions in the manner
of the struct module are very expensive.
You can construct all sorts of formats that memoryview cannot
handle:
>>> x = array(1, &
Stefan Krah added the comment:
list() has to *interpret* the endianness to display it. The endianness
of the *native* format does not matter. The endianness of an explicit
format matters, since list has to be able to convert non-native formats.
I suggest to look at XND, which is a memoryview
Stefan Behnel added the comment:
Agreed that adding "!=" would be a nice improvement, probably not very
invasive. PR welcome.
https://www.w3.org/TR/xpath-10/#booleans
--
nosy: +scoder
stage: -> needs patch
type: -> enhancement
versions: +Python
Stefan Behnel added the comment:
I'd suggest feeding the data into the parser in chunks, or letting it read from
a file-like object, or something like that.
Also, you probably want to do incremental processing on the data (see the
XMLPullParser and iterparse), because reading 3.5GB o
Change by Stefan Behnel :
--
title: ElementTree limitation -> ElementTree parser limitation of input string
size
___
Python tracker
<https://bugs.python.org/issu
Stefan Behnel added the comment:
Changing subject to make it clear what this ticket is really about.
--
title: Pure-Python ElementTree classes no longer available since 3.3 -> Allow
more low-level parser configuration in ElementTree
versions: +Python 3.10 -Python 3.3, Python
Change by Stefan Behnel :
--
resolution: -> duplicate
stage: -> resolved
status: open -> closed
___
Python tracker
<https://bugs.python.org/issue20198>
___
___
Stefan Krah added the comment:
It would have been nice to have had a chance to look at this, but
apparently those days are over.
--
___
Python tracker
<https://bugs.python.org/issue41
Change by Stefan Krah :
--
nosy: -skrah
___
Python tracker
<https://bugs.python.org/issue41732>
___
___
Python-bugs-list mailing list
Unsubscribe:
Stefan Krah added the comment:
I have been asked to backport this to 3.8. There's a very small window
of opportunity:
3.8.6: Monday, 2020-09-21
3.8.7rc1: Monday, 2020-11-02
3.8.7: Monday, 2020-11-16 (final version!)
Backporting procedures since 3.8 are unclear and a source of
con
Stefan Behnel added the comment:
Big +1 from me, too, for the same reasons Yury gave.
--
nosy: +scoder
___
Python tracker
<https://bugs.python.org/issue41
Stefan Behnel added the comment:
Copying some of the design discussion from the PR here
(https://github.com/python/cpython/pull/22196/files#r486730457), because it
belongs into the ticket.
Yury Selivanov proposed to add a new C-API function for this (naming changes by
me):
typedef
Stefan Behnel added the comment:
I'm happy to see this moving forward.
Not convinved of the "PyIter_Send()" name, though. I don't consider this part
of the iterator protocol. It's specific to generators and coroutines. Cython
would probably guard its usage b
Stefan Behnel added the comment:
I would also have preferred a more type specific function, but yeah, as long as
the types for which the function would normally be used are special cased early
enough in the implementation, it makes no big difference.
Fine with me, too
Stefan Behnel added the comment:
BTW, just to give this a house number, I remember having measured a performance
improvement of up to 70% at some point when switching from "generators always
raise a StopIteration at the end" to "generators just return NULL" in Cython
Stefan Behnel added the comment:
Closing again since GH-21528 has been merged in issue 41295.
--
status: open -> closed
___
Python tracker
<https://bugs.python.org/issu
Stefan Behnel added the comment:
FYI, https://github.com/cython/cython/pull/3427 has been merged into Cython. In
Cython 3.0, compiled coroutines will disguise as non-compiled coroutines, from
the PoV of asyncio.
Restricting this ticket to Py3.10 since we're rather discussing a new fe
Change by Stefan Behnel :
--
resolution: -> fixed
stage: patch review -> resolved
status: open -> closed
___
Python tracker
<https://bugs.python.or
Stefan Behnel added the comment:
> That example is especially problematic.
No, it's not. It uses .findall(), which returns a list. It's like when you make
a copy of a list to iterate over, when you want to modify the original list in
the loop.
That could be made explicit in
Change by Stefan Behnel :
--
keywords: +patch
pull_requests: +21489
stage: -> patch review
pull_request: https://github.com/python/cpython/pull/22464
___
Python tracker
<https://bugs.python.org/issu
Change by Stefan Behnel :
--
stage: -> patch review
___
Python tracker
<https://bugs.python.org/issue41892>
___
___
Python-bugs-list mailing list
Unsubscrib
Stefan Behnel added the comment:
@WoodyWoo, you can (and should) do something like this:
for ELEMchild in list(etroot):
Modifying a container while iterating over it is usually not a good idea. The
same applies to Python lists and dicts, for example.
--
stage: patch review
Stefan Behnel added the comment:
Closing as duplicate of issue 41892. Let's keep the discussion there.
--
___
Python tracker
<https://bugs.python.org/is
Change by Stefan Behnel :
--
Removed message: https://bugs.python.org/msg377740
___
Python tracker
<https://bugs.python.org/issue41899>
___
___
Python-bugs-list m
Stefan Behnel added the comment:
Closing as duplicate of issue 41891. Let's keep the discussion there.
--
nosy: +scoder
resolution: -> duplicate
stage: -> resolved
status: open -> closed
___
Python tracker
<https://bugs.pyth
Stefan Behnel added the comment:
Yes, it fixed already. Thanks!
--
nosy: +scoder
resolution: -> fixed
stage: patch review -> resolved
status: open -> closed
___
Python tracker
<https://bugs.python.or
New submission from Stefan Behnel :
import xml.etree.ElementTree as ET
xml="""
http://soap.sforce.com/2006/04/metadata";>
"""
print(ET.canonicalize(xml))
Fails with:
ValueError: Namespace "" is not declared in scope
when trying to build t
Change by Stefan Behnel :
--
keywords: +patch
pull_requests: +21493
stage: needs patch -> patch review
pull_request: https://github.com/python/cpython/pull/22474
___
Python tracker
<https://bugs.python.org/issu
Change by Stefan Behnel :
--
versions: +Python 3.10, Python 3.9
___
Python tracker
<https://bugs.python.org/issue41892>
___
___
Python-bugs-list mailin
Stefan Behnel added the comment:
New changeset 6a412c94b6b68e7e3632562dc7358a12ffd1447f by scoder in branch
'master':
bpo-41900: C14N 2.0 serialisation failed for unprefixed attributes when a
default namespace was defined. (GH-22474)
https://github.com/python/cpyt
Stefan Behnel added the comment:
New changeset a0f2b664335eb689abdecc677e09a193f503af59 by Miss Skeleton (bot)
in branch '3.9':
bpo-41900: C14N 2.0 serialisation failed for unprefixed attributes when a
default namespace was defined. (GH-22474) (GH-22507)
https://github.com/pyth
Stefan Behnel added the comment:
New changeset cfed5343331350c5737b464970a31f7588319e8b by Miss Skeleton (bot)
in branch '3.8':
bpo-41900: C14N 2.0 serialisation failed for unprefixed attributes when a
default namespace was defined. (GH-22474) (GH-22508)
https://github.com/pyth
Change by Stefan Behnel :
--
resolution: -> fixed
stage: patch review -> resolved
status: open -> closed
___
Python tracker
<https://bugs.python.or
Change by Stefan Behnel :
--
nosy: +scoder
nosy_count: 29.0 -> 30.0
pull_requests: +21519
pull_request: https://github.com/python/cpython/pull/22474
___
Python tracker
<https://bugs.python.org/iss
Change by Stefan Behnel :
--
nosy: +scoder
nosy_count: 9.0 -> 10.0
pull_requests: +21521
pull_request: https://github.com/python/cpython/pull/22474
___
Python tracker
<https://bugs.python.org/issu
Change by Stefan Behnel :
--
nosy: +scoder
nosy_count: 9.0 -> 10.0
pull_requests: +21520
pull_request: https://github.com/python/cpython/pull/22474
___
Python tracker
<https://bugs.python.org/issu
Change by Stefan Behnel :
--
pull_requests: -21520
___
Python tracker
<https://bugs.python.org/issue36533>
___
___
Python-bugs-list mailing list
Unsubscribe:
Change by Stefan Behnel :
--
pull_requests: -21519
___
Python tracker
<https://bugs.python.org/issue6721>
___
___
Python-bugs-list mailing list
Unsubscribe:
Change by Stefan Behnel :
--
nosy: -scoder
___
Python tracker
<https://bugs.python.org/issue36533>
___
___
Python-bugs-list mailing list
Unsubscribe:
Change by Stefan Behnel :
--
pull_requests: -21521
___
Python tracker
<https://bugs.python.org/issue33802>
___
___
Python-bugs-list mailing list
Unsubscribe:
Change by Stefan Behnel :
--
nosy: -scoder
___
Python tracker
<https://bugs.python.org/issue6721>
___
___
Python-bugs-list mailing list
Unsubscribe:
Change by Stefan Behnel :
--
nosy: -scoder
___
Python tracker
<https://bugs.python.org/issue33802>
___
___
Python-bugs-list mailing list
Unsubscribe:
Change by Stefan Behnel :
--
pull_requests: +21547
pull_request: https://github.com/python/cpython/pull/22546
___
Python tracker
<https://bugs.python.org/issue41
Stefan Behnel added the comment:
Closing since this works as designed.
Users are responsible for avoiding concurrent tree modifications during
iteration.
--
resolution: -> not a bug
stage: patch review -> resolved
status: open -&g
Stefan Behnel added the comment:
> Don't forget to remove PyGen_Send()
That's the function that allows sending data into a generator. It's also used
internally by "PyIter_Send()". Are you really suggesting to remove it, or to
make it underscore-priv
New submission from Stefan Völkl :
I found that the currency formatting does not work correctly for all locales.
For example:
{{{
import locale
amount = 24.99
locale.setlocale(locale.LC_ALL, 'it_IT.UTF-8')
price = locale.currency(amount)
print(price)
}}}
returns "€ 24,99&quo
Stefan Völkl added the comment:
>>> locale.localeconv()
{'int_curr_symbol': 'EUR ', 'currency_symbol': '€', 'mon_decimal_point': ',',
'mon_thousands_sep': '.', 'mon_grouping': [3, 3, 0],
Stefan Behnel added the comment:
The patch looks right. I'm not sure if this can still be changed in Py3.8,
though, since that has been around for quite a while now.
Admittedly, few people will disable the C accelerator module and thus whitness
this issue, but for them, this is a bre
Stefan Behnel added the comment:
In general, since the C accelerator is enabled by default, and few people would
consider disabling it explicitly, I generally consider the behaviour of the C
implementation to be "right", if both implementations differ.
As a single data point, the
Stefan Behnel added the comment:
New changeset 97e8b1eaeaf3aa325c84ff2e13417c30414d0269 by Ammar Askar in branch
'master':
bpo-40624: Add support for the XPath != operator in xml.etree (GH-22147)
https://github.com/python/cpython/commit/97e8b1eaeaf3aa325c84ff2e13417c
Change by Stefan Behnel :
--
resolution: -> fixed
stage: patch review -> resolved
status: open -> closed
___
Python tracker
<https://bugs.python.or
Stefan Krah added the comment:
Thanks for the comments. Most of them should be easy to fix.
Nick Coghlan wrote:
> [...] expose the Py_buffer len field as "memoryview.size" instead of
> "memoryview.len" (to reduce confusion with "len(memoryview)" and
&
Changes by Stefan Krah :
--
dependencies: +Problems with Py_buffer management in memoryobject.c (and
elsewhere?)
resolution: fixed -> remind
status: closed -> open
___
Python tracker
<http://bugs.python.org/i
Stefan Krah added the comment:
Reopening as a reminder that it isn't fixed yet in
http://hg.python.org/features/pep-3118 .
--
___
Python tracker
<http://bugs.python.org/is
Stefan Krah added the comment:
Revisiting memoryview.size: I foresee problems for NumPy users, since array.size
has a different meaning there:
>>> x = array([[1,2,3], [4,5,6]], dtype='q')
>>> x.shape
(2, 3)
>>> x.itemsize
8
>>> len(x)
2
>>&g
Stefan Krah added the comment:
Just as a note: It is not acceptable to be rude on the tracker or
to remove people from the nosy list as you did in #13695.
--
nosy: +skrah
___
Python tracker
<http://bugs.python.org/issue13
Stefan Krah added the comment:
py.user: The format string must always match the grammar, which is just
above the paragraph that you quoted:
[[fill]align][sign][#][0][width][,][.precision][type]
Thus, if fill and align are absent, it does not mean that you can add
arbitrary characters
Stefan Krah added the comment:
The text speaks about the regular case of a second character that
is not a valid alignment character, e.g.:
format(3.222, ".2f")
Clearly the '2' fulfills this criterion, so the parser knows that the
leading '.' is *not* a fill c
Stefan Krah added the comment:
Eric V. Smith wrote:
> As I look at it a little closer, I think I'm going to change the message to:
> "Invalid format type specified". The code has determined that instead of a
> type that's a single character long, it's rece
Stefan Krah added the comment:
Stefan Krah wrote:
>> ["xx10d"]
> look at the code now, but would the message also be raised for this spec?
>
> format(9, "xx10f")
Argh, 'd' is of course also a valid type specifier.
--
Stefan Krah added the comment:
> ... with *n*th (italic n) as alternate form
Knuth uses that in TAOCP, too. I think with or without italics it's
the most frequently used form overall.
Also the Lisp function is called nth and not n-th, even though in Lisp
it is possible to use hy
Stefan Krah added the comment:
> This is the last decision. Also, if anyone of you can, please then just >
> incorporate that final patch that Justin will make. Thanks.
Stop acting like a manager. A while ago a person had his account
disabled for constantly bumping up issues and tell
Changes by Stefan Krah :
--
nosy: -skrah
___
Python tracker
<http://bugs.python.org/issue13816>
___
___
Python-bugs-list mailing list
Unsubscribe:
New submission from Stefan Krah :
This came up in #10419, which is already a little crowded. PyBuffer_FillInfo()
returns success if the value for 'view' is NULL.
I can't really see a reason for that. Any thoughts?
--
components: Interpreter Core
messages: 151953
nosy: n
Changes by Stefan Krah :
Added file: http://bugs.python.org/file24323/8dd9f0ea4876.diff
___
Python tracker
<http://bugs.python.org/issue10181>
___
___
Python-bugs-list m
Stefan Krah added the comment:
Done in: http://hg.python.org/features/pep-3118/rev/508d5e3c579c
--
dependencies: -Problems with Py_buffer management in memoryobject.c (and
elsewhere?)
___
Python tracker
<http://bugs.python.org/issue13
Changes by Stefan Krah :
--
resolution: remind -> fixed
status: open -> closed
___
Python tracker
<http://bugs.python.org/issue13411>
___
___
Python-bugs-
Stefan Krah added the comment:
I removed the dependency since PyBuffer_ToContiguous() still needs to
be fixed in abstract.c while memoryview.tobytes() now works in the
PEP-3118 repo.
--
dependencies: -Problems with Py_buffer management in memoryobject.c (and
elsewhere?)
title
New submission from Stefan Krah :
test_pydoc fails on Ubuntu Lucid:
==
FAIL: test_apropos_with_bad_package (test.test_pydoc.PydocImportTest)
--
Traceback (most
New submission from Stefan Krah :
test_zlib currently fails on Ubuntu Lucid:
==
FAIL: test_library_version (test.test_zlib.VersionTestCase)
--
Traceback (most
Stefan Krah added the comment:
Thanks! There was a 32-bit 1.2.5 version in /usr/local/lib and
a 64-bit 1.2.3.3 version in /lib.
gcc picks up the header from /usr/local/include, while ld is smart
enough to choose the 64-bit version. So it was a multilib issue.
While this is not the most
New submission from Stefan Krah :
Passing -UNDEBUG as CFLAGS currently doesn't work:
./configure CFLAGS="-UNDEBUG" && make
[...]
libpython3.3m.a(object.o): In function `PyObject_Str':
/home/stefan/pydev/cpython/Objects/object.c:441: undefined reference to
1201 - 1300 of 4949 matches
Mail list logo
