Michael Felt added the comment:
After reading the PEP I realized it is much simpler. The test is for interrupts
that occur at a low-level - and not for permission issues. The test is failing
because there is a permission issue, not a missed interrupt issue. Modifying
the code to: (see line
Change by Michael Felt :
--
keywords: +patch, patch
pull_requests: +10840, 10841
stage: -> patch review
___
Python tracker
<https://bugs.python.org/issu
Change by Michael Felt :
--
keywords: +patch
pull_requests: +10840
stage: -> patch review
___
Python tracker
<https://bugs.python.org/issue35633>
___
___
Py
Change by Michael Felt :
--
pull_requests: +10842
___
Python tracker
<https://bugs.python.org/issue35189>
___
___
Python-bugs-list mailing list
Unsubscribe:
Change by Michael Felt :
--
pull_requests: +10842, 10843
___
Python tracker
<https://bugs.python.org/issue35189>
___
___
Python-bugs-list mailing list
Unsub
Change by Michael Felt :
--
pull_requests: +10842, 10843, 10844, 10845
___
Python tracker
<https://bugs.python.org/issue35189>
___
___
Python-bugs-list mailin
Change by Michael Felt :
--
pull_requests: +10842, 10843, 10845
___
Python tracker
<https://bugs.python.org/issue35189>
___
___
Python-bugs-list mailin
Change by Michael Felt :
--
components: -IO
___
Python tracker
<https://bugs.python.org/issue35633>
___
___
Python-bugs-list mailing list
Unsubscribe:
Michael Felt added the comment:
While the PR probably solves this - there is a 'bug' in pandas (I expect) that
prevents me from completing the test - as, I expect LONG before the .cpp source
is to be compiled - there is a error because a wrong flag is passed to the
compiler (-
Michael Felt added the comment:
On 04/01/2019 17:08, Kevin wrote:
> Kevin added the comment:
>
> Ah. We always compile with GCC, so would not have hit that particular problem.
>
> --
>
> ___
> Python tracker
> <http
Michael Felt added the comment:
Further along - however, I never get to the "link" routine.
Again, this is likely a pandas coding issue - currently python is calling xlc_r
..., but when I manually modify it to xlC_r I get the same error.
xlc_r -D_LARGE_FILES -O -I/opt/include -O
Michael Felt added the comment:
I had tried “wb+”, not “w+b”. Is there a difference? I forget if I tried just
“w+”.
But I’ll do them anyway/again to be sure.
Sent from my iPhone
> On 4 Jan 2019, at 23:43, STINNER Victor wrote:
>
>
> Change by STINNER Victor :
>
>
&g
Michael Felt added the comment:
On 04/01/2019 23:42, STINNER Victor wrote:
> STINNER Victor added the comment:
>
> Does the test pass if you open the file in read+write ("w+b") mode rather
> than write-only ("wb") mode?
>
> I'm talking about this li
Michael Büsch added the comment:
I would like to implement this feature.
So if somebody thinks that it's a bad idea to have this feature, please speak
up now.
--
nosy: +vstinner
___
Python tracker
<https://bugs.python.org/is
Michael Felt added the comment:
On 07/01/2019 15:46, STINNER Victor wrote:
> STINNER Victor added the comment:
>
> Since you are getting indentation error, I'm not sure about your test. Can
> you please apply the patch below and run again test_eintr? Does it still fail
>
Michael Saah added the comment:
Hi Victor, thanks for taking a look.
> Would why datetime have the same behavior on all platforms, but
> time.strftime('%') may or may not raise an exception depending on the libc?
If I understand the call stack correctly, datetime does n
Michael Felt added the comment:
On 08/01/2019 15:40, Ayappan wrote:
> Ayappan added the comment:
>
> Not sure what went wrong here.
> I used gcc & g++ and didn't hit this issue.
>
> --
>
> ___
> Python tracker
&
New submission from Michael Felt :
By default AIX builds 32-bit applications - and the combined .data, .bss and
.stack areas share one memory segment of 256 Mbyte.
This can be modified by either specifying a larger value for maxdata during
linking (e.g., with LDFLAGS=-bmaxdata:0x4000) or
Change by Michael Felt :
--
keywords: +patch
pull_requests: +11029
stage: -> patch review
___
Python tracker
<https://bugs.python.org/issue35704>
___
___
Py
Michael Saah added the comment:
> Michael - do you think you can / would you like to add the functionality that
> Victor mentioned to your existing PR? If not, I recommend we merge the
> current PR and open a new issue for "Lone trailing % not supported on all
> platforms&q
New submission from Michael Felt :
Hi all,
as we get closer to having the current tests all patched I want to have a place
to post new "failures" - since the BOT process is unable to report regressions
before all tests are passing for a time.
Initially, the tests run normally,
New submission from Michael Krötlinger :
After operations = xmltree.getElementsByTagName("operation") the table does not
contain operations antragstypenErmitteln and mammographieIndikationenErmitteln
--
files: EbsService.wsdl
messages: 333621
nosy: MiKr41
priority: norma
Michael Felt added the comment:
Well, I can close this again - whatever was wrong with test_xml_etree_c
disappeared - and a cursory look at test_os reveals that the issue might be the
time lag between the NFS server where the temp files are made and the "local"
sense of time.
M
Change by Michael Felt :
--
stage: -> resolved
status: open -> closed
___
Python tracker
<https://bugs.python.org/issue35735>
___
___
Python-bugs-list
Michael Felt added the comment:
On 07/01/2019 15:46, STINNER Victor wrote:
> STINNER Victor added the comment:
>
> Since you are getting indentation error, I'm not sure about your test. Can
> you please apply the patch below and run again test_eintr? Does it s
Michael Krötlinger added the comment:
http://schemas.xmlsoap.org/wsdl/";
xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/";
xmlns:tns="http://soap.ebs.client.chipkarte.at";
xmlns:wsam="http://www.w3.org/2007/05/addressing/metadata";
xmlns:wsp="http:/
New submission from Michael Felt :
I see in the bot history that test_bdb is now failing on AIX
https://buildbot.python.org/all/#/builders/161/builds/718/steps/4/logs/stdio
== CPython 3.8.0a0 (heads/master:a37f52436f, Jan 15 2019, 22:53:01) [C]
== AIX-1-00C291F54C00-powerpc-32bit big-endian
Michael Felt added the comment:
I’ll make a new PR and delete the news entry.
Sent from my iPhone
> On 15 Jan 2019, at 11:23, STINNER Victor wrote:
>
>
> STINNER Victor added the comment:
>
>> On AIX the test for flock() passes, but the test for lockf() fails: (...
Michael Felt added the comment:
Done.
> On 1/15/2019 11:23 AM, STINNER Victor wrote:
> I would prefer to simply skip the lockf() test rather than ignoring
> PermissionError for flock() and lockf() on all platforms. Can you please
> write a PR for that?
>
> There is no
New submission from Michael Felt :
Last August I started running a bot for AIX using xlc_r as the compiler, rather
than gcc that the other AIX bot uses.
Initially, I had no issues with the test_multiprocess* tests, but of late (last
two+ months I am guessing) I have been having regular
Change by Michael Felt :
--
title: test_multiprocessing_* tests - success versus fail varies over time ->
test_multiprocessing_* - crash in PyDict_GetItem - segmentation error
___
Python tracker
<https://bugs.python.org/issu
Michael Felt added the comment:
OK, I have gone as far back as "where" in dbx can bring me.
Could this, somehow, be related with changes made in issue-33015 ?
In any case, does it seem correct that "pthread_wrapper(void *arg) can be
correct if arg is nil?
+15
Michael Jacob added the comment:
Does this ticket track the issue in its title or the native crash? If it's the
latter, is there a new ticket for the None _handle or shall I create one?
--
nosy: +Michael Jacob2
versions: +Python 3.7
___
P
Michael Felt added the comment:
OK. being more specific about the test situation.
When I run ./python -m test test_multiprocessing_fork all is fine. However,
when I run it as: ./python -m test -j2 test_multiprocessing_main_handling
test_multiprocessing_fork
Michael Felt added the comment:
After enabling PYTHONTHREADDEBUG=1 I got the dprintf output.
I added line info (as fixed text) asin:
Python/thread_pthread.h:
+511 PyLockStatus
+512 PyThread_acquire_lock_timed(PyThread_type_lock lock, PY_TIMEOUT_T
microseconds,
+513
Michael Jacob added the comment:
So, I'm experiencing the issue in the title, too. The pipe handle stays valid
for between 5 and 60 minutes, then it goes None when written to.
I'm far from understanding that code, but this crude re-connect code seems to
solve the issue for me:
In
Michael Felt added the comment:
Update:
buildbot@x064:[/home/buildbot/buildarea/3.x.aixtools-aix-power6/issue]./python
-m test -v test_bdb
== CPython 3.8.0a0 (heads/master-dirty:0785889468, Jan 30 2019, 16:16:31) [C]
== AIX-1-00C291F54C00-powerpc-32bit big-endian
== cwd:
/home/buildbot
Michael Felt added the comment:
OK. New info.
Back in the time of issue 34347 I installed some extra filesets to support
UTF-8 on the virtual machine (aka partition) that I have the bot on.
On systems where this fileset is not installed this test does not fail.
Shall dig further - in a
Michael Sullivan added the comment:
How about adding another sigil that indicates that subsequent keyword-only
arguments are required? So then your example becomes (using ` as a totally
strawman option):
PyArg_ParseTupleAndKeywords(args, kwds, "O|O$O`O", kwlist, &a, &
New submission from Michael Schlenker :
The introduction of the ReadOnly flag in the ssl.enum_certificates() function
implementation has introduced a regression.
The old version returned certificates for both the current user and the local
system, the new function only enumerates system wide
Michael Schlenker added the comment:
It probably is even worse.
The flag seems to specifiy the physical locations, and just using
CERT_SYSTEM_STORE_LOCAL_SYSTEM probably misses the certificates distributed by
Group Policy or AD too, in addition to the stores for the current user.
See
Change by Michael Sullivan :
--
keywords: +patch
pull_requests: +11865
stage: -> patch review
___
Python tracker
<https://bugs.python.org/issue34235>
___
_
Michael Felt added the comment:
On 14/02/2019 23:57, Indra Talip wrote:
> Indra Talip added the comment:
>
> The current code and proposed changes use 'netstat -ia' to find the node
> however if netstat needs to perform a reverse DNS query to resolve some
> interfac
Michael Sullivan added the comment:
The point about a performance penalty is fair---my PR does add a search for the
'@' (which I spelled as '`' in my example above) sigil whenever it encounters a
'|'. (Though I'm not sure how big the impact would be? Format
Michael Sullivan added the comment:
A downside of the "allow $ twice" approach is that it means splitting up the
positional arguments, and a lot of the processing loop is built around the
assumption that the index into the keyword list and the index into the argument
tuple coi
Michael Felt added the comment:
OK. I have narrowed it down to this:
when
LANG=en_US.8859-15
the test fails.
root@x064:[/home/root]grep LANG /etc/environment
LANG=en_US
And now it passes.
--
___
Python tracker
<https://bugs.python.
Michael Felt added the comment:
Some record keeping - to keep track of when this regression first appeared on
the bot:
buildername POWER6 AIX 3.x Builder
buildnumber 718 Build
codebaseBuild
event pushChange
github_distinct trueChange
got_revision
Change by Michael Felt :
--
pull_requests: +11940
___
Python tracker
<https://bugs.python.org/issue35633>
___
___
Python-bugs-list mailing list
Unsubscribe:
Michael Felt added the comment:
The PR's have been merged. Many thanks.
Closing this issue and looking forward.
--
stage: patch review -> resolved
status: open -> closed
___
Python tracker
<https://bugs.python.
Michael Felt added the comment:
As far as 'master' is concerned, this has been resolved, so I'll close it
myself.
--
stage: -> resolved
status: open -> closed
versions: +Python 3.8 -Python 3.4
___
Python tracker
<
Michael Felt added the comment:
Again - after switching the env variable LANG to the 'default' everything works
as expected.
Leaving it open as a regression - because everything was working with a
non-default setting.
When I have more time I'll do a git bisect to try an
New submission from Michael Felt :
On a system using an older version of gcc (v5.7.4) I get an error: (also AIX
6.1)
gcc -pthread -Wno-unused-result -Wsign-compare -g -O0 -Wall -O
-std=c99 -Wextra -Wno-unused-result -Wno-unused-parameter
-Wno-missing-field-initializers -Werror
Michael Felt added the comment:
correction - gcc version is v4.7.4
--
___
Python tracker
<https://bugs.python.org/issue36034>
___
___
Python-bugs-list mailin
New submission from Louis Michael :
at https://docs.python.org/3/howto/regex.html#regex-howto
and
https://docs.python.org/3.8/howto/regex.html#regex-howto
https://docs.python.org/3.7/howto/regex.html#regex-howto
https://docs.python.org/3.6/howto/regex.html#regex-howto
https://docs.python.org
Change by Louis Michael :
--
keywords: +patch
pull_requests: +11968
stage: -> patch review
___
Python tracker
<https://bugs.python.org/issue35584>
___
___
Py
Michael Selik added the comment:
+1, This would be useful for quick analyses, avoiding the overhead of
installing scipy and looking through its documentation.
Given that it's in the statistics namespace, I think the name can be simply
``Normal`` rather than ``NormalDist``. Also, inste
Michael Felt added the comment:
I am still trying to get further with this, but I won't get far enough without
some help on how to best dig deeper.
For one, it should be leaving a core dump, but it never seems to leave the core
dump in the working directory. I know it is doing core
Michael Felt added the comment:
Another message that surprises me is:
Warning -- multiprocessing.process._dangling was modified by
test_multiprocessing_spawn
Before: <_weakrefset.WeakSet object at 0x3076e810>
After: <_weakrefset.WeakSet object at 0x3076e390>
Normally
Michael Felt added the comment:
Also - this looks like a core dump was 'seen', but later removed.
Warning -- files was modified by test_multiprocessing_forkserver
Before: []
After: ['core']
What can I change so that ot does not c
Michael Felt added the comment:
xlc has an option -qsource that creates output like this - first showing
the code with macro, then showing the expansion
>>>>> SOURCE SECTION <<<<<
...
16 | dev = st.st_dev;
17 | minor = minor(dev);
New submission from Michael Seifert:
It's possible to create a segfault when one (inappropriatly) changes the
functools.partial.keywords attribute manually. A minimal example reproducing
the segfault is:
>>> from functools import partial
>>> p = partial(int)
>>&g
Changes by Michael Seifert :
--
pull_requests: +536
___
Python tracker
<http://bugs.python.org/issue29800>
___
___
Python-bugs-list mailing list
Unsubscribe:
Michael Seifert added the comment:
Given that this my first contribution to CPython I'm not too sure about the
etiquette. When do I know (or who decides) when an agreement on a fix is
reached? I wouldn't mind retracting the pull request if someone else wants to
fix it differently.
New submission from Michael Seifert:
The PyTuple_GetSlice documentation says it "Take a slice of the tuple pointed
to by p from low to high and return it as a new tuple." [0] However in case the
start is <= 0 and the stop is >= tuplesize it doesn't return the promised
Changes by Michael Seifert :
--
title: PyTuple_GetSlice documentation incorrect -> PyTuple_GetSlice does not
always return a new tuple
___
Python tracker
<http://bugs.python.org/issu
Michael Seifert added the comment:
> What leads to your headache?
That depending on the arguments to "PyTuple_GetSlice" I get "SystemError:
..\Objects\tupleobject.c:156: bad argument to internal function" when using
PyTuple_SetItem on the (supposedly) new tuple.
May
Changes by Michael Seifert :
--
pull_requests: +554
___
Python tracker
<http://bugs.python.org/issue29800>
___
___
Python-bugs-list mailing list
Unsubscribe:
Changes by Michael Seifert :
--
pull_requests: +555
___
Python tracker
<http://bugs.python.org/issue29800>
___
___
Python-bugs-list mailing list
Unsubscribe:
Michael Seifert added the comment:
I rather thought about something along the lines of: "Take a slice of the tuple
pointed to by *p* from *low* to *high* and return it as a tuple. Whether the
returned tuple is new or not is an implementation detail (and may depend on the
value o
Changes by Michael Haubenwallner :
--
pull_requests: +560
___
Python tracker
<http://bugs.python.org/issue19521>
___
___
Python-bugs-list mailing list
Unsub
Michael Felt added the comment:
Curious.
First pass: using python2.7.12 also hanged as program, on the close()
second pass: interactive - do the read first, then the close - seems to work:
root@x064:[/data/prj/python/issues/29545]cat hello.py
#!/usr/bin/env python
import errno
import os
Changes by Michael Haubenwallner :
--
pull_requests: +652
___
Python tracker
<http://bugs.python.org/issue15590>
___
___
Python-bugs-list mailing list
Unsub
New submission from Michael Seifert:
When using `copy.copy` to copy an `itertools.chain` instance the results can be
weird. For example
>>> from itertools import chain
>>> from copy import copy
>>> a = chain([1,2,3], [4,5,6])
>>> b = copy(a)
>>> ne
New submission from Michael Seifert:
A copy of the struct definition can be found in the typeobject documentation
[1]. There is also some explanation of the "closure" function pointer in the
extending tutorial [2].
However the struct isn't explicitly defined as "c:type&q
New submission from Michael Seifert:
The `link`-target of the "type" struct member is the python built-in "type".
See [1].
I think it should not be a link at all.
[1] https://docs.python.org/3.7/c-api/structures.html#c.PyMemberDef
--
assignee: docs@python
compo
Changes by Michael Seifert :
--
pull_requests: +753
___
Python tracker
<http://bugs.python.org/issue1234>
___
___
Python-bugs-list mailing list
Unsubscribe:
New submission from Michael Seifert:
Some exceptions thrown by `PyArg_ParseTupleAndKeywords` refer to "function" or
"this function" even when a function name was specified.
For example:
>>> import bisect
>>> bisect.bisect_right([1,2,3,4], 2, low=10)
Changes by Michael Seifert :
--
pull_requests: +816
___
Python tracker
<http://bugs.python.org/issue29951>
___
___
Python-bugs-list mailing list
Unsubscribe:
Michael Seifert added the comment:
Thank you for the suggestions, I added them to the PR. If you want
But are you sure about the "keywords must be strings" -> "keyword arguments
must be strings" change? I always thought the key is the "keyword" and t
Michael Seifert added the comment:
Just an update what doesn't work: just overriding the `__copy__` method.
I tried it but it somewhat breaks `itertools.tee` because if the passed
iterable has a `__copy__` method `tee` rather copies the iterator (=> resulting
in a lot of unnecessar
New submission from Michael Selik:
Minor, but it looks like someone decided to use a defaultdict but forgot to
remove the checks for whether a key exists.
Creating a defaultdict(list):
https://github.com/python/cpython/blob/6f0eb93183519024cb360162bdd81b9faec97ba6/Lib/lib2to3/btm_matcher.py
Michael Selik added the comment:
I'll submit a pull request momentarily.
--
___
Python tracker
<http://bugs.python.org/issue29957>
___
___
Python-bugs-list m
Michael Selik added the comment:
PR submitted. I also signed the contributor agreement, but the bot doesn't seem
to have noticed.
--
___
Python tracker
<http://bugs.python.org/is
Michael Selik added the comment:
Ok, I'll change the PR.
--
___
Python tracker
<http://bugs.python.org/issue29957>
___
___
Python-bugs-list mailing list
New submission from Michael Selik:
Currently, slicing a MatchObject causes an IndexError and len() a TypeError.
It's natural to expect slicing and len to work on objects of a finite length
that index by natural numbers.
--
messages: 291050
nosy: selik
priority: normal
severity: n
Changes by Michael Selik :
--
components: +Regular Expressions
nosy: +ezio.melotti, mrabarnett
type: -> enhancement
___
Python tracker
<http://bugs.python.org/issu
Michael Selik added the comment:
This would also enable negative indexing, which currently raises "IndexError:
no such group".
Edit: I meant whole numbers, not natural numbers.
--
versions: +Python 3.7
___
Python tracker
<http://bu
Changes by Michael Sghaier :
--
pull_requests: +1154
___
Python tracker
<http://bugs.python.org/issue29406>
___
___
Python-bugs-list mailing list
Unsubscribe:
Michael Selik added the comment:
Yesterday I wanted to do a destructuring bind on a slice of groups in a
finditer. Similar situation to the use case of Issue #24454. It might not be
"normal code" but I end up in that situation every month or so when parsing
semi-structured document
Michael Selik added the comment:
Sorry, it looks like I got the issue number wrong. My comparison should not
have been with #24454, but instead with an issue I can't locate at the moment.
Reproducing the example:
for g0, g1, g2 in re.finditer(r'(\d+)/(\d+)', 'Is
Changes by Michael Sghaier :
--
pull_requests: +1218
___
Python tracker
<http://bugs.python.org/issue29870>
___
___
Python-bugs-list mailing list
Unsubscribe:
Changes by Michael Seifert :
--
pull_requests: +1220
___
Python tracker
<http://bugs.python.org/issue26828>
___
___
Python-bugs-list mailing list
Unsubscribe:
New submission from Michael Seifert:
The "Py_Ellipsis" object is part of the public C-API but it isn't documented
anywhere.
It is defined in "sliceobject.o/.h" so I created a PR and added it to the
"slice" documentation.
--
assignee: docs@python
Michael Seifert added the comment:
> I'm wondering if it is worth to add a separate section for Ellipsis at the
> same level as "Slice Objects", but in the same file.
I'm not sure either.
There seems to be no precedent in the documentation, for example
"
Changes by Michael Seifert :
--
pull_requests: +1280
___
Python tracker
<http://bugs.python.org/issue30059>
___
___
Python-bugs-list mailing list
Unsubscribe:
Changes by Michael Seifert :
--
pull_requests: +1278
___
Python tracker
<http://bugs.python.org/issue30059>
___
___
Python-bugs-list mailing list
Unsubscribe:
Changes by Michael Seifert :
--
pull_requests: +1279
___
Python tracker
<http://bugs.python.org/issue30059>
___
___
Python-bugs-list mailing list
Unsubscribe:
Michael Seifert added the comment:
> I explored that notion of iterator length transparency years ago. While I
> don't remember all the details, I did record some notes at the top of
> Lib/test/test_iterlen.py.
But isn't that the point of the length_hint? To provide an
Michael Seifert added the comment:
> I would like to mark this tracker item as closed. IMO it is a dead-end.
Yes, even some (not very uncommon cases) give incorrect results:
it = iter([1,2,3])
zip(it, it, it)
has length_hint 3 but will only yield one i
Michael Seifert added the comment:
> zip.__length_hint__() must return NotImplemented or raise TypeError if any of
> iterators don't implement __length_hint__ or its __length_hint__() returns
> NotImplemented or raises TypeError.
> And what should return zip(range(
1301 - 1400 of 3024 matches
Mail list logo
