Changes by Raymond Hettinger raymond.hettin...@gmail.com:
--
assignee: rhettinger -
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue21793
___
___
gladman added the comment:
I notice on the documentation for Python 3.5 that this proposed addition is not
mentioned. Is it still the intention to add this proposed change to Python 3.5?
--
___
Python tracker rep...@bugs.python.org
Changes by Raymond Hettinger raymond.hettin...@gmail.com:
--
resolution: - rejected
status: open - closed
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue9536
___
Bohuslav Slavek Kabrda added the comment:
Attaching a new version of patch:
- Rebased to latest default branch
- Simplified prints
- Using OSError instead of IOError
Hopefully this is the final version :)
--
Added file:
Changes by Serhiy Storchaka storch...@gmail.com:
--
assignee: - serhiy.storchaka
nosy: +serhiy.storchaka
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue21793
___
STINNER Victor added the comment:
I see that the issue #22486 is still open.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue22477
___
___
STINNER Victor added the comment:
What's the status of this issue? See also the issue #22477.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue22486
___
Ned Deily added the comment:
The changes for 3.4 are incomplete:
import ssl
Traceback (most recent call last):
File stdin, line 1, in module
File /py/dev/34/source/Lib/ssl.py, line 122, in module
from _ssl import PROTOCOL_SSLv3, PROTOCOL_SSLv23, PROTOCOL_TLSv1
ImportError: cannot
Serhiy Storchaka added the comment:
Here is a patch which addresses both Mark's suggestions.
* math.gcd() now work with arbitrary Python objects implementing __index__.
* fractions.gcd() and Fraction's constructor now use math.gcd() if both
arguments are int, but also support non-ints (e.g.
Changes by Serhiy Storchaka storch...@gmail.com:
Added file: http://bugs.python.org/file37422/lehmer_gcd_8.patch
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue22486
___
Mark Summerfield added the comment:
In message
http://bugs.python.org/issue17914#msg188626
Victor Stenner says
On Windows, GetSystemInfo() is called instead of reading an environment
variable. I suppose that this function is more reliable.
From my reading, and based on feedback from one of my
Roundup Robot added the comment:
New changeset 773e55c95703 by Victor Stinner in branch '3.4':
Issue #22935: Fix ssl module when SSLv3 protocol is not supported
https://hg.python.org/cpython/rev/773e55c95703
New changeset fb1ffd40d33e by Victor Stinner in branch 'default':
Issue #22935: Fix
Roundup Robot added the comment:
New changeset f0297263a1e8 by Victor Stinner in branch '3.4':
Issue #22935: Fix test_ssl when the SSLv3 protocol is not supported
https://hg.python.org/cpython/rev/f0297263a1e8
--
___
Python tracker
STINNER Victor added the comment:
The changes for 3.4 are incomplete
Ok, I fixed most obvious issues. There is a major severe issue in Lib/ssl.py:
def get_server_certificate(addr, ssl_version=PROTOCOL_SSLv3, ca_certs=None):
...
This line fails if PROTOCOL_SSLv3 name does not
STINNER Victor added the comment:
Oh, in Python 3.4, create_default_context() uses PROTOCOL_SSLv23, SSLSocket,
wrap_socket() and _create_unverified_context() use PROTOCOL_SSLv23 by default.
In Python 3.5, get_server_certificate() now uses PROTOCOL_SSLv23 by default
because test_ssl failed on
STINNER Victor added the comment:
From my reading, and based on feedback from one of my customers, I believe he
is correct and that GetSystemInfo() ought to be used on Windows. (It is
available in pywin32 win32api.)
Please open a new issue to suggest this enhancement, this issue is closed.
STINNER Victor added the comment:
get_server_certificate_sslv23.patch: Patch to use PROTOCOL_SSLv23 by default in
get_server_certificate(), as done in Python 2.7 and 3.5.
--
Added file: http://bugs.python.org/file37424/get_server_certificate_sslv23.patch
New submission from E Roberts:
New to the world of Python. The picture attached is an error that a teacher at
my school is receiving when he tries to run anything in IDLE.
I know nothing about coding/python/idle or anything of that nature.
Sorry I am of little help.
Please can someone help
STINNER Victor added the comment:
The problem is that your student created a file called random.py which
conflicts with the module random of the Python standard library. Please
rename the random.py file to random.py and remove .pyc files (ex: random.pyc or
__pycache__/random*pyc).
--
STINNER Victor added the comment:
Catching TypeError on len() looks as an ugly test to check if body is a string.
Why not doing the opposite: first to call fileno() and call AttributeError? Or
even use hasattr(body, fileno)?
--
nosy: +haypo
___
STINNER Victor added the comment:
issue15267.patch: I would feel more confortable if test_send_tempfile() ensures
that the socket contains the file content.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue15267
Roundup Robot added the comment:
New changeset 9565b56a4615 by Victor Stinner in branch '2.7':
Issue #18028: Fix aliasing issue in READ_TIMESTAMP() of ceval.c on x86_64,
https://hg.python.org/cpython/rev/9565b56a4615
New changeset adb445578995 by Victor Stinner in branch '3.4':
Issue #18028:
STINNER Victor added the comment:
3 core developers reviewed Christian's patch, so it also looks good to me :-)
Since Christian looks to be busy, I commited his patch. Thanks Christian for
your fix.
We might enable -fstrict-aliasing later, at least to compile Python core (not
to build
Changes by STINNER Victor victor.stin...@gmail.com:
--
title: -c: Line causing exception not shown for exceptions other than
SyntaxErrors - python -c: Line causing exception not shown for exceptions
other than SyntaxErrors
___
Python tracker
STINNER Victor added the comment:
SyntaxError exceptions have a text attribute which contains the line where the
error occurred. It's really a special case. For other exceptions, Python only
knows that the error occurred in the file called string.
Being able to display the line for any
Antoine Pitrou added the comment:
Also this debug output should be printed on stderr, not stdout.
--
nosy: +pitrou
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue23034
___
STINNER Victor added the comment:
Debugging output switched by Py_REF_DEBUG is now enabled only when -X
showrefcount is specified (issue17323).
Yes, I like the idea of doing that for other debug options.
--
nosy: +haypo
___
Python tracker
New submission from Mark Summerfield:
In message
http://bugs.python.org/issue17914#msg188626
Victor Stenner says
On Windows, GetSystemInfo() is called instead of reading an environment
variable. I suppose that this function is more reliable.
From my reading, and based on feedback from one of
Mark Summerfield added the comment:
Since this is closed I've created a new issue as requested:
http://bugs.python.org/issue23037
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue17914
___
Marc-Andre Lemburg added the comment:
Please always use PROTOCOL_SSLv23 since this is the only forward compatible way
of telling OpenSSL to use the best protocol available.
Any of the other options such as PROTOCOL_TLSv1 will fix the protocol version
to that one protocol version, whereas
Kurt Roeckx added the comment:
So this seems to be a function that just gets the certificate? You need to be
careful with this since a server could perfectly decide to send a different
certificate depending on the client hello it receives. Like if you support
ECDSA it might decide to send
STINNER Victor added the comment:
The code getting the number of processors on Windows is different between the
multiprocessing (Python 3.3) and os (Python 3.5) modules.
multiprocessing (old code):
try:
num = int(os.environ['NUMBER_OF_PROCESSORS'])
except
STINNER Victor added the comment:
So this seems to be a function that just gets the certificate? You need to
be careful with this since a server could perfectly decide to send a
different certificate depending on the client hello it receives. (...) In any
case, you should always use
STINNER Victor added the comment:
Any of the other options such as PROTOCOL_TLSv1 will fix the protocol version
to that one protocol version, whereas PROTOCOL_SSLv23 means to use any
protocol starting with SSLv2. In the context options you can then disable
SSLv2 and SSLv3 to e.g. have the
Kurt Roeckx added the comment:
SSLv3 does not support the TLS extensions so it's going to send a totally
different Client Hello. It will for instance not indicate with elliptic curves
it supports. So yes the behavior for SSLv3 and SSLv23 can be totally
different. But even with both SSLv23
STINNER Victor added the comment:
Do you have an example of server returning a different certificate depending on
the protocol?
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue22935
___
Brett Cannon added the comment:
I don't think we really need to say anything. If people want default results,
simply return None (which is handled for them by importlib.abc.Loader). The
only thing changing here is that the method will now be required instead of
optional.
I'll post the patch
New submission from Collin Anderson:
Can we remove references to #python.web? I assume it was a flourishing channel
at some point.
https://docs.python.org/3/howto/webservers.html#other-notable-frameworks
--
assignee: docs@python
components: Documentation
messages: 232550
nosy:
Marc-Andre Lemburg added the comment:
STINNER Victor added the comment:
Any of the other options such as PROTOCOL_TLSv1 will fix the protocol
version to that one protocol version, whereas PROTOCOL_SSLv23 means to use
any protocol starting with SSLv2. In the context options you can then
Kurt Roeckx added the comment:
Most such sites actually seem to have dropped support for SSLv3.
One site where it depends on the cipher string is bugs.cdburnerxp.se
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue22935
Serhiy Storchaka added the comment:
Here is (conceivably incomplete) list of debugging and tracing output (but not
error reporting) from C code.
Controlled output.
Import and shutdown details -- controlled by the -v flag.
Parser tracing -- controlled by the -d flag.
If Py_REF_DEBUG is defined
Roundup Robot added the comment:
New changeset 1edff7001f58 by Benjamin Peterson in branch '2.7':
remove reference to dead irc channel (closes #23038)
https://hg.python.org/cpython/rev/1edff7001f58
New changeset aba5f771f5ec by Benjamin Peterson in branch '3.4':
remove reference to dead irc
New submission from Philip Lee:
when using open(filename, 'w') on Windows , File names are not allowed to
contain any characters in \/:*?| , however open(filename, 'w') doesn't
throw any exceptions when the file name contains these characters .
I think some warning should be written in the
New submission from Wojtek Ruszczewski:
The documentation for urlencode() [1] isn't very clear on how the safe
parameter is used, it would better not list it together with encoding and error
as only applying to strings.
[1]
R. David Murray added the comment:
The argument to open is a path. Some of those characters have a meaning in a
path.
I ran a couple of quick experiments: ab*c.txt fails with an exception.
:16.txt created a file, which I can do an 'ls' and cat (but not rm) on in
git-bash, but I'm not sure
R. David Murray added the comment:
The current documentation looks very clear to me, and I don't understand your
changed version. Can you give an example of how the existing text is
inaccurate or results in confusion?
--
nosy: +r.david.murray
___
Tim Golden added the comment:
Agree with RDM: we're just passing the path through to the Windows API (on
Windows). We don't generally carry out this kind of pre-emptive check.
--
resolution: - not a bug
stage: - resolved
status: open - closed
___
New submission from Samwyse:
The csv module currently implements four quoting rules for dialects:
QUOTE_MINIMAL, QUOTE_ALL, QUOTE_NONNUMERIC and QUOTE_NONE. These rules treat
values of None the same as an empty string, i.e. by outputting two consecutive
quotes. I propose the addition of two
R. David Murray added the comment:
As an enhancement, this could be added only to 3.5. The proposal sounds
reasonable to me.
--
keywords: +easy
nosy: +r.david.murray
stage: - needs patch
versions: -Python 2.7, Python 3.2, Python 3.3, Python 3.4, Python 3.6
Changes by Berker Peksag berker.pek...@gmail.com:
--
stage: needs patch - resolved
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue9536
___
___
Brett Cannon added the comment:
Here is a patch that makes sure that if exec_module() is defined then so is
create_module(). There really isn't any benefit in the code now, but starting
in Python 3.6 we can make a very clear code path delineation between spec-based
loading and old-fashioned
Changes by Brett Cannon br...@python.org:
--
dependencies: +Don't have importlib.abc.Loader.create_module() be optional
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue23013
___
Samwyse added the comment:
David: That's not a problem for me.
Sorry I can't provide real patches, but I'm not in a position to compile (much
less test) the C implementation of _csv. I've looked at the code online and
below are the changes that I think need to be made. My use cases don't
Brett Cannon added the comment:
Fix is part of issue #23014, so if that goes in then this will be fixed as a
side-effect.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue23013
___
Wojtek Ruszczewski added the comment:
I was looking at the sentence:
When query parameter is a str, the safe, encoding and error parameters are
passed down to quote_plus() for encoding.
The query argument can't be a string itself (gives a TypeError with 3.5a0 and I
think it's only intended to
Brett Cannon added the comment:
Issue #23014 is planning to make create_module() required so that module
creation doesn't have a two-tiered way of specifying a default module (which is
handy in C code).
--
dependencies: +Don't have importlib.abc.Loader.create_module() be optional
Changes by Brett Cannon br...@python.org:
--
assignee: - brett.cannon
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue21581
___
___
Brett Cannon added the comment:
Should this be closed, Eric?
--
status: open - pending
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue21099
___
___
Brett Cannon added the comment:
Do we still need this patch, Eric?
--
status: open - pending
versions: +Python 3.5 -Python 3.4
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue19711
___
Brett Cannon added the comment:
I would still like to get this solved for Python 3.5. Should we hash out a
solution at PyCon?
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue19698
___
Roundup Robot added the comment:
New changeset 5754f069b123 by Steve Dower in branch 'default':
Issue #22919: Windows build updated to support VC 14.0 (Visual Studio 2015),
which will be used for the official 3.5 release.
https://hg.python.org/cpython/rev/5754f069b123
--
nosy:
Steve Dower added the comment:
I'll be closely tracking any issues that arise out of this throughout the next
couple of days, but it should be fairly smooth (especially for people who don't
upgrade VS immediately). There are certainly a few things that are broken, but
I'll make separate
David Watson added the comment:
Here are the alternative patches to allow more than two calls to
confstr(). One patch set just keeps reallocating the buffer
until it's big enough, while the other makes a limited number of
attempts (in this case 20) before raising RuntimeError.
--
Eldar Abusalimov added the comment:
ping?
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue22735
___
___
Python-bugs-list mailing list
New submission from Marc-Andre Lemburg:
With Python 2.7.8, ctypes builds fine on FreeBSD x86, but with Python 2.7.9,
the build fails with:
*** WARNING: renaming _ctypes since importing it failed:
build/lib.freebsd-8.3-RELEASE-p3-i386-2.7/_ctypes.so: Undefined symbol
ffi_call_win32
Since
Marc-Andre Lemburg added the comment:
The cause seems to be these changes of the file (diff between the 2.7.8 and
2.7.9 version):
@@ -368,14 +374,21 @@ void ffi_call(ffi_cif *cif, void (*fn)(v
#ifdef X86_WIN64
case FFI_WIN64:
ffi_call_win64(ffi_prep_args, ecif, cif-bytes,
R. David Murray added the comment:
OK, now I understand. How about this phrasing:
The *safe*, *encoding*, and *error* parameters are passed down to
:func:`quote_plus` (the *encoding* and *error* parameters are only passed when
the query element is a :class:`str`).
--
New submission from Vjacheslav:
from __future__ import print_function
print (1,2)
1 2
in interactive session, but, with this 3 lines in tmp.txt:
python -m doctest tmp.txt
fails (prints tuple)
--
components: Library (Lib)
messages: 232577
nosy: fva
priority: normal
severity: normal
Arfrever Frehtes Taifersar Arahesis added the comment:
It should not be more complex to read a line from a command line argument than
to read a line from a regular file.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue23035
Wojtek Ruszczewski added the comment:
Thanks, that's right and better, as it doesn't replicate the safe explanation.
I've just noticed another small one, the docstring for quote() [2] says:
encoding must not be specified if string is a str -- that should be ... is a
bytes.
[2]
Benjamin Peterson added the comment:
2to3 patch lgtm. Please apply to 3.4, too, though.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue22823
___
Terry J. Reedy added the comment:
The section documents JSONDecoder and then JSONEncoder. Looking at the current
3.4 online docs, I do not see any significant duplication within either entry.
Even if there were duplication between, we might leave it to keep the entries
complete in
Terry J. Reedy added the comment:
Code entered with -c seems to be treated the same as code entered at the
prompt of the interactive interpreter.
1/0
Traceback (most recent call last):
File stdin, line 1, in module
ZeroDivisionError: division by zero
In both cases, the offending code is
Arfrever Frehtes Taifersar Arahesis added the comment:
Argument of -c option can have multiple lines, while only 1 line can be
directly entered in interactive interpreter.
python -c $'line1\nline2\nline3\nline4\n...'
--
___
Python tracker
Changes by Martin Panter vadmium...@gmail.com:
--
nosy: +vadmium
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue18373
___
___
Python-bugs-list
Changes by Martin Panter vadmium...@gmail.com:
--
nosy: +vadmium
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue18679
___
___
Python-bugs-list
Changes by Martin Panter vadmium...@gmail.com:
--
nosy: +vadmium
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue5166
___
___
Python-bugs-list
Terry J. Reedy added the comment:
One can paste multiple lines, comprising multiple statements, into the console
interprer. (Shell only recognizes a single pasted statement.)
I agree, however, that it seems that Python could keep the split version of the
input line for the purpose of
Arfrever Frehtes Taifersar Arahesis added the comment:
Arguments after argument of -c option are included in sys.argv:
$ python -c import sys; print(sys.argv) a b
['-c', 'a', 'b']
--
___
Python tracker rep...@bugs.python.org
New submission from Bart Grzybicki:
Python 2.7.6 (default, Mar 22 2014, 22:59:56)
[GCC 4.8.2] on linux2
Type help, copyright, credits or license for more information.
115.26 + 2.01
117.270001
115.26 + 2.02
117.28
115.27 + 2.01
117.28
--
messages: 232586
nosy: bartgee
Benjamin Peterson added the comment:
Welcome to base 2. https://docs.python.org/2/tutorial/floatingpoint.html
--
nosy: +benjamin.peterson
resolution: - not a bug
status: open - closed
___
Python tracker rep...@bugs.python.org
Demian Brecht added the comment:
Updated patch addressing further reviews
--
Added file: http://bugs.python.org/file37434/issue21793_6.patch
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue21793
Aaron Hill added the comment:
I've created a patch that fixes this, and added an accompanying unit test
(which fails without the change).
--
keywords: +patch
nosy: +Aaron1011
Added file: http://bugs.python.org/file37435/mock-open-allow-binary-data.patch
Martin Panter added the comment:
Update patch with typo fixed, removed note about the “codecs” module (which I
never found useful either), and updated the doc string with similar wording.
Terry, do you think the wording in the patch is good enough, or do you think
some of your proposed
Changes by Steven D'Aprano steve+pyt...@pearwood.info:
--
nosy: +steven.daprano
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue23017
___
___
Demian Brecht added the comment:
Thanks for the patch Aaron. Unfortunately this doesn't quite fix the issue.
There are two problems with the patch:
If a bytes object is passed into mock_open, I'd expect a bytes object in the
output. In your patch, not only is this not the case (the output is
Demian Brecht added the comment:
There are two problems with the patch
That was intended to be removed after I changed the wording :P
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue23004
Steven D'Aprano added the comment:
Even though I agree with closing this issue, there is some support for ignoring
certain missing values when calculating min() and max(). The draft 2008
revision of IEEE-754 includes two functions maxNum and minNum which silently
skip over NANs:
Changes by vegeshna satyanarayana raju satya.nani...@gmail.com:
--
nosy: satyanani40
priority: normal
severity: normal
status: open
title: json data iteration through loop in python
___
Python tracker rep...@bugs.python.org
New submission from vegeshna satyanarayana raju:
I have json data in following format
{message:[frappe,websocerp,erpnext]}
I want each name (frappe, websocerp, erpnext) in three iteration
after that i can use as
frappe.something.get_data()
websocerp.something.get_data()
Steven D'Aprano added the comment:
This is a bug tracker for issues in the Python language and standard library,
not a service for learning how to program using Python.
If you have an actual bug to report, you should give more detail including the
actual code you used, the result you
Changes by Demian Brecht demianbre...@gmail.com:
--
nosy: +demian.brecht
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue23043
___
___
Raymond Hettinger added the comment:
Samwyse, are these suggestions just based on ideas of what could be done or
have you encountered real-world CSV data exchanges that couldn't be handled by
the CSV module?
--
assignee: - skip.montanaro
nosy: +rhettinger, skip.montanaro
Martin Panter added the comment:
I have been bitten by this when attempting to implement my own event loops.
Parts of the “asyncio” code itself expects that the callback is not invoked
directly after call_soon() returns. Here is a simple patch.
--
keywords: +patch
nosy: +vadmium
New submission from Martin Panter:
The documentation mentions BaseEventLoop as an attribute of the “asyncio”
module, but it is not actually there (at least in v3.4.2). I have to import it
specially from “asyncio.base_events”. Is this an oversight in the
documentation, or am I relying on
95 matches
Mail list logo
