[issue46575] One-off errors in hashlib.scrypt error messages
New submission from Ron Kaminsky : There are one-off errors in upper bounds given in the error messages for hashlib.scrypt(...). MAX_INT *is* accepted (and at least for maxmem, works). See https://github.com/python/cpython/blob/8fb36494501aad5b0c1d34311c9743c60bb9926c/Modules/_hashopenssl.c#L1375 and https://github.com/python/cpython/blob/8fb36494501aad5b0c1d34311c9743c60bb9926c/Modules/_hashopenssl.c#L1382 With thanks to everyone involved for all the fine work on Python! -- messages: 412103 nosy: ron_kaminsky priority: normal severity: normal status: open title: One-off errors in hashlib.scrypt error messages type: behavior ___ Python tracker <https://bugs.python.org/issue46575> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue44489] _handle_existing_loggers should respect loggers that were manually disabled
New submission from Ron Serruya :
The method `_handle_existing_loggers` in the logging lib (called when
configuring loggers using dictConfig) iterates over all existing loggers and
sets their .disabled attribute according to the `disable_existing_loggers`
parameter (usually set to false)
However this only lets the user completely disable/enable all existing loggers,
and there is no way to tell the function to keep the value to what it was
This example was how I found about it
1. Imported the pkg ddtrace, which writes some logs that I'm not interested in
2. Disabled the ddtrace logger
`logging.getLogger('ddtrace.internal.writer').disabled = True`
3. Imported the pkg Sanic, which configures its logging using
`logging.configure.dictConfig()`, with `disable_existing_loggers` set to False,
as it doesn't want to disable all of the loggers that were created before it
4. `_handle_existing_loggers` re-enabled the logger that I manually disabled
before
Ps. apologies if this is not the correct place, I don't really see this as a
bug, more like a feature request, however the only place I found for feature
requests were PEPs, which this obviously isnt
--
components: Library (Lib)
messages: 396327
nosy: ronserruya2
priority: normal
severity: normal
status: open
title: _handle_existing_loggers should respect loggers that were manually
disabled
versions: Python 3.8
___
Python tracker
<https://bugs.python.org/issue44489>
___
___
Python-bugs-list mailing list
Unsubscribe:
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue42992] Tkinter bbox coordinates incorrectly drawn
Ron Hoffmann added the comment: Thank you for your response. I have been fighting this issue in a large piece of code for quite some time. So I wrote a small test script as you asked for and the problem will not reproduce. All behaviour of code is as expected. I must therefore assume there is no bug in tkinter and the problem lies in my code or with my development environment. Please consider the issue closed -- resolution: -> not a bug ___ Python tracker <https://bugs.python.org/issue42992> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue42992] Tkinter bbox coordinates incorrectly drawn
New submission from Ron Hoffmann : position coordinates retrieved from any object on a canvas with pos = canvas.bbox(object) are returned correctly but when drawn on the canvas (x0,y0) are correct, but (x1, y1) are not drawn in the proper positions. x1 has been divided by 2 somewhere and y1 as been multiplied by 2 somewhere. in order for the bounding box to be drawn correctly x1 and y1 need to be recalculated as follows x1 = pos[0] + ( ( pos[2] - pos[0] ) * 2 ) y1 = pos[1] + ( ( pos[3] - pos[1] ) / 2 ) -- components: Tkinter messages: 385446 nosy: rhoffmann priority: normal severity: normal status: open title: Tkinter bbox coordinates incorrectly drawn type: behavior versions: Python 3.8 ___ Python tracker <https://bugs.python.org/issue42992> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue39257] contextvars.Context.run hangs forever in ProccessPoolExecutor
Ron Serruya added the comment:
Sending Context.run to another process via ProccessPoolExecutor hangs forever:
```
from contextvars import ContextVar, copy_context
from concurrent.futures import ProcessPoolExecutor
from multiprocessing import Process
var: ContextVar[int] = ContextVar('var',default=None)
if __name__ == '__main__':
# * This hangs forever *
with ProcessPoolExecutor(max_workers=1) as pp:
ctx = copy_context()
pp.submit(ctx.run, list)
# ** This throws 'cannot pickle Context' *
ctx = copy_context()
p = Process(target=ctx.run, args=(list,))
p.start()
p.join()
```
python version is 3.8.0
running on Mac OSX 10.15.1
--
___
Python tracker
<https://bugs.python.org/issue39257>
___
___
Python-bugs-list mailing list
Unsubscribe:
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue39257] contextvars.Context.run hangs forever in ProccessPoolExecutor
New submission from Ron Serruya :
Sending Context.run to another process via ProccessPoolExecutor hangs forever:
```
from contextvars import ContextVar, copy_context
from concurrent.futures import ProcessPoolExecutor
from multiprocessing import Process
var: ContextVar[int] = ContextVar('var',default=None)
if __name__ == '__main__':
# * This hangs forever *
with ProcessPoolExecutor(max_workers=1) as pp:
ctx = copy_context()
pp.submit(ctx.run, list)
# ** This throws 'cannot pickle Context' # * This hangs forever
*
ctx = copy_context()
p = Process(target=ctx.run, args=(list,))
p.start()
p.join()
```
python version is 3.8.0
running on Mac OSX 10.15.1
--
messages: 359575
nosy: ronserruya
priority: normal
severity: normal
status: open
title: contextvars.Context.run hangs forever in ProccessPoolExecutor
type: behavior
versions: Python 3.8
___
Python tracker
<https://bugs.python.org/issue39257>
___
___
Python-bugs-list mailing list
Unsubscribe:
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue38529] Python 3.8 improperly warns about closing properly closed streams
Ron Frederick added the comment: Sorry, I should have said that the change below was in the file asyncio/streams.py. -- ___ Python tracker <https://bugs.python.org/issue38529> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue38529] Python 3.8 improperly warns about closing properly closed streams
Ron Frederick added the comment:
I think the following change might address this problem:
***
*** 233,239
def _on_reader_gc(self, wr):
transport = self._transport
! if transport is not None:
# connection_made was called
context = {
'message': ('An open stream object is being garbage '
--- 233,239
def _on_reader_gc(self, wr):
transport = self._transport
! if transport is not None and not transport.is_closing():
# connection_made was called
context = {
'message': ('An open stream object is being garbage '
--
___
Python tracker
<https://bugs.python.org/issue38529>
___
___
Python-bugs-list mailing list
Unsubscribe:
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue38529] Python 3.8 improperly warns about closing properly closed streams
New submission from Ron Frederick :
In testing AsyncSSH against Python 3.8, I noticed a large number of the
following errors, even though I was properly closing streams before the objects
holding them were garbage-collected.
An open stream object is being garbage collected; call "stream.close()"
explicitly.
After some investigation, the problem appears to be that closing a stream is
not good enough to prevent the error. The check in asyncio doesn't properly
handle the case where the stream is closing, but has not fully closed. Here's a
simple test program that demonstrates this:
import asyncio
async def tcp_client():
reader, writer = await asyncio.open_connection('127.0.0.1', 22)
writer.close()
asyncio.run(tcp_client())
It's possible to avoid this message by awaiting on writer.wait_closed(), but
wait_closed() doesn't exist until Python 3.7, making it very difficult to write
portable code and still avoid this message.
--
components: asyncio
messages: 354953
nosy: Ron Frederick, asvetlov, yselivanov
priority: normal
severity: normal
status: open
title: Python 3.8 improperly warns about closing properly closed streams
type: behavior
versions: Python 3.8
___
Python tracker
<https://bugs.python.org/issue38529>
___
___
Python-bugs-list mailing list
Unsubscribe:
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue16438] Numeric operator predecence confusing
ron added the comment: Any progress on this? -- nosy: +ronron ___ Python tracker <https://bugs.python.org/issue16438> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue34529] add the option for json.dumps to return newline delimited json
ron added the comment: Well... when handling GBs of data - it's preferred to generate the file directly in the required format rather than doing conversions. The new line is a format... protocols don't matter here... I still think the library should allow the user to create this format directly. Lets get out of the scope of Google or others... The new line is a great format it allows you to take a "row" in the middle of the file and see it. You don't need to read 1gb file into parser in order to see it you can use copy 1 row... We are adopting this format for all our jsons, so it would be nice to get the service directly from the library. -- ___ Python tracker <https://bugs.python.org/issue34529> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue34529] add the option for json.dumps to return newline delimited json
ron added the comment: I'm a bit confused here. On one hand you say it's two lines of code. On other hand you suggest that each service provider will implement it's own functions. What's the harm from adding - small , unbreakable functionality? Your points for small code could have also been raised against implementing reverse() - yet Python still implemented it - saved the 2 line code from the developer. At the end.. small change or not.. This is a new format. Conversion between formats are required from any programming language.. -- ___ Python tracker <https://bugs.python.org/issue34529> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue34529] add the option for json.dumps to return newline delimited json
ron added the comment: Raymond Hettinger answer is incorrect. The main difference between Json and new line delimited json is that new line contains valid json in each line. Meaning you can do to line #47 and what you will have in this line is a valid json. Unlike the regular json where if one bracket is wrong the while file is unreadable. You can not just add /n after one "object". You need also to change the brackets. Keep in mind that not all Jsons are simple.. some contains huge amount of nested objects inside of them. You must identify where Json start and where it ends without being confused by nesting jsons. There are many programming solutions to this issue. For example: https://stackoverflow.com/questions/51595072/convert-json-to-newline-json-standard-using-python/ My point is that this is a new format which is going to be widely accepted since Google adopted it for BigQuery. flipping strings can also be easily implemented yet Python still build a function to do that for the user. I think it's wise to allow support for this with in the Json library.. saving the trouble for programmer from thinking how to implement it. -- ___ Python tracker <https://bugs.python.org/issue34529> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue34529] add the option for json.dumps to return newline delimited json
New submission from ron : Many service providers such as Google BigQuery do not accept Json. They accept newline delimited Json. https://cloud.google.com/bigquery/docs/loading-data-cloud-storage-json#limitations please allow to receive this format directly from the dump. -- messages: 324244 nosy: ronron priority: normal severity: normal status: open title: add the option for json.dumps to return newline delimited json type: enhancement versions: Python 3.7 ___ Python tracker <https://bugs.python.org/issue34529> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue33213] crypt function not hashing properly on Mac (uses a specific salt)
Change by Ron Reiter : -- type: -> security ___ Python tracker <https://bugs.python.org/issue33213> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue33213] crypt function not hashing properly on Mac (uses a specific salt)
Change by Ron Reiter : -- title: crypt function not hashing properly -> crypt function not hashing properly on Mac (uses a specific salt) ___ Python tracker <https://bugs.python.org/issue33213> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue33213] crypt function not hashing properly
Ron Reiter added the comment:
Also:
>>> crypt.crypt("test", "$5")
'$5yVOkTkyRzn.'
>>> crypt.crypt("test", "$6")
'$6asQOJRqB1i2'
>>> crypt.crypt("test", "$7")
'$7tSOkvDyiL6U'
So the salt is "$6"
--
___
Python tracker
<https://bugs.python.org/issue33213>
___
___
Python-bugs-list mailing list
Unsubscribe:
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue33213] crypt function not hashing properly
Ron Reiter added the comment:
Python 3.6.4 (default, Mar 22 2018, 23:35:12)
[GCC 4.2.1 Compatible Apple LLVM 9.0.0 (clang-900.0.39.2)] on darwin
Type "help", "copyright", "credits" or "license" for more information.
>>> import crypt
>>> crypt.crypt("test", crypt.METHOD_SHA512)
'$6asQOJRqB1i2'
>>> crypt.crypt("test", crypt.METHOD_SHA512)
'$6asQOJRqB1i2'
--
___
Python tracker
<https://bugs.python.org/issue33213>
___
___
Python-bugs-list mailing list
Unsubscribe:
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue33213] crypt function not hashing properly
Ron Reiter added the comment: Apparently it's a Mac issue. My crypt.methods only contains [] which is probably why this fails. It's a silent failure of some sort that is causing this. -- ___ Python tracker <https://bugs.python.org/issue33213> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue33213] crypt function not hashing properly
Ron Reiter added the comment: You guessed it, the salt is "$6" -- ___ Python tracker <https://bugs.python.org/issue33213> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue33213] crypt function not hashing properly
Ron Reiter added the comment:
import crypt
Expected result:
>>> crypt.crypt("test") == crypt.crypt("test")
False
>>> crypt.crypt("test", crypt.mksalt()) == crypt.crypt("test", crypt.mksalt())
False
Unexpected results:
>>> crypt.crypt("test", crypt.METHOD_SHA512) == crypt.crypt("test",
>>> crypt.METHOD_SHA512)
True
>>> crypt.crypt("test", crypt.mksalt(crypt.METHOD_SHA512)) ==
>>> crypt.crypt("test", crypt.mksalt(crypt.METHOD_SHA512))
True
--
___
Python tracker
<https://bugs.python.org/issue33213>
___
___
Python-bugs-list mailing list
Unsubscribe:
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue33213] crypt function not hashing properly
New submission from Ron Reiter :
import crypt
Expected result:
>>> crypt.crypt("test") == crypt.crypt("test")
False
>>> crypt.crypt("test", crypt.mksalt()) == crypt.crypt("test", crypt.mksalt())
False
Unexpected results:
>>> crypt.crypt("test", crypt.METHOD_SHA512) == crypt.crypt("test",
>>> crypt.METHOD_SHA512)
True
>>> crypt.crypt("test", crypt.mksalt(crypt.METHOD_SHA512)) ==
>>> crypt.crypt("test", crypt.mksalt(crypt.METHOD_SHA512))
False
--
components: Extension Modules
messages: 314866
nosy: Ron Reiter
priority: normal
severity: normal
status: open
title: crypt function not hashing properly
versions: Python 3.6
___
Python tracker
<https://bugs.python.org/issue33213>
___
___
Python-bugs-list mailing list
Unsubscribe:
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue25749] asyncio.Server class documented but not exported
Ron Frederick added the comment: > I think you're doing it the right way. It's a rather niche requirement, so I > don't think we should make create_server to somehow support this use case. Agreed. > asyncssh looks absolutely amazing, btw. Thanks so much! -- ___ Python tracker <https://bugs.python.org/issue25749> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue25749] asyncio.Server class documented but not exported
Ron Frederick added the comment: That'd be great if you could add AbstractServer to the 3.7 docs - thanks! Regarding the other issue, I'm already set up to use multiple asyncio.Server objects to deal with the shared port issue and it's working fine. It did mean duplicating a handful of lines of code from asyncio to iterate over the getaddrinfo() results (creating one asyncio.Server per sockaddr instead of letting asyncio create a single asyncio.Server with multiple listening sockets) and there are some other minor details like cleaning up if the kernel-selected dynamic port chosen for the first interface is not actually free on all other interfaces, but I'm not actually looking for any changes in how that's working right now. Here's the code I'm referring to if you're curious: https://github.com/ronf/asyncssh/blob/master/asyncssh/listener.py#L192 -- ___ Python tracker <https://bugs.python.org/issue25749> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue25749] asyncio.Server class documented but not exported
Ron Frederick added the comment: Thanks. Unfortunately, in the case of the way SSH listeners with dynamic ports, the protocol only allows a single port number to be returned. So, when binding on multiple interfaces there's a requirement that the SAME port be chosen for all of the socket bindings, which can't easily be done today with a single asyncio.Server object. That's a bit off-topic for this issue, though. Regarding exposing the sockets, it would never really make sense to directly call send() on a listening socket, and I can see why it also wouldn't make sense to allow calling accept(). I'm really not sure there's ANY call other than getsockaddr() that really makes sense here, though, so perhaps it would be better to evolve the API in AbstractServer into returning a list of sockaddr tuples rather than sockets. -- ___ Python tracker <https://bugs.python.org/issue25749> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue25749] asyncio.Server class documented but not exported
Ron Frederick added the comment: In my original report, I suggested _either_ exporting asyncio.Server since that's what was documented elsewhere _OR_ adding AbstractServer to the documentation and changing existing references to asyncio.Server to point at asyncio.AbstractServer instead, as that symbol is already exported but is not currently documented. There appear to be good reasons for hiding the implementation details of Server, and I'm good with that. I just think the docs and the exports need to agree on one or the other. I originally had references to AbstractServer in my project docs, but changed them to Server after seeing that only Server was currently in the public Python documentation. As for references to the "sockets" member of Server, I'm not currently relying on that in my code. I have code that can handle getaddrinfo() returning more than one address to listen on, but I create separate Server instances for each individual address right now, as this gives me better control when a caller asks to listen on a dynamic port on multiple interfaces at once. -- ___ Python tracker <https://bugs.python.org/issue25749> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue31855] mock_open is not compatible with read(n) (and pickle.load)
Ron Rothman added the comment: Confirmed that the behavior exists in Python 3.6 as well. -- versions: +Python 3.6 ___ Python tracker <https://bugs.python.org/issue31855> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue31855] mock_open is not compatible with read(n) (and pickle.load)
New submission from Ron Rothman :
mock.mock_open works as expected when reading the entire file (read()) or when
reading a single line (readline()), but it seems to not support reading a
number of bytes (read(n)).
These work as expected:
from mock import mock_open, patch
# works: consume entire "file"
with patch('__main__.open', mock_open(read_data='bibble')) as m:
with open('foo') as h:
result = h.read()
assert result == 'bibble' # ok
# works: consume one line
with patch('__main__.open', mock_open(read_data='bibble\nbobble')) as m:
with open('foo') as h:
result = h.readline()
assert result == 'bibble\n' # ok
But trying to read only a few bytes fails--mock_open returns the entire
read_data instead:
# consume first 3 bytes of the "file"
with patch('__main__.open', mock_open(read_data='bibble')) as m:
with open('foo') as h:
result = h.read(3)
assert result == 'bib', 'result of read: {}'.format(result) # fails
Output:
Traceback (most recent call last):
File "/tmp/t.py", line 25, in
assert result == 'bib', 'result of read: {}'.format(result)
AssertionError: result of read: bibble
The unfortunate effect of this is that mock_open cannot be used with
pickle.load.
with open('/path/to/file.pkl', 'rb') as f:
x = pickle.load(f) # this requires f.read(1) to work
--
components: Library (Lib)
messages: 304841
nosy: ron.rothman
priority: normal
severity: normal
status: open
title: mock_open is not compatible with read(n) (and pickle.load)
type: behavior
versions: Python 2.7
___
Python tracker
<https://bugs.python.org/issue31855>
___
___
Python-bugs-list mailing list
Unsubscribe:
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue28305] Make error for Python3.6 on Cygwin
Ron Barak added the comment: Can I apply http://bugs.python.org/file44208/3.5-issue21085-struct_siginfo-2.patch to 3.6 as is? -- ___ Python tracker <http://bugs.python.org/issue28305> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue28305] Make error for Python3.6 on Cygwin
Ron Barak added the comment: Re: Cygwin is an unsupported platform. Currently, from the contents of Python-3.6.0b1, one may be led to believe that Cygwin _is_ supported, e.g. - see the references to Cygwin in the README file: $ grep -i cygwin README On Unix, Linux, BSD, OSX, and Cygwin: find out more. On OSX and Cygwin, the executable is called python.exe; -- ___ Python tracker <http://bugs.python.org/issue28305> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue28305] Make error for Python3.6 on Cygwin
New submission from Ron Barak:
Successfully did:
$ gunzip Python-3.6.0b1.tgz
$ tar xvf Python-3.6.0b1.tar
$ pushd Python-3.6.0b1
$ ./configure --disable-ipv6 --with-optimizations
However, when trying to do:
$ make profile-opt
I get:
...
gcc -Wno-unused-result -Wsign-compare -DNDEBUG -g -fwrapv -O3 -Wall
-Wstrict-prototypes-std=c99 -Wextra -Wno-unused-result
-Wno-unused-parameter -Wno-missing-field-initializers -fprofile-generate -I.
-IInclude -I./Include-DPy_BUILD_CORE -c ./Modules/signalmodule.c -o
Modules/signalmodule.o
In file included from Include/Python.h:85:0,
from ./Modules/signalmodule.c:6:
./Modules/signalmodule.c: In function 'fill_siginfo':
./Modules/signalmodule.c:960:60: error: 'siginfo_t {aka struct }'
has no member named 'si_band'
PyStructSequence_SET_ITEM(result, 6, PyLong_FromLong(si->si_band));
^
Include/tupleobject.h:62:75: note: in definition of macro 'PyTuple_SET_ITEM'
#define PyTuple_SET_ITEM(op, i, v) (((PyTupleObject *)(op))->ob_item[i] = v)
^
./Modules/signalmodule.c:960:5: note: in expansion of macro
'PyStructSequence_SET_ITEM'
PyStructSequence_SET_ITEM(result, 6, PyLong_FromLong(si->si_band));
^
make[2]: *** [Makefile:1731: Modules/signalmodule.o] Error 1
make[2]: Leaving directory '/home/Administrator/python/3.6/Python-3.6.0b1'
make[1]: *** [Makefile:511: build_all_generate_profile] Error 2
make[1]: Leaving directory '/home/Administrator/python/3.6/Python-3.6.0b1'
make: *** [Makefile:496: profile-opt] Error 2
--
components: Build
files: python3.6Make.err.txt
messages: 277650
nosy: ronbarak
priority: normal
severity: normal
status: open
title: Make error for Python3.6 on Cygwin
type: compile error
versions: Python 3.6
Added file: http://bugs.python.org/file44872/python3.6Make.err.txt
___
Python tracker
<http://bugs.python.org/issue28305>
___
___
Python-bugs-list mailing list
Unsubscribe:
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue27767] Receive "A required privilege is not held by the Client" error message when Installing python on Windows 10 64 bit
Ron Carr added the comment: Hi Nosy and Brett, I worked it out, even though I turned off the virus checker it was still in memory. I had to right click on the install file, then select allow install, it then completed successfully. Regards, Ron On Tue, Aug 16, 2016 at 2:44 AM, Brett Cannon wrote: > > Brett Cannon added the comment: > > 1. Is this pre- or post-Anniversary update? > > 2. Is the PC administered by anyone other than yourself (e.g. is it a work > machine)? > > 3. Are you trying to do a system-wide install or a personal install? > > 4. For at least Python 3.5 the installer does work as I have done it > myself multiple times. > > -- > nosy: +brett.cannon > > ___ > Python tracker > <http://bugs.python.org/issue27767> > ___ > -- ___ Python tracker <http://bugs.python.org/issue27767> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue27767] Receive "A required privilege is not held by the Client" error message when Installing python on Windows 10 64 bit
New submission from Ron Carr: Hi, I am unable to install Python 3.6.0, 3.5.2 and 2.7.12, on my Windows 10 64 bit system, receive error message "A required privilege is not held by the client". I have turned UAC, and changed registry setting to zero. Also have ensured my Administrator has full access rights, but still get the same error. I have also turned off my virus checker. Any help would be greatly appeciated. Regards, Ballterrier -- components: Installation messages: 272752 nosy: ballterrier priority: normal severity: normal status: open title: Receive "A required privilege is not held by the Client" error message when Installing python on Windows 10 64 bit type: security versions: Python 3.6 ___ Python tracker <http://bugs.python.org/issue27767> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue26887] Erratum in https://docs.python.org/2.6/library/multiprocessing.html
New submission from Ron Barak: Erratum in https://docs.python.org/2.6/library/multiprocessing.html: The chunksize argument is the same as the one used by the map() method. For very long iterables using a large value for chunksize can make >>>make<<< the job complete much faster than using the default value of 1. -- messages: 264520 nosy: ronbarak priority: normal severity: normal status: open title: Erratum in https://docs.python.org/2.6/library/multiprocessing.html versions: Python 2.7 ___ Python tracker <http://bugs.python.org/issue26887> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue25749] asyncio.Server class documented but not exported
New submission from Ron Frederick: The asyncio documentation defines the class 'asyncio.Server' in section 18.5.1.15. However, this class is not exported by asyncio. It is defined in base_events.py but not in the __all__ list. The only class exported at the asyncio top level is asyncio.AbstractServer, defined in events.py. I think the documentation should match the exports. Either Server should be exported out of base_events.py, or the documentation should only refer to asyncio.AbstractServer. -- components: asyncio messages: 255476 nosy: Ron Frederick, gvanrossum, haypo, yselivanov priority: normal severity: normal status: open title: asyncio.Server class documented but not exported type: behavior versions: Python 3.4, Python 3.5, Python 3.6 ___ Python tracker <http://bugs.python.org/issue25749> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue25033] Python 2.7.10 make - fails on some Standard Library Modules
New submission from Ron Barak: UnixWare7 only supports Python 1.6 I added Python 2.7.10 from sources. Python works, but its make did not finish cleanly: several Standard Library modules failed to build (see attached: it has to be a screenshot since VirtualBox does not support cut-and-paste on UnixWare). Can you suggest what should be done so that `multiprocessing`, `ssl`, and `select` will compile/build successfully? -- components: Build files: Python_make_failure.PNG messages: 250244 nosy: ronbarak priority: normal severity: normal status: open title: Python 2.7.10 make - fails on some Standard Library Modules versions: Python 2.7 Added file: http://bugs.python.org/file40411/Python_make_failure.PNG ___ Python tracker <http://bugs.python.org/issue25033> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue24616] 'make install' fails installation of man pages for Python 2.7.10 on Unixware 7.1.4
Ron Barak added the comment: @Serhiy, Not only would posting text be clearer, but much easier. Alas, the Unixware I use is on a VirtualBox, and VitualBox does not support Guest Extension on Unixware - which means that neither cut-and-paste nor sharing host filesystem are possible. So, unless I get any ideas of how to get text off my Unixware on VirtualBox, screenshots are all I have. -- ___ Python tracker <http://bugs.python.org/issue24616> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue24615] 'make install' fails installation of man pages for Python 2.7.10 on Unixware 7.1.4
Changes by Ron Barak : -- resolution: -> duplicate status: open -> closed ___ Python tracker <http://bugs.python.org/issue24615> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue24616] 'make install' fails installation of man pages for Python 2.7.10 on Unixware 7.1.4
New submission from Ron Barak: I wanted to add Python 2.7 to Unix. I downloaded the sources to the VirtualBox on which the Unix is installed. ./configure is successful. make is successful after I manually applied the changes in http://bugs.python.org/issue24611 However, 'make install' fails the installation of man pages (see attached). (Note that Python 2.7.10 is installed and is accessible as /usr/local/bin/python2.7) Environment: OS Unixware 7.1.4 Python 2.7.10 CC Optimizing C Compilation System (CCS) 4.2 05/11/04 (ux714.bl3af) -- components: Installation files: make_install_fail.PNG messages: 246648 nosy: ronbarak priority: normal severity: normal status: open title: 'make install' fails installation of man pages for Python 2.7.10 on Unixware 7.1.4 versions: Python 2.7 Added file: http://bugs.python.org/file39912/make_install_fail.PNG ___ Python tracker <http://bugs.python.org/issue24616> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue24615] 'make install' fails installation of man pages for Python 2.7.10 on Unixware 7.1.4
Ron Barak added the comment: EDIT 1 (cut and paste had some extraneous data): I wanted to add Python 2.7 to Unix. I downloaded the sources to the VirtualBox on which the Unix is installed. ./configure is successful. make is successful after I manually applied the changes in http://bugs.python.org/issue24611 However, 'make install' fails the installation of man pages (see attached). (Note that Python 2.7.10 is installed and is accessible as /usr/local/bin/python2.7) Environment: OS Unixware 7.1.4 Python 2.7.10 CC Optimizing C Compilation System (CCS) 4.2 05/11/04 (ux714.bl3af) -- Added file: http://bugs.python.org/file39911/make_install_fail.PNG ___ Python tracker <http://bugs.python.org/issue24615> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue24615] 'make install' fails installation of man pages for Python 2.7.10 on Unixware 7.1.4
Changes by Ron Barak : -- components: +Installation -Build ___ Python tracker <http://bugs.python.org/issue24615> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue24615] 'make install' fails installation of man pages for Python 2.7.10 on Unixware 7.1.4
New submission from Ron Barak: I wanted to add Python 2.7 to Unix. I downloaded the sources to the VirtualBox on which the Unix is installed. ./configure is successful. make is successful after I manually applied the changes in http://bugs.python.org/issue24611 However, 'make install' fails the installation of man pages (see attached). (Note that Python 2.7.10 is installed and is accessible as /usr/local/bin/python2.7) ./configure --prefix=/usr \ --enable-shared \ --with-system-expat \ without problems. However, when I try to run make, it fails on: cc –Kpthread –Wl,-Bexport –o python Modules/python.o libpython2.7.a -lsocket –lnsl –lpthread –ldl –lm Undefined first referenced symbol in file _PyInt_FromDev libpython2.7.a(posixmodule.o) UX:ld: ERROR: Symbol referencing errors. No output written to python *** Error code 1 (bu21) UX:make: ERROR: fatal error. Environment: OS Unixware 7.1.4 Python 2.7.10 CC Optimizing C Compilation System (CCS) 4.2 05/11/04 (ux714.bl3af) -- components: Build files: make_install_fail.PNG messages: 246646 nosy: ronbarak priority: normal severity: normal status: open title: 'make install' fails installation of man pages for Python 2.7.10 on Unixware 7.1.4 versions: Python 2.7 Added file: http://bugs.python.org/file39910/make_install_fail.PNG ___ Python tracker <http://bugs.python.org/issue24615> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue24611] Compiling Python 2.7.10 Error on Unixware 7.1.4
Ron Barak added the comment: When I try to apply the patch manually, namely - editing Modules/posixmodule.c, and moving the #endif a few lines up, the make finishes correctly. So, the patch does work: I'm probably not applying it correctly. Could you point to my error in applying the patch? -- ___ Python tracker <http://bugs.python.org/issue24611> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue24611] Compiling Python 2.7.10 Error on Unixware 7.1.4
Ron Barak added the comment: I tried to apply the patch. Alas, I get an "Hmm... I can't seem to find a patch in there anywhere." error. See attached screenshot. Did I apply the patch incorrectly? -- Added file: http://bugs.python.org/file39909/issue24611.PNG ___ Python tracker <http://bugs.python.org/issue24611> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue24611] Compiling Python 2.7.10 Error on Unixware 7.1.4
New submission from Ron Barak: I wanted to add Python 2.7 to Unix. I downloaded the sources to the VirtualBox on which the Unix is installed and run ./configure --prefix=/usr \ --enable-shared \ --with-system-expat \ without problems. However, when I try to run make, it fails on: cc –Kpthread –Wl,-Bexport –o python Modules/python.o libpython2.7.a -lsocket –lnsl –lpthread –ldl –lm Undefined first referenced symbol in file _PyInt_FromDev libpython2.7.a(posixmodule.o) UX:ld: ERROR: Symbol referencing errors. No output written to python *** Error code 1 (bu21) UX:make: ERROR: fatal error. Environment: OS Unixware 7.1.4 Python 2.7.10 CC Optimizing C Compilation System (CCS) 4.2 05/11/04 (ux714.bl3af) -- components: Build messages: 246604 nosy: ronbarak priority: normal severity: normal status: open title: Compiling Python 2.7.10 Error on Unixware 7.1.4 type: compile error versions: Python 2.7 ___ Python tracker <http://bugs.python.org/issue24611> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue18387] Add 'symbols' link to pydoc's html menu bar.
Ron Adam added the comment: Adding you Nick, I don't have commit rights. This probably doesn't need much.. maybe a one line comment in news is all. (And maybe not even that.) -- nosy: +ncoghlan ___ Python tracker <http://bugs.python.org/issue18387> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue18740] str is number methods don't recognize '.'
Ron Adam added the comment: I get the same resluts if I make the string by str(123.0). I was thinking it should test True for the isdecimal case for that. It seems I missunderstood their purpose/use. This seems like it would be a very common misunderstanding. It appears, (Because it isn't stated in the doc strings), that they are for testing what specific sub-group of unicode data, the individual character(s) are in. I think the methods doc strings should say this and be worded so they are more character specific. """ Tests each character, and returns true if all of them are in the unicode ___ sub-group. """ As for testing weather or not a string as a whole represents a number value, it seems try/except is still the best way. :-/ -- ___ Python tracker <http://bugs.python.org/issue18740> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue18740] str is number methods don't recognize '.'
New submission from Ron Adam: Shouldn't at least isdecimal return True? >>> '123.0'.isdecimal() False >>> '123.0'.isalnum() False >>> '123.0'.isnumeric() False >>> '123.0'.isdigit() False -- components: Interpreter Core messages: 195186 nosy: ron_adam priority: normal severity: normal status: open title: str is number methods don't recognize '.' type: behavior versions: Python 3.4 ___ Python tracker <http://bugs.python.org/issue18740> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue18387] Add 'symbols' link to pydoc's html menu bar.
Ron Adam added the comment: I agree the specific content for each symbol are separate issues. Those are probably best addressed individually or a few at a time when they are closely related. -- ___ Python tracker <http://bugs.python.org/issue18387> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue18387] Add 'symbols' link to pydoc's html menu bar.
Ron Adam added the comment: Patch update: "<>" removed from pydoc symbols table. -- Added file: http://bugs.python.org/file30931/pdoc_symbols.diff ___ Python tracker <http://bugs.python.org/issue18387> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue18387] Add 'symbols' link to pydoc's html menu bar.
Changes by Ron Adam : Removed file: http://bugs.python.org/file30922/pdoc_symbols.diff ___ Python tracker <http://bugs.python.org/issue18387> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue18387] Add 'symbols' link to pydoc's html menu bar.
Changes by Ron Adam : Removed file: http://bugs.python.org/file30843/pdoc_symbols.diff ___ Python tracker <http://bugs.python.org/issue18387> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue18387] Add 'symbols' link to pydoc's html menu bar.
Ron Adam added the comment: Updated the patch. -- ___ Python tracker <http://bugs.python.org/issue18387> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue18387] Add 'symbols' link to pydoc's html menu bar.
Ron Adam added the comment: Thanks for catching that. I had used unquote_plus instead of unquote. That is needed for multi-field form data, pydoc doens't need it. Removed the back tick from the pydoc symbols list. The topic link for that symbol was already removed. I also attempted to make the escape() usage a bit better by using the escape function from the html package in more places. It does just a bit better job of escaping. I wasn't aware help() would take a "symbols" argument when I added the "keywords" and "topics" pages to the html server. I've been meaning to get this in for a while. -- Added file: http://bugs.python.org/file30922/pdoc_symbols.diff ___ Python tracker <http://bugs.python.org/issue18387> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue18436] Add mapping of symbol to function to operator module
Ron Adam added the comment:
Regarding opertor.get_op:
Look at help("symbols") output for consistancy. There may be items in one that
can be included in the other.
The operator.get_op addition would be useful for improving help on the symbol
information for help/pydoc. Currently it seems overly general for symbols.
Also patch, http://bugs.python.org/issue18387, which adds help("symbols")
output to pydocs web browser interface. It could use a review.
--
nosy: +ron_adam
___
Python tracker
<http://bugs.python.org/issue18436>
___
___
Python-bugs-list mailing list
Unsubscribe:
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue18387] Add 'symbols' link to pydoc's html menu bar.
Ron Adam added the comment: New slightly improved patch. Combined the topic index's, topics, keywords, and the new symbols case, into a single html_topicsindex(title) function. -- Added file: http://bugs.python.org/file30843/pdoc_symbols.diff ___ Python tracker <http://bugs.python.org/issue18387> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue18387] Add 'symbols' link to pydoc's html menu bar.
Changes by Ron Adam : Removed file: http://bugs.python.org/file30831/pdoc_symbols.diff ___ Python tracker <http://bugs.python.org/issue18387> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue18387] Add 'symbols' link to html menu bar.
New submission from Ron Adam:
This patch adds a 'symbols' link after the 'topics' and 'keywords' links in the
html browser menu bar.
help('symbols') worked, but there was no way to get to it in the html browser.
This also adds unquote_plus() to the url handler to unquote the html input form
fields. This is needed to allow entering the symbols.
--
components: Library (Lib)
files: pdoc_symbols.diff
keywords: patch
messages: 192471
nosy: ron_adam
priority: normal
severity: normal
status: open
title: Add 'symbols' link to html menu bar.
versions: Python 3.4
Added file: http://bugs.python.org/file30831/pdoc_symbols.diff
___
Python tracker
<http://bugs.python.org/issue18387>
___
___
Python-bugs-list mailing list
Unsubscribe:
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue18387] Add 'symbols' link to pydoc's html menu bar.
Changes by Ron Adam : -- title: Add 'symbols' link to html menu bar. -> Add 'symbols' link to pydoc's html menu bar. ___ Python tracker <http://bugs.python.org/issue18387> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10716] Modernize pydoc to use better HTML and separate CSS
Ron Adam added the comment: I'm going to go over this issue again with fresh eyes after having been away for some time. Recent experience with another project has helped answer some of the questions I had earlier. Particulary, how not to over specifying class names and id's. This should lead to cleaner html pages that will be easier to style with css. It should also lead to a smaller patch. ;-) It seems that most of the input so far has more to do with spelling rather than function. Is there a prefered style guide for css that we should use? -- ___ Python tracker <http://bugs.python.org/issue10716> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue9674] make install DESTDIR=/home/blah fails when the prefix specified is /
Ron Hubbard added the comment: George.Peristerakis' patch works please apply -- ___ Python tracker <http://bugs.python.org/issue9674> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue13028] python wastes linux users time by checking for dylib on each dynamic library load
Ron Hubbard added the comment: i'll try to reproduce this later. looking at the below strace output, python's behaviour seems pretty stupid tho, for example if /lib is the only existing path out of /lib, /lib64, /usr/lib/, /usr/local/lib, etc etc, it should check for all these directories once, and then not try to open .so in unexisting directories over and over again, inflicting multiple syscalls for each dso. -- nosy: +arschficker ___ Python tracker <http://bugs.python.org/issue13028> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue9674] make install DESTDIR=/home/blah fails when the prefix specified is /
Ron Hubbard added the comment: this is a very ugly bug and should be fixed ASAP it's not only breaking python itself, but any package that uses this python installer, for example http://seclists.org/nmap-dev/2012/q3/1025 what is preventing a merge of the existing patch ? -- ___ Python tracker <http://bugs.python.org/issue9674> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue13028] python wastes linux users time by checking for dylib on each dynamic library load
Changes by Ron Hubbard : -- type: -> resource usage ___ Python tracker <http://bugs.python.org/issue13028> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue16065] Python/distutils setup.py: passing --prefix / makes --root ignored
Ron Hubbard added the comment: python 2.7.2 installation: CFLAGS="-D_GNU_SOURCE -D_BSD_SOURCE" ./configure -C --prefix="/" || exit 1 make -j9 || exit 1 make DESTDIR="//opt/python" install || exit 1 what python generates out of --install-scripts=//bin \ --install-platlib=//lib/python2.7/lib-dynload \ is both wrong (i.e. the platlib stuff also ignores DESTDIR passed to make) -- ___ Python tracker <http://bugs.python.org/issue16065> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue16065] Python/distutils setup.py: passing --prefix / makes --root ignored
Changes by Ron Hubbard : -- type: -> security ___ Python tracker <http://bugs.python.org/issue16065> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue16065] Python/distutils setup.py: passing --prefix / makes --root ignored
New submission from Ron Hubbard: setup.py loses the DESTDIR aka --root iff "/" is passed as prefix http://seclists.org/nmap-dev/2012/q3/1025 I can reproduce this now, but only with a prefix of "/". For example, this works: $ python setup.py install --prefix "/a" --root "/home/david/destdir" copying build/scripts-2.7/ndiff -> /home/david/destdir/a/bin But this doesn't: $ python setup.py install --prefix "/" --root "/home/david/destdir" copying build/scripts-2.7/ndiff -> /bin This looks like a Python/distutils bug. the same seems to happen on python install: when installing python 2.7.2, "2to3", "idle", "pydoc" and "smptd.py" are installed into /bin rather than into the chosen destdir ./python -E ./setup.py install \ --prefix=/ \ --install-scripts=//bin \ --install-platlib=//lib/python2.7/lib-dynload \ --root=//opt/python/ [...] running install running build running build_ext INFO: Can't locate Tcl/Tk libs and/or headers running install_scripts copying build/scripts-2.7/smtpd.py -> /bin copying build/scripts-2.7/idle -> /bin copying build/scripts-2.7/pydoc -> /bin copying build/scripts-2.7/2to3 -> /bin changing mode of /bin/smtpd.py to 755 changing mode of /bin/idle to 755 changing mode of /bin/pydoc to 755 changing mode of /bin/2to3 to 755 running install_egg_info Writing /lib/python2.7/lib-dynload/Python-2.7.2-py2.7.egg-info if test -f //opt/python//bin/python -o -h //opt/python//bin/python; \ then rm -f //opt/python//bin/python; \ else true; \ fi (cd //opt/python//bin; ln python2.7 python) rm -f //opt/python//bin/python-config (cd //opt/python//bin; ln -s python2.7-config python-config) test -d //opt/python//lib/pkgconfig || /bin/install -c -d -m 755 //opt/python//lib/pkgconfig rm -f //opt/python//lib/pkgconfig/python.pc [snip] -- components: Build messages: 171389 nosy: arschficker priority: normal severity: normal status: open title: Python/distutils setup.py: passing --prefix / makes --root ignored versions: Python 2.7 ___ Python tracker <http://bugs.python.org/issue16065> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue13659] Add a help() viewer for IDLE's Shell.
Ron Adam added the comment: What about having idle open a web browser session with pydocs new browse option? python3 -m pydoc -b We've added input fields to the pages that take the same input as help() command does. It also links to the online help pages, and you can view the source code of the files directly in the browser. (Sometimes that's the best documentation you can get.) -- nosy: +ron_adam ___ Python tracker <http://bugs.python.org/issue13659> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue13607] Move generator specific sections out of ceval.
Ron Adam added the comment: Updated patch with suggested changes. It also has a cleaned up fast_block_end section. Concerning speed. What happens is (as Tim and Raymond have pointed out) that we can make some things a little faster, in exchange for other things being a little slower. You can play around with the order of the why cases in the fast_block_end section and see that effect. By using a switch instead of if-else's, that should result in more consistent balance between the block exit cases. The order I currently have gives a little more priority for exceptions and that seems to help a tiny bit with the ccbench scores. I think that is a better bench mark than the small micro tests like pybench does. The problem with pybench is, it doesn't test deeper nesting where these particular changes will have a greater effect. -- Added file: http://bugs.python.org/file24087/f_why2.diff ___ Python tracker <http://bugs.python.org/issue13607> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue13607] Move generator specific sections out of ceval.
Changes by Ron Adam : Removed file: http://bugs.python.org/file24047/f_why1.diff ___ Python tracker <http://bugs.python.org/issue13607> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue13607] Move generator specific sections out of ceval.
Ron Adam added the comment:
I think the time benefits I saw are dependent on how the C code is compiled.
So it may be different on different compilers or the same compiler with only a
very minor change.
Some of the things I've noticed...
A switch is sometimes slower if it has a "default:" block.
Moving "why = tstate->why_exit;" to just before the if helps a tiny bit.
why = tstate->why_exit;
if (why != WHY_EXCEPTION) {
Returning directly out of the WHY_YIELD case.
case WHY_YIELD:
return result;
These will be mostly compiler dependent, but they won't slow things down any
either.
What I was trying to do is clean up things a bit in ceval.c. Having the why
available on the frame can help by allowing some things to be moved out of
ceval.c where it makes sense to do that.
I'll post a new diff tonight with the why_exit moved back to the frame object
and the why's back to enums. Yes, I think the frame object is a good place for
it.
One of the odd issues is the opcode and why values sometimes need to be pushed
on the value stack. Which means it needs to be converted to a pyobject first,
then converted back after it's pulled off the stack. I'm looking for a way to
avoid that.
I also was able to make fast_block_end section simpler and more understandable
without making it slower. I think it was trying to be too clever in order to
save some lines of code. That makes it very hard to figure out by someone else.
But first I need to finish my Christmas shopping, I'll post a new patch tonight
when I get a chance. :-)
--
___
Python tracker
<http://bugs.python.org/issue13607>
___
___
Python-bugs-list mailing list
Unsubscribe:
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue13607] Move generator specific sections out of ceval.
Ron Adam added the comment: New diff file. The main difference is I moved the saved why value to the tstate object instead of the frame object as why_exit. I'm not seeing the time savings now for some reason. Maybe the previous increase was a case of coincidental noise. (?) Still looking for other reasons though. ;-) Moving the generator code from the eval loop to the generator object may still be a good thing to do. -- Added file: http://bugs.python.org/file24047/f_why1.diff ___ Python tracker <http://bugs.python.org/issue13607> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue13607] Move generator specific sections out of ceval.
Changes by Ron Adam : Removed file: http://bugs.python.org/file23969/f_why.diff ___ Python tracker <http://bugs.python.org/issue13607> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue13607] Move generator specific sections out of ceval.
Ron Adam added the comment: A simple test to show the difference. BEFORE: $ python3 -mtimeit "def y(n):" " for x in range(n):" "yield x" "sum(y(10))" 10 loops, best of 3: 3.87 usec per loop $ python3 -mtimeit "def y(n):" " for x in range(n):" "yield x" "sum(y(100))" 10 loops, best of 3: 186 msec per loop AFTER: $ ./python -mtimeit "def y(n):" " for x in range(n):" "yield x" "sum(y(10))" 10 loops, best of 3: 3.81 usec per loop $ ./python -mtimeit "def y(n):" " for x in range(n):" "yield x" "sum(y(100))" 10 loops, best of 3: 168 msec per loop before after y(10) usec's 3.873.81 - 1.55% y(100)msec's 186 168 - 9.67% -- ___ Python tracker <http://bugs.python.org/issue13607> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue13607] Move generator specific sections out of ceval.
New submission from Ron Adam : The following changes cleanup the eval loop and result in a pretty solid 2 to 3% improvement in pybench for me. And it is about 5% faster for long generators. * Change why enum type to int and #defines. And moved the why defines to opcode.h so that they can be seen by the genrator objects after a yield, return, or exception. * Added an "int f_why" to frames so the generator can see why it returned from a send. * Refactored generator obj so it can use the "f->f_why" to determine what to do without having to do several checks first. * Moved the generator specific execption save/swap/and clear out of the cevel main loop. No need to check for those on every function call. The only test that fails is the frame size is test_sys. I left that in for now so someone could check that, and tell me if it's ok to fix it, or if I need to do something else. I also considered putting the why on the tstate object. It might save some memory as there wouldn't be as many of those. -- components: Interpreter Core files: f_why.diff keywords: patch messages: 149583 nosy: ron_adam priority: normal severity: normal status: open title: Move generator specific sections out of ceval. type: performance versions: Python 3.3 Added file: http://bugs.python.org/file23969/f_why.diff ___ Python tracker <http://bugs.python.org/issue13607> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue11682] PEP 380 reference implementation for 3.3
Ron Adam added the comment: Thanks for the updated links Nick. There is a comment in the docs that recommends putting parentheses around any yield expression that returns a value. So it is in agreement with that in the function argument case. The grammar I used does keep it as a variant. yield_expr 'yield' [testlist | yield_from] yield_from 'from' test The purpose of doing that is so I can do ... yield_expr 'yield' [testlist | yield_from | yield_raise] yield_from 'from' test yield_raise 'raise' [test ['from' test]] The yield_raise part is only an interesting exercise to help me understand cpythons internals better. I'm getting there and hope to be able to contribute to more bug fixes, and patches. :-) -- ___ Python tracker <http://bugs.python.org/issue11682> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue11682] PEP 380 reference implementation for 3.3
Ron Adam added the comment: There is a test for 'yield from' as a function argument without the extra parentheses. f(yield from x) You do need them in the case of a regular yield. f((yield)) or f((yield value)) Shouldn't the same rule apply in both cases? * I'm trying to do a version of the patch with 'yield_from' as a separate item from 'yield' in the grammar, but it insists on the parentheses due to it being a yield_expr component. -- nosy: +ron_adam ___ Python tracker <http://bugs.python.org/issue11682> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue11816] Refactor the dis module to provide better building blocks for bytecode analysis
Ron Adam added the comment: Instead of a get_instructions() function, How about using a DisCode class that defines the API for accessing Opinfo tuples of a disassembled object. So instead of... for instr in dis.bytecode_instructions(thing): process(instr) You could use... for instr in dis.DisCode(thing): process(instr) And I would like to be able to do... assertEqual(DisCode(thing1), DisCode(thing2)) It could also have a .dis() method that returns formatted output that matches what dis() currently prints. That would allow tests that use dis.dis() to get rid of capturing stdout with minimal changes. result = DisCode(func).dis() # return a dis compatible string. A DisCode object also offers a nice place to put documentation for the various pieces and an overall view of the new API without getting it confused with the current dis.dis() API. It's easier for me to remember an object with methods than several separate but related functions. (YMMV) This is very near a version of dis I did a while back where I removed the prints and returned a list of list object from dis.dis(). The returned object had __repr__ that formatted the data so it matched the current dis output. That made it work the same in a python shell. But I could still access and alter individual lines and fields by indexing or iterating it. While it worked nicely, it wouldn't be backwards compatible. -- nosy: +ron_adam ___ Python tracker <http://bugs.python.org/issue11816> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue13062] Introspection generator and function closure state
Changes by Ron Adam : -- nosy: +ron_adam ___ Python tracker <http://bugs.python.org/issue13062> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10713] re module doesn't describe string boundaries for \b
Changes by Ron Ridley : -- nosy: +Ron.Ridley ___ Python tracker <http://bugs.python.org/issue10713> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue2571] cmd.py always uses raw_input, even when another stdin is specified
Changes by Ron Adam : -- nosy: +ron_adam ___ Python tracker <http://bugs.python.org/issue2571> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue11182] pydoc.Scanner class not used by anything
New submission from Ron Adam : There doesn't seem to be any references to it in any other part of pydoc, or the Library for that matter. Searching for it on google code search (and also google web search) only turns up auto generated API references for python editing tools like VIM, and of course it's existence in pydoc itself. This doesn't appear to be related to the ModuleScanner class in any way other than possibly being a bit of left over example code. Can it be removed? -- components: Library (Lib) messages: 128365 nosy: ron_adam priority: normal severity: normal status: open title: pydoc.Scanner class not used by anything versions: Python 3.3 ___ Python tracker <http://bugs.python.org/issue11182> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue9364] some problems with the documentation of pydoc
Changes by Ron Adam : -- nosy: +ron_adam ___ Python tracker <http://bugs.python.org/issue9364> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue1038909] pydoc method documentation lookup enhancement
Ron Adam added the comment: I agree. It is close enough to be a duplicate. I suggest closing it. As Ka-Ping noted in the other issue: "There's a link to the base class provided if you want to find out what the base class does." This is easy to do if your viewing pydoc output in a web browser. And you can also look at the source code to see any comments. At some point we can consider enhancing the command line help mode to make it easier to do the same. -- ___ Python tracker <http://bugs.python.org/issue1038909> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10716] Modernize pydoc to use CSS
Ron Adam added the comment: A reminder: Check for instances where html.escape is not called on data inserted into the html pages. I'll update the patch as the non-css (error handling) parts made it into python 3.2. :-) -- ___ Python tracker <http://bugs.python.org/issue10716> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10961] Pydoc touchups in new browser for 3.2
Ron Adam added the comment: New and hopefully last patch... pydoc_misc_fix_e.diff I removed the .html in the ?key= links as Eric suggested. I checked the navbar float behavior on browsershots.org. Multiple versions of MSIE, firefox, opera, chrome, and safari were tested on Ubuntu and Windows XP. They all looked very close to each other. Better than I expected. :-) As for clearing floats, there is the html clear="all" attribute, and a css style="clear:both;". The browsershots.org tests confirms style="clear:both;" works as it should where I used it. Cheers, and hopefully this is ready to go. I believe it is. -- Added file: http://bugs.python.org/file20616/pydoc_misc_fix_e.diff ___ Python tracker <http://bugs.python.org/issue10961> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10961] Pydoc touchups in new browser for 3.2
Ron Adam added the comment: Ok, after input from Eric, Here is another patch. Removed a set of unneeded parentheses. Changed the title of the pages from PyDoc to Pydoc. A better fix for the uncaught floats. Wrap the main content in div with style="clear:both;". Should work on nearly everything. Also avoided floating the "get" and "search" form inputs. That was causing them to separate too much in IE. To summarize ... Minor fixes for new browser mode only. Fix float problems with the navbar. Change html page titles to "Pydoc" instead of "Python". Call html.markup() on topic contents. Fix topic/object shadowing. Improved error handling. (Part of the shadowing fix.) -- Added file: http://bugs.python.org/file20499/pydoc_misc_fix_d.diff ___ Python tracker <http://bugs.python.org/issue10961> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10961] Pydoc touchups in new browser for 3.2
Changes by Ron Adam : Removed file: http://bugs.python.org/file20473/pydoc_misc_fix_c.diff ___ Python tracker <http://bugs.python.org/issue10961> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10961] Pydoc touchups in new browser for 3.2
Ron Adam added the comment: George, My apologies to you for the late corrections. And thanks for doing this. Eric, I replied to your comments on Rietveld. Thanks for taking a look. I'll wait until you have a chance to reply and test it, then upload a new patch with any needed changes. Ron -- ___ Python tracker <http://bugs.python.org/issue10961> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10961] Pydoc touchups in new browser for 3.2
Changes by Ron Adam : -- nosy: +eric.araujo, rhettinger ___ Python tracker <http://bugs.python.org/issue10961> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10961] Pydoc touchups in new browser for 3.2
Changes by Ron Adam : Removed file: http://bugs.python.org/file20468/pydoc_misc_fix.diff ___ Python tracker <http://bugs.python.org/issue10961> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10961] Pydoc touchups in new browser for 3.2
Ron Adam added the comment: A few last minute changes.. I think this will be all. Run topic contents through html.markup. That makes ref:, pep:, and html: links if they exist. (I meant to this earlier.) Fix case where topic reference links are to objects rather than another topic. (applies to keywords also.) Skips making an empty reference section if there are no references with a topic. These are all small changes, and nothing should be controversial in this as everything changed only effects the new html browser mode. -- Added file: http://bugs.python.org/file20473/pydoc_misc_fix_c.diff ___ Python tracker <http://bugs.python.org/issue10961> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10961] Pydoc touchups in new browser for 3.2
Changes by Ron Adam : Removed file: http://bugs.python.org/file20467/pydoc_misc_fix.diff ___ Python tracker <http://bugs.python.org/issue10961> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10961] Pydoc touchups in new browser for 3.2
Ron Adam added the comment: new patch... Adjusted a comment in the _gettopic method. Everything else the same. -- Added file: http://bugs.python.org/file20468/pydoc_misc_fix.diff ___ Python tracker <http://bugs.python.org/issue10961> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10961] Pydoc touchups in new browser for 3.2
New submission from Ron Adam : A collection of small fix's that only effect the new browser mode. * Change title of html pages from "Python ..." to "PyDoc ...". * Fixed unterminated div float for items returned without a header. example: str, None, True, False * Added "topic?key=..." url command to explicitly get topics. This is to avoid the shadowing when an object has the same name as a topic. * Nicer parsing and error handling in the url handler. -- components: Library (Lib) files: pydoc_misc_fix.diff keywords: patch messages: 126633 nosy: georg.brandl, ron_adam priority: normal severity: normal status: open title: Pydoc touchups in new browser for 3.2 type: behavior versions: Python 3.2 Added file: http://bugs.python.org/file20467/pydoc_misc_fix.diff ___ Python tracker <http://bugs.python.org/issue10961> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10918] **kwargs unnecessarily restricted in concurrent.futures 'submit' API
Ron Adam added the comment: Yes, you are correct. Pulling the first value off of args would work. This is new for 3.2, can it still be changed? One more thing to consider... One of the things I look at for functions like these is, how easy is it to separate the data from the program interface? I prefer: submit_data = [fn, args, kwds] e.submit(*submit_data) or.. submit_args = [(a, k), (a, k), ... ] for args, kwds in submit_args: e.submit(fn, args, kwds) But its a trade off against easier direct calling. My feelings, is submit will be used more in an indirect way, like these examples, rather than being used directly by writing out each submit separately. -- ___ Python tracker <http://bugs.python.org/issue10918> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10918] **kwargs unnecessarily restricted in concurrent.futures 'submit' API
Ron Adam added the comment: Change... "are never unpacked within submit." to... Are completely separate. It's the attempt to mix two function signatures together as one, that was/is the problem. -- ___ Python tracker <http://bugs.python.org/issue10918> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10918] **kwargs unnecessarily restricted in concurrent.futures 'submit' API
Ron Adam added the comment:
Here is the whole method for reference...
def submit(self, fn, *args, **kwargs):
with self._shutdown_lock:
if self._shutdown_thread:
raise RuntimeError('cannot schedule new futures after shutdown')
f = _base.Future()
w = _WorkItem(f, fn, args, kwargs)
self._pending_work_items[self._queue_count] = w
self._work_ids.put(self._queue_count)
self._queue_count += 1
self._start_queue_management_thread()
self._adjust_process_count()
return f
submit.__doc__ = _base.Executor.submit.__doc__
If self and fn are in kwargs, they are probably a *different* self and fn, than
the self and fn passed to submit!
The current submit definition doesn't allow that, and pulling out self, and fn,
would not be correct either.
If it's still possible to change the method call signature, it should be
without asterisks...
def submit(self, fn, args, kwargs):
...
Then the correct way to call it would be...
submit(foo, [1, 2], dict(fn=bar))
There wouldn't be a conflict because the args, and keywords, (to be eventually
passed to fn), are never unpacked within submit.
--
___
Python tracker
<http://bugs.python.org/issue10918>
___
___
Python-bugs-list mailing list
Unsubscribe:
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10918] **kwargs unnecessarily restricted in API
Ron Adam added the comment: Is this issue referring to something in Python's library, or a hypothetical function someone may write? If it's in the library, we can look at that case in more detail, otherwise, it's just a bad program design issue and there's nothing to do. -- ___ Python tracker <http://bugs.python.org/issue10918> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10918] **kwargs unnecessarily restricted in API
Ron Adam added the comment: Why is this surprising? >>> def foo(c, c=None): ... pass ... File "", line 1 SyntaxError: duplicate argument 'c' in function definition In the previous examples, it finds the duplicate at run time instead of compile time due to not being able to determine the contents of kwargs at compile time. It's just a bug in your code if you do it, and it should raise an exception as it does. -- nosy: +ron_adam ___ Python tracker <http://bugs.python.org/issue10918> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
