Changes by John Leitch :
--
nosy: +christian.heimes
___
Python tracker
<http://bugs.python.org/issue25019>
___
___
Python-bugs-list mailing list
Unsubscribe:
New submission from John Leitch:
Python 3.3, 3.4, and 3.5 suffer from a vulnerability caused by the behavior of
the product_setstate() function. When called, the function loops over the state
tuple provided and clamps each given index to a value within a range from 0 up
to the max number of
Changes by John Leitch :
Added file: http://bugs.python.org/file40401/product_setstate_Type_Confusion.py
___
Python tracker
<http://bugs.python.org/issue25021>
___
___
John Leitch added the comment:
Glancing over the code, I see the issues you describe. Tonight I will verify
your revised patch and report back.
--
___
Python tracker
<http://bugs.python.org/issue25
John Leitch added the comment:
All appears well.
--
___
Python tracker
<http://bugs.python.org/issue25021>
___
___
Python-bugs-list mailing list
Unsubscribe:
John Beck added the comment:
@haypo: Yes, that patch works (applied to 3.5.0rc3; proxy problems are
preventing me from updating my clone of the default branch at the moment) i.e.,
pyconfig.h shows:
#define HAVE_GETRANDOM_SYSCALL 1
To answer your other questions:
* Calling syscall
John Beck added the comment:
Yes, the syscall was failing with EINVAL.
--
___
Python tracker
<http://bugs.python.org/issue25003>
___
___
Python-bugs-list mailin
John Beck added the comment:
Sorry, let me try to clarify. ENOSYS is the correct errno value to check for,
for the situation (e.g., Solaris < 11.3) of a non-existent system call. But
EINVAL should also be checked for to make sure the system call was invoked with
proper parameters. My bui
John Beck added the comment:
Yes, those patches work, with a caveat. While testing this, I found out why I
had needed EINVAL earlier (and still do, for now): there is a bug in the
Solaris implementation of getrandom(2). If flags are 0 and the buffer size >
1024, then it fails with EIN
John Beck added the comment:
I have queried the engineer who owns the kernel bug and will post an update
once I hear back from him. But as it is already almost midnight on Friday in
his geo, it may well be Monday before I hear back.
--
___
Python
Changes by John Leitch :
--
nosy: +brycedarling
___
Python tracker
<http://bugs.python.org/issue25092>
___
___
Python-bugs-list mailing list
Unsubscribe:
John Beck added the comment:
The owner of the Solaris kernel bug has confirmed that he plans to get
the fix into both Solaris 12 and 11.3.
--
___
Python tracker
<http://bugs.python.org/issue25
John Beck added the comment:
I have tested your patch with 3.5, and it works fine, although I did have to
make a minor change to get test_os to pass. In test_os.py you had:
...
USE_GETENTROPY = ((sysconfig.get_config_var('HAVE_GETENTROPY') == 1)
New submission from John Taylor:
In the Windows Help File for Python 3.5:
17.2 multiprocessing
17.2.1.1 The Process class
2nd code example: "To show the individual process IDs involved, here is an
expanded example"
def info(title):
print(title)
print('module name:
John Taylor added the comment:
To follow up on my previous message, I looked at the documentation for
os.getppid().
It states:
Changed in version 3.2: Added support for Windows.
--
___
Python tracker
<http://bugs.python.org/issue25
John Beck added the comment:
Confirmed that test_os runs cleanly on Solaris 12, for each of:
* 2.7.10 (plus your patch from 98454:202c827f86df)
* 3.4.3 (plus your patch from 98455:83dc79eeaf7f)
* 3.5.0 (plus your patch from 98452:835085cc28cd)
* 3.6 (tip
John Gray added the comment:
I hit this issue with an "H:" homedrive that is on a network share, and then in
Windows is using "offline files" to keep a local copy. .idlerc was not cached
so IDLE worked when online/connected to my work network but not when I was
offl
John Gray added the comment:
For the h: drive issue mentioned above: This was on Python 2.7.10.
--
___
Python tracker
<http://bugs.python.org/issue14576>
___
___
John Gray added the comment:
See Issue14576 which is the same underlying issue.
--
nosy: +John Gray
___
Python tracker
<http://bugs.python.org/issue8231>
___
___
Changes by John Morrissey :
--
nosy: +johnmorr
___
Python tracker
<http://bugs.python.org/issue23735>
___
___
Python-bugs-list mailing list
Unsubscribe:
New submission from John Hagen:
According to the Python docs, optparse has been deprecated since Python 3.2,
but it does not emit a DeprecationWarning when imported Python 3.2+.
https://docs.python.org/3/library/optparse.html
PyCharm can uses these DeprecationWarnings to provide helpful
John Hagen added the comment:
First time trying to contribute to the Python standard library.
I attached a patch that is modeled off the deprecated imp module. The
DeprecationWarning message is taken from the Python docs:
https://docs.python.org/3/library/optparse.html
--
keywords
John Hagen added the comment:
@martin.panter My new patch fixes Lib/test_optparse.py by suppressing the
warning like test_imp does as you suggested.
@serhiy.storchaka I don't have a strong preference that it be a
DeprecationWarning vs. PendingDeprecationWarning since to me, both ge
Changes by John Hagen :
Removed file: http://bugs.python.org/file40913/optparse_deprecationwarning.patch
___
Python tracker
<http://bugs.python.org/issue25521>
___
___
John Hagen added the comment:
Is there any consensus on how to move forward with this? I feel there are at
least 4 options:
1) Do nothing.
Pro: No work.
Con: It feels misleading to the user since the docs clearly state it's
deprecated. Some users (especially new ones) may mis
John Runyon added the comment:
This is a duplicate of 20468, which has a patch submitted (over a year ago).
--
nosy: +jrunyon
___
Python tracker
<http://bugs.python.org/issue24
John Runyon added the comment:
*bump*.
This flat-out wrong documentation has already misled several people, and has
had a proposed patch with no comments for over a year.
--
nosy: +jrunyon
___
Python tracker
<http://bugs.python.org/issue20
John Runyon added the comment:
New proposed patch.
I understand not wanting to document an "internal only name", except that in
this case it rather needs to be documented. I would strongly prefer Angad's
patch to mine because you do, at times, need to know the actual name of t
New submission from John Yeung:
The math module docs state
Except when explicitly noted otherwise, all return values are floats.
But math.factorial isn't what I would call explicit about returning int:
math.factorial(x)
Return x factorial. Raises ValueError if x is not integral
New submission from John Walker:
In statistics, there is a FIXME on Line 250 above _decimal_to_ratio that says:
# FIXME This is faster than Fraction.from_decimal, but still too slow.
Half of the time is spent in a conversion in d.as_tuple(). Decimal internally
stores the digits as a string
John Walker added the comment:
Heres the output of running the benchmark on my machine:
Testing proposed implementation
number = 1
0.07098613299967838
number = 10
0.6952260910002224
number = 100
6.948197601999709
Testing current implementation
number = 1
0.141816276996
Changes by John Walker :
--
type: -> performance
___
Python tracker
<http://bugs.python.org/issue25928>
___
___
Python-bugs-list mailing list
Unsubscrib
John Walker added the comment:
> I guess there's some version mixup here: From Python 3.3 on
> the integrated C version of decimal does not store the digits
> as a string and does not have the private _int method.
Stefan, _int is a slot in Lib/_pydecimal.py. It should be defined
John Walker added the comment:
> That should only happen if the C version did not build for some reason:
Ahh, gotcha. I assume one instance where this happens is when the machine
doesn't have libmpdec.so
--
___
Python tracke
John Walker added the comment:
> No, the regular build uses the libmpdec that is shipped with
> Python. The external libmpdec.so only comes into play if you
> compile --with-system-libmpdec.
Oh, OK. I see whats happening. My distro deletes the shipped version and
compiles --wi
New submission from John Walker:
Minor fixes to comments and a docstring in Lib/tokenize.py I found while
looking for more important bugs.
afer -> after
alternately -> alternatively
intput -> input
argment -> argument
--
assignee: docs@python
components: Documentation
fil
Changes by John Walker :
--
nosy: +johnwalker
___
Python tracker
<http://bugs.python.org/issue25863>
___
___
Python-bugs-list mailing list
Unsubscribe:
John Walker added the comment:
You're welcome, have a happy new year. :)
--
___
Python tracker
<http://bugs.python.org/issue25977>
___
___
Python-bugs-list m
John Walker added the comment:
Here is Martin's message as a unit test. It checks utf-8 and the iso-2022
family except iso-2022-cn and iso-2022-cn-ext because they are not supported.
The errors occur with all iso-2022 charsets.
--
keywords: +patch
Added file: http://bugs.pytho
John Szakmeister added the comment:
FWIW, I'm seeing the same issue as Jason too, and his solution seems reasonable
to me.
--
nosy: +jszakmeister
___
Python tracker
<http://bugs.python.org/is
New submission from John Malmberg:
The _PyDumpTraceback and _Py_DumpTracebackThreads routines in traceback.h are
tagged with PyAPI_DATA attributes when they should be tagged with PyAPI_FUNC.
For platforms that use those attributes, this can cause run-time issues if
those methods are called
New submission from John Hagen:
The Python documentation recommends editors that can be used on Unix:
https://docs.python.org/3.5/using/unix.html#editors
If the intent is to advertise very excellent IDEs (as Geany and Komodo Edit are
listed), I suggest that PyCharm Community Edition
(https
New submission from John Beck:
A bug has been filed against Solaris' internal version of Python, which is
largely the same (including in this case) as the base version we get from
python.org. The bug is that os.defpath starts with ':' and thus any Python
script run with a null P
New submission from John Taylor:
The print statement does not display accurate results.
code:
print("%35d" % (1e21))
print("%35d" % (1e22))
print("%35d" % (1e23))
print("%35d" % (1e24))
print("%35d" % (1e25))
print(&qu
New submission from John Snow:
malloc_closere.c holds a static list of items: free_list.
The items are being allocated in the more_core method using VirtualAlloc /
mmap. However they never get released.
Here is the allocation code:
#ifdef MS_WIN32
item = (ITEM *)VirtualAlloc(NULL
New submission from John Beck:
Solaris ships Python versions 2.7, 3.4 and 3.5 at present. For 2.7,
we ship both 32-bit and 64-bit versions; for 3.4 and 3.5 we only ship
64-bit versions. For 2.7, we ship /usr/lib/python2.7/config/ with the
usual suspects (Makefile, Setup.config, config.c
Changes by John O'Connor :
--
nosy: +jcon
___
Python tracker
<http://bugs.python.org/issue21423>
___
___
Python-bugs-list mailing list
Unsubscr
New submission from John Lehr:
libplist raises an invalid file exception on loading properly formed binary
plists containing UID (0x80) values. The binary files were tested for form
with plutil.
Comments at line 706 state the value is defined but not in use in plists, and
the object is not
John Lehr added the comment:
I’m glad you found it in the Apple specification. I looked, but missed it. I
would absolutely defer to you on your assessment of the decoding.
> On Apr 7, 2016, at 1:46 AM, Serhiy Storchaka wrote:
>
>
> Serhiy Storchaka added the comment:
>
John Lehr added the comment:
I’m sorry, but the files in which I detected the problem cannot be circulated.
I will try to create a test account on Snapchat and generate some test data,
but I can’t do this anytime soon.
> On Apr 7, 2016, at 12:51 AM, SilentGhost wrote:
>
>
>
John Lehr added the comment:
Based on the format specification pointed to by Serhiy, perhaps this a better
patch, correcting size from previous patch submission and treating:
706,707c706,708
< # tokenH == 0x80 is documented as 'UID' and appears to be used for
<
John Hagen added the comment:
With 3.6.0a1 scheduled just around the corner, is there consensus about how to
begin this? I just signed the contributor agreement, so I should be able to
try to help if we have a plan on how to divide the work
New submission from John Hagen:
I suggest that the AutoNumberedEnum be added to the standard library for the
following reasons:
1) Provides a fundamental tool for defining a unique, abstract set of coupled
members
2) Avoids boilerplate @enum.unique for a very common use case of enumerations
3
John Hagen added the comment:
@Ethan, I hadn't tried to use the aenum AutoNumberEnum that way, but I agree
with Barry that I like it. To me that is the ideal case we should shoot for as
I think it's the best* long term and deviate only if practical concerns prevent
it.
So I am +1
New submission from John Nagle:
"robotparser" uses the default Python user agent when reading the "robots.txt"
file, and there's no parameter for changing that.
Unfortunately, the "mod_security" add-on for Apache web server, when used with
the standard OWA
New submission from John Beck:
Issue 8473 fixed a problem with lineendings in test_doctest, but it
appears not to work in verbose mode. Adding verbose=False to the
doctest.testfile() invocations in test_lineendings() fixes this.
Attaching a patch to fix this for both 2.7 and 3.4
John Nagle added the comment:
Will this be applied to the Python 2.7.9 library as well?
--
___
Python tracker
<http://bugs.python.org/issue23476>
___
___
Pytho
John Nagle added the comment:
Three years later, I'm converting to Python 3. Did this get fixed in Python 3?
--
___
Python tracker
<http://bugs.python.org/i
New submission from John Nagle:
I'm porting a large, working system from Python 2 to Python 3, using "six", so
the same code works with both. One part of the system works a lot like the
multiprocessing module, but predates it. It launches child processes with
"Popen"
John Nagle added the comment:
> Or just use pickle._Pickler instead of pickle.Pickler and like
> (implementation detail!).
Tried that. Changed my own code as follows:
25a26
>
71,72c72,73
< self.reader = pickle.Unpickler(self.proc.stdout)# set up reader
<
John Nagle added the comment:
"minimize you data" - that's a big job here. Where are the tests for "pickle"?
Is there one that talks to a subprocess over a pipe? Maybe I can adapt that.
--
___
Python tracker
<http:
John Nagle added the comment:
More info: the problem is on the "unpickle" side. If I use _Unpickle and
Pickle, so the unpickle side is in Python, but the pickle side is in C, no
problem. If I use Unpickle and _Pickle, so the unpickle side is
New submission from John Nagle:
Installing Python 3.4.2 on CentOS 6. Clean install. Using procedure in README
file:
./configure
make
make test
2 tests fail in "make test" The first one is because the FTP client
test is trying to test against a site that is long gone, the Digital
John Hergenroeder added the comment:
If no-one else wants it, I'd love to tackle this as my first Python (and OSS in
general) contribution. Attached is a one-line patch that just does a
CHECK_CLOSED call in buffered_peek and is modeled on the pattern in the
buffered_flush function just
John Hergenroeder added the comment:
Thanks for the feedback, Berker!
I've added a test case that closes a buffered reader and then attempts to both
peek and read1 it. I tacked it onto the end of the BufferedReaderTest class in
test_io, but let me know if there's a better place
New submission from John Nagle:
ssl.wrap_socket() always uses the SSL certificate associated with the raw IP
address, rather than using the server_host feature of TLS. Even when
wrap_socket is used before calling "connect(port, host)", the "host" parameter
isn't us
John Nagle added the comment:
If SSL error reporting is getting some attention, something should be done to
provide better text messages for the SSL errors. All certificate verify
exceptions return the string "certificate verify failed (_ssl.c:581)". The line
number in _ss
John Nagle added the comment:
I'm using wrap_socket because I want to read the details of a server's SSL
certificate.
"Starting from Python 3.2, it can be more flexible to use
SSLContext.wrap_socket() instead" does not convey that ssl.wrap_socket() will
fail to con
John Beck added the comment:
We (Solaris engineering) have hit this issue after migrating from 2.6
being our default version of Python to 2.7 being the default. The
specific component that broke was vim (version 7.4), trying to compile
if_python.c:
"/usr/include/python2.7/pyport.h"
John Hergenroeder added the comment:
Thanks!
I submitted my contributor agreement form last week -- is there anything I can
do to improve this patch while I wait for that to process?
--
___
Python tracker
<http://bugs.python.org/issue23
John Ehresman added the comment:
I've confirmed that the test included in the 3/25/15 patch fails without the
change to ffi.c. I think the 11/5/14 change fixed the bug for calling into a C
function and converting the return value, but did not address the callback
case. The new patch
John Ehresman added the comment:
I think at a minimum, a return should be added in the cases that call
GenerateConsoleCtrlEvent and it fails.
Here's a more radical proposal, though: deprecate kill() on Windows and add a
function that calls GenerateConsoleCtrlEvent and another that
John Ehresman added the comment:
A problem with os.kill with CTRL_C_EVENT is that CTRL_C_EVENT == 0 and on unix
kill w/ a signal number of 0 is how you test to see if a process is running.
This means that code written on unix to see if a process exists will try to
send a ctrl-c to the other
John Ehresman added the comment:
Here's the 1st draft of a test for interrupts during time.sleep(). It creates
a thread to generate the ctrl-c events which seems to work well (note that
kill() on win32 is quite limited in terms of sending events to other
processes). The creation and u
New submission from John Ehresman:
os.kill() on Windows cannot act like it does on non-windows platforms because
of differences in the underlying platforms. I think only kill() with a signal
number of 9 (terminate process unconditionally) and a signal number of 0 (test
to see if process
John Ehresman added the comment:
I've created issue #23948 for the idea of deprecating os.kill().
Is a patch needed for adding a return in the error case? It's that way in 2.7
and I'm struggling to come up with a reason why it shouldn't be added other
than strict ba
John Ehresman added the comment:
Part of the issue here is that GenerateConsoleCtrlEvent doesn't work like kill
w/ SIGINT does on unix -- it only works if the the target process id is 0 and
then it generates the signal in all processes that share the console. An
alternate proposal here
John Ehresman added the comment:
GenerateConsoleCtrlEvent has different limitations for CTRL_BREAK_EVENT and
CTRL_C_EVENT according to MSDN; I was referring to the CTRL_C_EVENT
limitations. Which python level signal handler will CTRL_BREAK_EVENT trigger
John Ehresman added the comment:
Interesting -- I didn't know about removing the ignore flag in the child
process. The question is whether this is close enough to the kill w/ SIGINT
behavior on unix to use the same name. I think that there are enough
differences to warrant a Wi
New submission from john kaiser:
found error when naming variables with basic functions
how to replicate
while=123 #while should be treated as variable name
while True: #this should be treated as a function
print while #this should be as a variable name
result:
File "C:\Users
John Hergenroeder added the comment:
It looks like my contributor form has gone through -- what should my next steps
here be? Thanks!
--
___
Python tracker
<http://bugs.python.org/issue23
Changes by John Beck :
--
nosy: +jbeck
___
Python tracker
<http://bugs.python.org/issue1298835>
___
___
Python-bugs-list mailing list
Unsubscribe:
New submission from John Beck:
The man page for Python (3.4 and 3.5) says:
-I Run Python in isolated mode. This also implies -E and -S. In
isolated mode sys.path contains neither the scripts directory
nor the users site-packages directory. All PYTHON
John Beck added the comment:
Adding Christian Heimes to the nosy list; as the author of the fix for
issue 16499, he seems an excellent person to answer the question and
offer advice on the approaches discussed herein.
--
nosy: +christian.heimes
John Beck added the comment:
Thank you very much for clarifying that. I have updated the bug Title
accordingly.
--
title: man page says -I implies -S. code says -s. Should it be both? -> man
page says -I implies -S. code says -s.
___
Python trac
John Hergenroeder added the comment:
Wonderful! Thanks for your help, Berker!
--
___
Python tracker
<http://bugs.python.org/issue23796>
___
___
Python-bugs-list m
New submission from John Runyon:
the documentation
(https://docs.python.org/2/library/threading.html#threading.Timer) lists
"threading.Timer" as a class. It is not, which means that (for example) you can
not use it in isinstance(). "threading._Timer" is a clas
John Runyon added the comment:
Concise documentation isn't my forte, but my confusion would've been avoided
with a note that "for historical reasons, threading.Timer is actually a factory
function for the underlying class threading._Timer" or somethin
New submission from John Didion:
The following code works fine when I run it on OSX 10.9, but causes a
segmentation fault when run on linux. Specifically, the Travis build on python
3.5.2 results in a segfault when the last line is uncommented.
import argparse
parser = argparse.ArgumentParser
John Didion added the comment:
This code also works fine when I run it myself on python 3.5.1 on an SL6
machine, so it's either specific to 3.5.2 or it's very platform-specific.
--
___
Python tracker
<http://bugs.python.o
John Didion added the comment:
I can't reproduce it with 3.5.2 on SL6 either. So it must be a weird issue
specific to whatever environment they're using for builds on Travis. I'll close
this and submit it as a bug over there.
--
resolution: -> works for me
stat
New submission from John Leitch:
Python 3.5.2 suffers from a use after free vulnerability caused by the behavior
of the LZMADecompressor.decompress method. The problem exists due to a dangling
pointer created by an incomplete error path in the _lzma!decompress function.
static PyObject
Changes by John Leitch :
Added file: http://bugs.python.org/file44828/Py35_LZMADecompressor.py
___
Python tracker
<http://bugs.python.org/issue28275>
___
___
Python-bug
John Leitch added the comment:
Of course. Attached is a new patch that includes test coverage. It crashes on
failure as there isn't any reasonable way to monitor for this kind of undefined
behavior, but it's better than nothing.
--
Added file: http://bugs.python.org
New submission from John Leitch:
Python 3.5.2 suffers from a type confusion vulnerability in the
chain.__setstate__ method of the itertools module. The issue exists due to lack
of argument validation in the chain_setstate() function:
static PyObject *
chain_setstate(chainobject *lz, PyObject
Changes by John Leitch :
Added file: http://bugs.python.org/file44900/Py35_itertools.py
___
Python tracker
<http://bugs.python.org/issue28322>
___
___
Python-bugs-list m
New submission from John Taylor:
The python-3.6.0b2-amd64.exe binary installs the 64-bit version of python, but
the binary itself is only 32-bit. I would like this to be a 64-bit binary so
that Python can easily be installed on Windows Server 2016 Nano Server. Since
this OS version will
John Taylor added the comment:
python-3.6.0b2-embed-amd64.zip will load the interpreter as is easy to install.
The Python Embedded Distribution documentation mentions needing ucrtbase.dll,
which is already installed on Nano Server.
One small pain point is that ctrl-z seems to exit/suspend
New submission from John Ehresman:
The index returned by _PyEval_RequestCodeExtraIndex is currently specific to
the current thread state. This means that there will be problems if the index
is used on another thread. It would be possible to set things up in my code so
that
New submission from John Nagle:
urllib.robotparser.RobotFileParser always uses the default Python user agent.
This agent is now blacklisted by many sites, and it's not possible to read the
robots.txt file at all.
--
components: Library (Lib)
messages: 281314
nosy: nagle
pri
901 - 1000 of 1249 matches
Mail list logo
