Jon Brandvein added the comment:
Regarding the patch: I'd also like to see sys.stdout.flush() and
sys.stderr.flush() between "exitcode = self._boostrap()" and "exit(exitcode)"
in /Lib/multiprocessing/forking.py :: main(). (The extra stderr flush would be
for sym
New submission from Jon Brandvein :
Currently the multiprocessing library calls a hard exit function (os._exit
under unix, ExitProcess under Windows) to terminate the child process.
Under unix, this is necessary because the child is forked without exec-ing.
Calling sys.exit() would make it
Jon Brandvein added the comment:
Patch looks fine. I like the use of "finally" for the flush.
--
___
Python tracker
<http://bugs.python.org/issue13812>
___
__
Jon Brandvein added the comment:
Good point. I don't think those particular behaviors are documented, so I'm not
sure whether we need to worry about breaking them.
--
___
Python tracker
<http://bugs.python.o
New submission from Jon Brandvein :
Raising SystemExit manually, or calling sys.exit, with an argument of "True" or
"False" results in no output to the screen. According to
Doc/library/exceptions.rst and Doc/library/sys.rst, any object that is not an
integer or None
New submission from Jon Brandvein :
In a child process, raising SystemExit or calling sys.exit with a non-integer,
non-string argument value causes a TypeError at Lib/multiprocessing/process.py
:: _bootstrap. This is from concatenating the argument with '\n' and writing it
Jon Brandvein added the comment:
> If such a function is added, I'd like the option to not indent empty lines:
> trailing spaces are often not a good idea.
>From dedent's documentation, it wasn't immediately clear to me that it ignores
>blank lines when determi
Jon Brandvein added the comment:
Also, as Brett pointed out to me in #13853, bool is a subclass of int, so they
should follow the same code path. I suggest replacing
elif type(e.args[0]) is int:
exitcode = e.args[0]
with something like
elif isinstance(e.args[0], int
Jon Bringhurst added the comment:
I just ran into this while using the smtplib example on:
2.6 (r26:66714, Jan 17 2012, 11:02:11)
GCC 4.1.2 20080704 (Red Hat 4.1.2-44)
Running the program simply gives a "Segmentation Fault (core dumped)"
Running it under gdb...
[Thread debug
Changes by Jon Bringhurst :
--
type: -> crash
versions: +Python 2.6 -Python 2.2
___
Python tracker
<http://bugs.python.org/issue1003195>
___
___
Python-
New submission from Jon Bringhurst :
I just ran into this while using the smtplib example on:
2.6 (r26:66714, Jan 17 2012, 11:02:11)
GCC 4.1.2 20080704 (Red Hat 4.1.2-44)
Running the program simply gives a "Segmentation Fault (core dumped)"
Running it under gdb...
[Thread debug
Changes by Jon Brandvein :
--
nosy: +brandj
___
Python tracker
<http://bugs.python.org/issue10482>
___
___
Python-bugs-list mailing list
Unsubscribe:
Changes by Jon Brandvein :
--
nosy: +brandj
___
Python tracker
<http://bugs.python.org/issue4806>
___
___
Python-bugs-list mailing list
Unsubscribe:
Jon Vaughan added the comment:
FWIW I upgraded to ubuntu pangolin beta over the weekend, which includes
2.7.3rc1, and I'm also experiencing a problem with urandom.
File "/usr/lib/python2.7/email/utils.py", line 27, in
import random
File "/usr/lib/python2.7/ran
Jon Vaughan added the comment:
Victor - yes that was it; a mixture of a 2.7.2 virtual env and 2.7.3.
Apologies for any nuisance caused.
--
___
Python tracker
<http://bugs.python.org/issue13
New submission from Jon Oberheide :
The multiprocessing module performs a time-dependent comparison of the HMAC
digest used for authentication:
def deliver_challenge(connection, authkey):
import hmac
assert isinstance(authkey, bytes)
message = os.urandom(MESSAGE_LENGTH
Jon Oberheide added the comment:
In fact, it'd probably be useful to have a time_independenct_comparison()
helper function somewhere in general.
--
___
Python tracker
<http://bugs.python.org/is
Jon Oberheide added the comment:
Ah yeah, I suppose it's not be exploitable in this case due to the challenge
nonce.
However, it might still be a good thing to fix for to set an example for other
hmac module users (internal or external) that might not have the same situ
Jon Oberheide added the comment:
You call it obfuscating, I call it security correctness and developer
education. Tomayto, tomahto. ;-)
Anywho, your call of course, feel free to close.
--
___
Python tracker
<http://bugs.python.org/issue14
Jon Oberheide added the comment:
> One thing that could definitely be interesting is to look through the
> code base and example to see if a similar - but vulnerable - pattern
> is used, and fix such occurrences.
Based on some quick greps, I didn't see many internal users o
Jon Oberheide added the comment:
Will do!
--
___
Python tracker
<http://bugs.python.org/issue14532>
___
___
Python-bugs-list mailing list
Unsubscribe:
Jon Oberheide added the comment:
Here's a v1. Works with both str and bytes types for Python 3.x.
Not sure I'm completely happy with the docs, but I'd appreciate any feedback on
them!
--
keywords: +patch
Added file: http://bugs.python.org/file25186/hmac-time-indep
Jon Oberheide added the comment:
> This is not time independent. Is it an issue?
You're correct, the length check does leak the length of the expected digest as
a performance enhancement (otherwise, your comparison runtime is bounded by the
length of the attackers input).
G
Jon Oberheide added the comment:
> You could rewrite:
>
> result |= x ^ y
>
> as:
>
> result |= (x != y)
You could, but it's best not to introduce any conditional branching based if at
all possible. For reference, see:
http://rdist.root.org/2009/05/
Jon Oberheide added the comment:
Here's a v2 patch. Changes include checking the input types via isinstance,
test cases to exercise the type checking, and a note documenting the leak of
the input length.
--
Added file: http://bugs.python.org/file25197/hmac-time-independent-v2.
New submission from Jon Ribbens :
email.headers can wrap headers by putting a FWS as the very first thing in the
output:
>>> from email.header import Header
>>> Header("a" * 67, header_name="Content-ID").encode()
'\n aa
Jon Ribbens added the comment:
It is not correct folding. It might not be explicitly forbidden, but it is
clearly unwise, and is breaking 'conservative in what you send'. Outlook will
not be the only program that fails to parse Pytho
Jon Ribbens added the comment:
I did read the RFCs. I suspect the [CFWS] in the msg-id is for the benefit of
the references production which contains a list of msg-ids. The 78-character
suggested line length limit is explicitly noted as being for display purposes,
and therefore is of little
New submission from Jon McMahon :
Subclasses of io.IOBase can be instantiated with abstractmethod()s, even though
ABCs are supposed to prevent this from happening. I'm guessing this has to do
with io using the _io C module because the alternative pure-python
implementation _pyio doesn&#
New submission from Jon Ribbens:
The email module, when creating base64-encoded text parts, does not process
line breaks correctly - RFC 2045 s6.8 says that line breaks must be converted
to CRLF before base64-encoding, and the email module is not doing this.
>>> from email.mime.te
New submission from Jon Ribbens:
The email module, when creating text parts using character encoding utf-8,
base64-encodes the output even though this is often inappropriate (e.g. if it
is a Western language it is almost never appropriate).
>>> from email.mime.text import MIMET
Jon Ribbens added the comment:
Just a note for anyone finding this in searching results: it appears that what
David means by "python3 API" is actually a new API in Python 3.6
(email.message.EmailMessage).
--
___
Python trac
Jon Ribbens added the comment:
OK cool, but please note that this is a MIME issue not an SMTP issue - if the
message has text that is being base64-encoded then it must use CRLF line breaks
regardless of whether SMTP is involved or not
Jon Ribbens added the comment:
So on further investigation, with the new API and policy=SMTP, it does generate
correct base64 output. So I guess on the basis that the new version can
generate the right output, and it appears to be a deliberate choice that the
default policy breaks the RFCs
New submission from Jon Dufresne:
After upgrading to Python 3.6, I'm working towards cleaning up
"DeprecationWarning: invalid escape sequence". I've noticed that the
Deprecation warning only appears on the first run. It looks like once the code
is compiled to `__pycache
Jon Dufresne added the comment:
I see.
I think if the goal is for developers to see and fix these DeprecationWarnings,
it would help if the warnings were reproducible without taking steps different
from normal Python development. TBH, this is the first time I've ever used the
-B CLI arg
Jon Dufresne added the comment:
Understood. Thanks for the response. I'll have to keep this in mind as I debug
these warnings in the future.
--
resolution: -> not a bug
stage: -> resolved
status: open -> closed
___
Python
New submission from Jon Dufresne:
Lib has some patterns that could be easily discovered and cleaned up. Doing so
will reduce the number of unnecessary temporary lists in memory and unnecessary
function calls. It will also take advantage of Python's own rich features in a
way that bette
Changes by Jon Dufresne :
--
pull_requests: +2015
___
Python tracker
<http://bugs.python.org/issue28867>
___
___
Python-bugs-list mailing list
Unsubscribe:
Change by Jon Janzen :
--
pull_requests: +12152
___
Python tracker
<https://bugs.python.org/issue26707>
___
___
Python-bugs-list mailing list
Unsubscribe:
Jon Janzen added the comment:
I recently upgraded my python version and my hot-patch broke due to changes in
bpo-32072 (GH-4455).
It reminded me of this b.p.o., and after reading through the messages to remind
myself where the patch stood I realized that my tone friendly towards the end
New submission from Jon Janzen :
Per the documentation and in-line code warnings, the old API for plistlib was
deprecated in version 3.4. My understanding is that deprecated functionality is
to be removed in the next major version, so this code is long overdue for
removal
Change by Jon Janzen :
--
keywords: +patch
pull_requests: +12466
stage: -> patch review
___
Python tracker
<https://bugs.python.org/issue36409>
___
___
Py
Jon Janzen added the comment:
Ah, I misinterpreted PEP4. I thought it only applied to modules as a whole
(e.g. plistlib) rather than individual functionality within that module. I'll
close my PR and wait until 3.9 is accepting patches
--
versions: +Python 3.9 -Pytho
New submission from Jon Dufresne :
Here: https://docs.python.org/3/reference/datamodel.html#object.__get__
The __get__ signature is defined as:
object.__get__(self, instance, owner)
But here: https://docs.python.org/3/howto/descriptor.html#descriptor-protocol
It is defined as:
descr
Jon Janzen added the comment:
Hello,
I have attached a file extracted from the database of the 2Do App for iOS and
macOS. The file contains information about tags used in the app.
plistlib cannot currently parse this file because it lacks the ability to read
byte 0x80 (UID).
I believe the
Jon Janzen added the comment:
@serhiy.storchaka: I've implemented a UID wrapper class
I've also updated the parser and writer classes to support the UID wrapper. The
implementations for reading/writing XML UID tags match the implementations
given by Apple's plutil distrib
Jon Janzen added the comment:
Ping
--
___
Python tracker
<https://bugs.python.org/issue26707>
___
___
Python-bugs-list mailing list
Unsubscribe:
Jon Janzen added the comment:
Support for KeyedArchives are not limited to the Swift implementation I linked
to. They have been supported since Mac OS X since 10.2 (long before Swift came
around). The documentation
(https://developer.apple.com/documentation/foundation/nskeyedarchiver
Jon Janzen added the comment:
Ping
--
___
Python tracker
<https://bugs.python.org/issue26707>
___
___
Python-bugs-list mailing list
Unsubscribe:
New submission from Jon Banafato :
Calling loop.close() on an eventloop configured to use a ProcessPoolExecutor
can result in an OSError.
Expected behavior: no exception raised.
Actual behavior: an OSError is raised, and following this call, quit() fails to
terminate the process gracefully
New submission from Jon Ribbens :
The documentation for email.message_from_binary_file is missing a
line-continuation backslash at the end of the `.. function::` line which means
the output formatting is mangled and it has no permalink.
--
assignee: docs@python
components
Change by Jon Ribbens :
--
keywords: +patch
pull_requests: +7831
stage: -> patch review
___
Python tracker
<https://bugs.python.org/issue34124>
___
___
Py
New submission from Jon Irenicus:
Python's really slowing my computer down.
After running my script, the computer grinds to a halt and it's performance
drops.
Even after a reboot, the problem still persists.
--
components: Windows
messages: 191661
nosy: jon_irenicus
priori
Jon Irenicus added the comment:
The problem is when i run my python script, it somehow slows the whole computer
down.
I checked my cpu usage, ram usage and disk usage, but nothing comes up.
The script isn't big, it's only about 10kb big.
--
status: pendi
Jon Irenicus added the comment:
#David Edelsohn
It's not changing anything.
with open('url_list.txt') as f:
content = f.readlines()
content = ''.join(content)
content = list(content)
if content[0] == 'h' and content[1] == 't' and co
New submission from Jon Foster:
I recently looked at using the ipaddress module in a project, and noticed some
discrepencies between the code and the documentation, and some things that
weren't documented. A patch to fix these is attached.
* The IPv4Network.__init__ documentation wr
Jon Foster added the comment:
(If this is accepted, please consider it for backport to 3.3 too. It is just a
documentation improvement).
--
type: -> enhancement
versions: +Python 3.3
___
Python tracker
<http://bugs.python.org/issu
New submission from Jon Foster:
Short version:
Validation of netmasks and hostmasks in IPv4Network is wrong: it rejects many
valid netmasks, it accepts many invalid netmasks and hostmasks, and it sometimes
throws the wrong exception. Patch attached.
Long version:
Wrongly rejecting hostmasks
Changes by Jon Foster :
--
nosy: +jongfoster
___
Python tracker
<http://bugs.python.org/issue16531>
___
___
Python-bugs-list mailing list
Unsubscribe:
Jon Oberheide added the comment:
v3 patch, based on feedback from the review here:
http://bugs.python.org/review/14532/show
--
Added file: http://bugs.python.org/file25262/hmac-time-independent-v3.patch
___
Python tracker
<http://bugs.python.
Jon Oberheide added the comment:
I have used the name "secure_compare" in the past for such a function. That
said, I don't have strong feelings either way about the naming, so I'll yield
to the others.
--
___
P
Jon Oberheide added the comment:
Ok, patch v4 uploaded. Only change is the rename to "secure_compare".
--
Added file: http://bugs.python.org/file25414/hmac-time-independent-v4.patch
___
Python tracker
<http://bugs.python.o
Jon Oberheide added the comment:
> You should explain what you already said: it is not a risk because the
> length of a HMAC is fixed.
Well, that's not entirely accurate. Exposing the length of the HMAC can expose
what underlying hash is being used (eg. HMAC-SHA1 has different
New submission from Jon Oberheide :
Hi all,
I was informed that the hmac.secure_compare() function added in 14532 is not
time-independent when processing unicode values:
"The function as given is probably not timing independent if the attacker can
provide unicode values. This is becaus
Jon Oberheide added the comment:
Thanks for the feedback, haypo. I've updated the patch to use unicode-internal.
As long as the encode() of the expected non-attacker-controlled digest is not
dependent on the actual contents of the digest, we should be good.
--
Added file:
Jon Oberheide added the comment:
Sounds good to me, Nick.
--
___
Python tracker
<http://bugs.python.org/issue14955>
___
___
Python-bugs-list mailing list
Unsub
Jon Oberheide added the comment:
Wow, that escalated quickly. :-)
Nick, thanks for keeping things focused and on track.
To recap, the primary motivation here is two-fold. First, folks are using ==
pretty frequently in an unsafe manner when comparing digests, signatures, and
other fixed
Jon Oberheide added the comment:
On a side note, it may be useful to follow the conventions that already exist
in OpenBSD for their timingsafe_bcmp(3):
http://www.rootr.net/man/man/timingsafe_bcmp/3
"timingsafe" may be a more reasonable naming convention that is a bit less
New submission from Jon Clements :
I'm not a numeric expert but I was looking at a post on S/O which related to
converting a Fraction to a certain amount of decimal places. I've had a hunt on
the tracker but couldn't find anything relevant, but if I've missed it, I
apologi
Jon Clements added the comment:
Mark - I bow to your superiour knowledge here. However, would not a classmethod
of .from_fraction be welcome?
ie, I could write:
d = D.from_fraction(5, 7)
Then the documents labour the point about what you've mentioned?
Just an idea, but fully realise y
Jon Clements added the comment:
Not sure what's going on with my machine today: keep sending things to early.
I meant:
D.from_fraction(F)
where if F is not of type Fraction, then the args are used to construct a
Fraction - so can use an existing or creat
Jon Clements added the comment:
The more I think about this - the shades of grey kick in.
D.from_fraction(F or creatable F)
Then it would be 'reasonable to assume' for a F.to_decimal() to exist.
Possibly with an optional context argument.
Then, what happens if I do D('2.4
New submission from Jon Obermark:
If they are not going to call the __metaclass__ or the class __new__, then they
should return `set` objects instead of subclass objects, so that it is clear
what is going on.
As it is, the results of set operations receive some subclass information but
not
Jon Obermark added the comment:
The closing author is correct, the use case is adequately covered by __init__,
and that has been fixed in 3. It makes sense this will not be backported.
--
___
Python tracker
<http://bugs.python.org/issue15
New submission from Jon Brandvein:
def foo():
try:
return 1
finally;
return 2
print(foo()) # 2
I've seen this peculiar case discussed on a few blogs lately, but was unable to
find confirmation that this behavior is defined.
In the try/finally section of Doc/refe
Changes by Jon Henry :
--
nosy: +jhenry82
___
Python tracker
<http://bugs.python.org/issue9720>
___
___
Python-bugs-list mailing list
Unsubscribe:
Changes by Jon Clements :
--
nosy: +joncle
___
Python tracker
<http://bugs.python.org/issue19363>
___
___
Python-bugs-list mailing list
Unsubscribe:
Changes by Jon Gauthier :
--
keywords: +patch
Added file: http://bugs.python.org/file32678/issue19164.patch
___
Python tracker
<http://bugs.python.org/issue19
Jon Clements added the comment:
Was looking up epoll.modify and noticed in the docs it's listed as "
Modify a register file descriptor." - I believe that should be "Modify a
registered file descriptor"...
--
nosy: +joncle
Jon Poler added the comment:
I will give this a shot if it is just hard-coding a table with errno names.
Dynamically scraping the errno names and inserting them with the exception
hierarchy might be beyond me since I've never used Sphinx before.
--
nosy: +jon.
Jon Poler added the comment:
I'm not entirely sure that I'm interpreting what you are looking for correctly,
but here is what the table looks like with literalinclude.
--
keywords: +patch
Added file: http://bugs.python.org/file36365/OS_exceptions_t
Jon Poler added the comment:
Antoine:
I'll look in to this unless you want do so yourself.
Thanks.
--
nosy: +jon.poler
___
Python tracker
<http://bugs.python.org/is
Jon Poler added the comment:
Serhiy, should I submit these fixes as separate patches? E.g. one patch for the
warnings module, and another for the socket module?
More generally, should the items included in __all__ be derived from the items
described in the documentation? For instance, only
Jon Poler added the comment:
Here is a patch that changes __all__ in Lib/warnings.py to include the
functions mentioned in the library reference
https://docs.python.org/dev/library/warnings.html#available-functions. A
unittest is included.
This is my first patch, so comments/feedback are
Jon Poler added the comment:
Here's one way to accomplish this. Please see attached
os_exceptions_table_V2.patch.
I wasn't having much luck trying to use ReST, so I took advantage of the fact
that the Doc/conf.py file is executed every time sphinx-build is run. conf.py
imports and
New submission from Jon Poler:
It looks like there might be a contradiction in the documentation of import in
the language reference. In the loading subsection
https://docs.python.org/dev/reference/import.html#loading, first bulleted list
of the section, it specifies that if a loader fails
Jon Poler added the comment:
Thanks, Brett!
--
___
Python tracker
<http://bugs.python.org/issue22191>
___
___
Python-bugs-list mailing list
Unsubscribe:
Changes by Jon Parise :
--
nosy: -jon
___
Python tracker
<http://bugs.python.org/issue5755>
___
___
Python-bugs-list mailing list
Unsubscribe:
https://mail.pyth
New submission from Jon Shemitz:
The tutorial says "Each value is an object, and therefore has a class (also
called its type). It is stored as object.__class__."
So, I tried
>>> 3.__class__
File "", line 1
3.__class__
^
SyntaxErr
Jon Shemitz added the comment:
That makes sense. Perhaps, then, the tutorial should include the FAQ? (I
can't be the only person who thought to try this.)
On Wed, Feb 19, 2014 at 3:59 PM, R. David Murray wrote:
>
> R. David Murray added the comment:
>
> It's actually almo
New submission from Jon Debonis :
Added ability to insert cookies into cookie jar.
Fixed problem where some domain names are prepended with '.' and others
were not.
Fixed problem with _LWPCookieJar.py to handle case where version = None
import urllib2, urllib, time
import
New submission from Jon Parise :
reference/datamodel.rst misspells "Custom" as "Custon". The attached
patch fixes that.
--
assignee: georg.brandl
components: Documentation
files: datamodel.custon.diff
keywords: patch
messages: 92157
nosy: georg.brandl, jon
severity:
New submission from Jon Foster :
The documentation for the C API function PyUnicode_DecodeUTF16() does
not match the code.
If *byteorder is 1 or -1, the documentation says that the function looks
for a BOM. It doesn't. This patch updates the documentation to match
the code.
(Also, I
New submission from Jon Parise :
I've sometimes found it useful to define a convenience macro named
Py_RETURN_BOOL(x) which is essentially:
#define Py_RETURN_BOOL(x) if (x) Py_RETURN_TRUE; else Py_RETURN_FALSE
It's useful for implementing functions which return Boolean values based
Jon Parise added the comment:
Also attached is a short set of examples of how this macro could be used
in the Python source tree.
--
Added file: http://bugs.python.org/file14983/Py_RETURN_BOOL.examples.patch
___
Python tracker
<h
Jon Parise added the comment:
Also attached is a small documentation patch.
--
Added file: http://bugs.python.org/file14984/Py_RETURN_BOOL.doc.patch
___
Python tracker
<http://bugs.python.org/issue7
Jon Parise added the comment:
I agree, as well.
I didn't consider PyBool_FromLong() because I was expecting to solve the
problem using a macro, but that is clearly not the best approach here
(insignificant function call overhead
New submission from Jon Parise :
The _static/opensearch.xml output on docs.python.org for the 3.1 and 3.2
(dev/py3k) branches still refers to the 3.0 documentation.
Doc/conf.py's html_use_opensearch value should be updated in those
source branches to reflect their updated version nu
Changes by Jon Parise :
--
nosy: +jon
___
Python tracker
<http://bugs.python.org/issue7060>
___
___
Python-bugs-list mailing list
Unsubscribe:
http://mail.pyth
101 - 200 of 248 matches
Mail list logo
