New submission from Pam McA'Nulty :
- Cloned a new cpython onto my new MacOS system (Mojave 10.14.4)
- built as per https://devguide.python.org/
- test failure:
```
./python.exe -m test -j3 test_socket
Run tests in parallel using 3 child processes
0:00:24 load avg: 0.88 [1/1/1] test_s
Change by Pam McA'Nulty :
--
title: test_socket test_host_resolution_bad_address test failure -> Test
Failure MacOS : test_socket test_host_resolution_bad_address
___
Python tracker
<https://bugs.python.org
Pam McA'Nulty added the comment:
Reviewing docs and am writing a queue implementation for usability testing. I
think ShareableList needs to support `close()` and `unlink()` directly. The
`.shm` attribute should be considered an _implementation_ detail, and not be
exposed.
--
Pam McA'Nulty added the comment:
In the example code, the 'result' variable is declared on the stack in the
callback() function. So it will be effectively when callback() returns.
Also the "result" variable in main() is never referenced. A pointer main()'
Pam McA'Nulty added the comment:
oops -
"In the example code, the 'result' variable is declared on the stack in the
callback() function. So it will be effectively when callback() returns."
should be
"In the example code, the 'result' variable i
Changes by Pam McA'Nulty :
--
nosy: +Pam.McANulty
___
Python tracker
<http://bugs.python.org/issue14483>
___
___
Python-bugs-list mailing list
Unsubscr
New submission from Pam McA'Nulty:
make failed on Mac OS X including sys/random.h
It looks to be caused by this commit:
https://github.com/python/cpython/commit/1958527a2c5dda766b1917ab563622434b3dad0d
Restoring the removed ifdefs solves the problem (see github PR)
Official patch to f
Pam McA'Nulty added the comment:
Patch for fix
--
keywords: +patch
Added file: http://bugs.python.org/file46009/Issue29057_random_include.patch
___
Python tracker
<http://bugs.python.org/is
Pam McA'Nulty added the comment:
OSX: 10.11.6 (15G1212)
Xcode 8.2.1 Build version 8C1002
--
___
Python tracker
<http://bugs.python.org/issue29057>
___
___
Pam McA'Nulty added the comment:
I just clicked "Random Issue" and it seemed to be an "easy" (ish) one - which
is just what I'd like to tackle over xmas break :)
--
___
Python tracker
<
Pam McA'Nulty added the comment:
Yeah, I looked at the code and saw what you described, David. I think I'll see
if there's a good place to mention this constraint in the docs and then I'll
find another one (besides the macOS build issue I ran into when trying to buil
Pam McA'Nulty added the comment:
I will say that, though my fix seems to work, it feels that the "right" place
to put the fix is in ./configure.
Sadly, I don't speak './configure', though I apparently remember enough C from
17
Pam McA'Nulty added the comment:
Good question.
It looks like there are 3 defines getting checked:
HAVE_SYS_RANDOM_H and either HAVE_GETRANDOM or HAVE_GETENTROPY
The previous issue seemed to be that you could have HAVE_GETRANDOM and/or
HAVE_GETENTROPY be set, but still not have a sys/ran
Pam McA'Nulty added the comment:
New patch to make consistent wrt use of "defined()"
--
Added file: http://bugs.python.org/file46024/Issue29057_random_include-v2.patch
___
Python tracker
<http://bugs.pyt
Pam McA'Nulty added the comment:
I've dug into things some more.
In my mac environment, sys/random.h is pretty empty and doesn't actually seem
to provide anything that Python/random.c uses. The compile error is a type
error is because 'u_int' never gets typedef
Pam McA'Nulty added the comment:
I can conform that Chi Hsuan Yen's patch works for me.
I'm concerned that the build includes sys/random.h despite it not actually
being needed to build python on mac os x (my worry is possible "shenanigans" by
Apple in future version
Changes by Pam McA'Nulty :
--
nosy: +Pam.McANulty
___
Python tracker
<http://bugs.python.org/issue27198>
___
___
Python-bugs-list mailing list
Unsubscr
Changes by Pam McA'Nulty :
--
nosy: +Pam.McANulty
___
Python tracker
<http://bugs.python.org/issue27152>
___
___
Python-bugs-list mailing list
Unsubscr
Changes by Pam McA'Nulty :
--
nosy: +Pam.McANulty
___
Python tracker
<http://bugs.python.org/issue26859>
___
___
Python-bugs-list mailing list
Unsubscr
New submission from Pam McA'Nulty:
While working on another issue, I added a test to increase (low-hanging fruit)
test coverage in unittest.runner.TextTestResult
--
components: Tests
files: textresult_coverage.patch
keywords: patch
messages: 269330
nosy: Pam.McANulty
priority: n
Changes by Pam McA'Nulty :
--
title: Increase test coverage of unittest.runner.TextTestResult -> Patch to
Increase test coverage of unittest.runner.TextTestResult
___
Python tracker
<http://bugs.python.org
Pam McA'Nulty added the comment:
Here's a patch. I needed to handle the fact that the repr of a single byte can
be 1, 2 or 4 characters long and did not want to wrap in the middle of a byte
representation. Note also that bytes literals require a continuation
character. In the pa
Pam McA'Nulty added the comment:
oops, forgot to add some samples:
>>> pprint.pprint(b"\n\n\n\n\n\n", width=5)
b'\n'\
b'\n'\
b'\n'\
b'\n'\
b'\n'\
b'\n'
>>> pprint.pprint({"a": b"\x00\xff
Pam McA'Nulty added the comment:
- eval expects bytes to have a continuation character and test_str_wrap did an
eval check so I figured test_bytes_wrap should as well:
# repr some bytes:
>>> b = b"\x00\xff" * 5
>>> b
b'\x00\xff\x00\xff\x00\xff\x00\xff\x
Pam McA'Nulty added the comment:
Here's a new version. It looks more like the str_parts patch and uses
parentheses instead of continuation as suggested.
Sample output:
>>> pprint.pprint(b"\n\na\x00", width=1)
(b'\n'
b'\n'
Changes by Pam McA'Nulty :
--
nosy: +Pam.McANulty
___
Python tracker
<http://bugs.python.org/issue10612>
___
___
Python-bugs-list mailing list
Unsubscr
Pam McA'Nulty added the comment:
Added unittest.StopTestRun exception. It's caught and handled in
testPartExecutor() - which is the same place SkipTest is caught.
If report=False, then it sets the result.haltTestRun attribute, which is a
signal to TestTextRunner to not generate
Pam McA'Nulty added the comment:
This version fixes a few things after using review.
I still have some open questions:
o Where in unittest.rst should the StopTestRun documentation actually live?
I've put it right after the SkipTest exception. That doesn't feel perfect,
but
Changes by Pam McA'Nulty :
--
nosy: +r.david.murray
___
Python tracker
<http://bugs.python.org/issue10612>
___
___
Python-bugs-list mailing list
Unsubscr
Changes by Pam McA'Nulty :
--
nosy: +kushal.das
___
Python tracker
<http://bugs.python.org/issue10612>
___
___
Python-bugs-list mailing list
Unsubscr
Pam McA'Nulty added the comment:
Remove quotes from quoted patterns only on windows systems (since if the quotes
get parsed into the pattern field on a non-windows system, one should respect
the user's command line efforts).
Test uses unittest.mock.patch to test &quo
Pam McA'Nulty added the comment:
This version of the patch just updates the docs. Since the quotes aren't
really necessary for the example to work, the patch removes the single quotes
from the example.
I don't think that the python unittest documentation should explai
Pam McA'Nulty added the comment:
Thanks, Zach for both the comments and the mention of the email bounce. I
changed jobs and didn't have this site listed in my "must update email address
list" (fixed now)
Should I re-update the doc patch and
Pam McA'Nulty added the comment:
Here's a version of the docs with double quotes
--
Added file:
http://bugs.python.org/file39033/cpython-22812-discovery-double-quotes-v3.patch
___
Python tracker
<http://bugs.python.o
34 matches
Mail list logo
