[issue37152] Add AF_LOCAL alias for AF_UNIX
New submission from carlo : both mean the same thing and are used to reference local socket files if you do a `man socket` one of the lines says PF_LOCALHost-internal protocols, formerly called PF_UNIX, (AF and PF mean the same thing here, but importantly it shows that PF_UNIX has been depreciated) this change gives users the option to type socket.AF_LOCAL as well as socket.AF_UNIX when specifying the address family for the socket. this is my first issue so lmk if there is anything I'm missing ) -- components: Library (Lib) messages: 344585 nosy: frosty00 priority: normal severity: normal status: open title: Add AF_LOCAL alias for AF_UNIX versions: Python 3.7 ___ Python tracker <https://bugs.python.org/issue37152> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue37152] Add AF_LOCAL alias for AF_UNIX
Change by carlo : -- keywords: +patch pull_requests: +13695 stage: -> patch review pull_request: https://github.com/python/cpython/pull/13810 ___ Python tracker <https://bugs.python.org/issue37152> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue37152] Add AF_LOCAL alias for AF_UNIX
carlo added the comment: > I'm -1 to add the alias. It just adds to the confusion. It's also against the > Zen of Python: "There should be one-- and preferably only one --obvious way > to do it." Agreed with the zen of python. This is my first PR / issue, thanks for the fast reply. You may close this issue ) -- ___ Python tracker <https://bugs.python.org/issue37152> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue22307] os.getlogin() documentation has misleading side note
New submission from Carlo: The documentation for os.getlogin() says: ... ``pwd.getpwuid(os.getuid())[0]`` to get the login name of the currently effective user id Either, os.getuid() should be changed to os.geteuid(), or the wording should be changed. -- assignee: docs@python components: Documentation messages: 226139 nosy: Carlo, docs@python priority: normal severity: normal status: open title: os.getlogin() documentation has misleading side note versions: Python 3.4, Python 3.5 ___ Python tracker <http://bugs.python.org/issue22307> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue13252] new decumulate() function in itertools module
New submission from Carlo Verre : After in Python 3.2 the accumulate() function has been added to itertools module, for self-evident reasons of completeness and symmetry we could add in 3.3 the inverse decumulate() function, which, given the iterable argument p, yields p[0], p[1] - p[0], p[2] - p[1]... Its equivalent python form is in the attached file decumulate.py, below. -- components: Extension Modules files: decumulate.py messages: 146263 nosy: carlo.verre, rhettinger priority: normal severity: normal status: open title: new decumulate() function in itertools module type: feature request versions: Python 3.3 Added file: http://bugs.python.org/file23507/decumulate.py ___ Python tracker <http://bugs.python.org/issue13252> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10560] Fixes for Windows sources
New submission from Carlo Bramini : Hello, I was able to compile latest python sources with MSVC5, by importing and fixing a bit the project workspaces of MSVC6. During this action I received some messages, so I gave a look to the sources and I would like to suggest the following fixes: 1) in posixmodule.c, I had a warning of constant out of range for secs_between_epochs. The problem has been solved by applying "i64" suffix as suggested in MSDN for doing correct declaration of 64 bits constants. While doing this fix, I took this chance for adding support for all currently supported platforms: MSVC, GCC and Watcom. 2) in posixmodule.c, I fixed a bit check_gfax() function: - Function declaration has been fixed with 'void' in its parameter section (fixes a warning). - I removed the variable 'checked' and I placed instead the handle to kernel32 module. - I removed the L-value assignment: all other source codes in Python are already corrected in that manner, this is the last one that needs to be fixed. 3) in posixmodule.c, there is a bug in function Py_GetFileAttributesExW(): it tests for 'gfaxa' but later it uses 'gfaxw'. 4) in dl_nt.c, I fixed function prototypes with "void" (solves a warning). 5) in dl_nt.c, in function _LoadActCtxPointers(), I do not see a good reason for using widechar version of GetModuleHandle, since it just need to retrieve the instance of kernel32. 6) in dynload_win.c, I fixed _Py_ActivateActCtx prototype declaration (solves a warning). 7) in dynload_win.c, I suggest to rename local strcasecmp() to something less dangerous to prototype conflicts. 8) in dynload_win.c, in function _PyImport_GetDynLoadFunc() the first 'cookie' variable is not used, so its declaration has been removed. I hope you will find this useful. Sincerely, Carlo Bramini. -- components: Windows files: python.txt messages: 122651 nosy: Carlo_Bramini priority: normal severity: normal status: open title: Fixes for Windows sources Added file: http://bugs.python.org/file19853/python.txt ___ Python tracker <http://bugs.python.org/issue10560> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10560] Fixes for Windows sources
Carlo Bramini added the comment: According to the instructions received at #python-dev, I'm posting a new patch with the same fixes made on the most recent SVN sources (py3k). Actually the new patch does not include the fixes made on the GetFileAttributesEx wrappers since they have been removed in the SVN sources; however I would like to remember that removing that code will also break support for Windows 98 and Windows ME: it's true that they have it but only ASCII version is working. Sincerely, Carlo Bramini. -- Added file: http://bugs.python.org/file19855/python-svn.txt ___ Python tracker <http://bugs.python.org/issue10560> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10560] Fixes for Windows sources
Carlo Bramini added the comment: I modified the patch by using Py_LL() as suggested in a previous comment. I just would like to say that these fixes are not required to compiling under MSVC5: I was able to compile all the sources as they were, even without changes and this is a great thing. I have just noticed, from some strange warning messages, that few things required to be fixed, now reduced to correct __STDC__ syntax to some functions (declaring in that manner is wrong anyways, since it's C89) and fix a constant with the right modifier. -- Added file: http://bugs.python.org/file19863/python-svn.txt ___ Python tracker <http://bugs.python.org/issue10560> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue2139] sqlite3 module needs upgrading
New submission from carlo verr: In Python 2.5.2.c1 the sqlite3 module contains (exactly as Python 2.5.1 does) PySQLite 2.3.2 with SQLite 3.3.4, which is very old and very buggy, it hungs randomly. Last available version of SQLite is 3.5.6. Last available version of PySQLite for Python 2.5 is 2.4.1, which contains SQLite 3.5.2. -- components: Library (Lib) messages: 62521 nosy: carloverre severity: normal status: open title: sqlite3 module needs upgrading type: behavior versions: Python 2.5 __ Tracker <[EMAIL PROTECTED]> <http://bugs.python.org/issue2139> __ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue43964] ctypes CDLL search path issue on MacOS
Carlo Cabrera added the comment: Re option 3: relying on `DYLD_LIBRARY_PATH` or `DYLD_FRAMEWORK_PATH` isn't a great solution either because of SIP. It's can get impractical to use in many standard Makefile-based build systems, for example. (cf. https://github.com/qmk/qmk_cli/issues/60, https://github.com/Homebrew/discussions/discussions/1737) I imagine it can get quite vexing to set these variables but find them to not have the effect you expected them to. One workaround for the example above would be to compile your own `make` program (or use one from a package manager) so that SIP doesn't sanitise your environment, but I imagine that's not an ideal solution either. -- nosy: +ccabrera ___ Python tracker <https://bugs.python.org/issue43964> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue32244] Multiprocessing: multiprocessing.connection.Listener.accept() should accept a timeout
Carlo Dri added the comment: In agree with this proposal! I was looking for the exact same possibility of specifying a timeout to the accept() method, both in AF_INET and AF_PIPE sockets. If there is any better way to implement this I would love to hear it. -- nosy: +carlodri ___ Python tracker <https://bugs.python.org/issue32244> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue32244] Multiprocessing: multiprocessing.connection.Listener.accept() should accept a timeout
Change by Carlo Dri : -- versions: +Python 3.8 ___ Python tracker <https://bugs.python.org/issue32244> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue33533] Provide an async iterator version of as_completed
Change by Carlo Dri : -- nosy: +carlodri ___ Python tracker <https://bugs.python.org/issue33533> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue34410] Segfault/TimeoutError: itertools.tee of multiprocessing.pool.imap_unordered
New submission from Carlo Rosati : Hello, When I run the attached code, I encounter a segmentation fault. Thanks, Carlo -- files: 3.py messages: 323546 nosy: carlorosati priority: normal severity: normal status: open title: Segfault/TimeoutError: itertools.tee of multiprocessing.pool.imap_unordered type: crash versions: Python 2.7, Python 3.7 Added file: https://bugs.python.org/file47750/3.py ___ Python tracker <https://bugs.python.org/issue34410> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue34410] Segfault/TimeoutError: itertools.tee of multiprocessing.pool.imap_unordered
Carlo Rosati added the comment: I figured out that the problem is itertools.tee does not use a multiprocessing.Manager proxied object for shared state. I was able to create a workaround tee as follows. def multiprocessing_tee(iterable, n=2): """Write a multiprocessing safe itertools.tee""" it = iter(iterable) m = multiprocessing.Manager() lists = [m.list() for i in range(n)] def gen(local_list): keep_m_alive = m while True: if not local_list: # when the local list is empty newval = next(it) # fetch a new value and for l in lists:# load it to all the lists l.append(newval) yield local_list.pop(-1) return tuple(gen(l) for l in lists) -- ___ Python tracker <https://bugs.python.org/issue34410> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue34410] Segfault/TimeoutError: itertools.tee of multiprocessing.pool.imap_unordered
Carlo Rosati added the comment: Okay I needed to do .pop(0) instead of .pop(-1) which is probably O(N) -- ___ Python tracker <https://bugs.python.org/issue34410> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue34410] Segfault/TimeoutError: itertools.tee of multiprocessing.pool.imap_unordered
Carlo Rosati added the comment: You'll also need to lock when modifying the manager's list. Does anyone know how to do this using the multiprocessing.Queues without deadlocking? -- ___ Python tracker <https://bugs.python.org/issue34410> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue34410] Segfault/TimeoutError: itertools.tee of multiprocessing.pool.imap_unordered
Carlo Rosati added the comment: I've actually written a few workarounds that should be considered a multiprocessing specific tee function. I need feedback/critique on these. Hopefully we can all agree on one solution that's the best. It is unfortunate that the multiprocessing manager does not provide a dequeue. The first one I wrote uses a managed list. def multiprocessing_tee(iterable, n=2): """Write a multiprocessing safe itertools.tee""" it = iter(iterable) m = multiprocessing.Manager() mylock = m.Lock() lists = [m.list() for i in range(n)] def gen(local_list): for i in itertools.count(): with mylock: if not local_list: # when the local list is empty newval = next(it) # fetch a new value and for l in lists:# load it to all the lists l.append(newval) yield local_list.pop(0) return tuple(gen(l) for l in lists) The second two implementations use queues. def multiprocessing_tee_q(iterable, n=2): """Write a multiprocessing safe itertools.tee""" it = iter(iterable) m = multiprocessing.Manager() lock = m.Lock() queues = [m.Queue(-1) for _ in range(n)] # -1 means infinite maxsize (so puts won't block) def gen(myqueue): while True: with lock: # no one else touches anything try: newval = myqueue.get_nowait() except Queue.Empty: newval = next(it) for q in queues: q.put(newval) newval = myqueue.get() yield newval return tuple(gen(q) for q in queues) class Sentinel(object): """used as Queue Sentinel""" def multiprocessing_tee_q2(iterable, n=2): """Write a multiprocessing safe itertools.tee""" it = iter(iterable) m = multiprocessing.Manager() lock = m.Lock() queues = [m.Queue(-1) for _ in range(n)] # -1 means infinite maxsize (so puts won't block) def gen(myqueue): while True: try: retval = myqueue.get_nowait() except Queue.Empty: # what happens if the other process puts last item in my queue before i get lock? with lock: # no one else touches anything try: newval = next(it) except StopIteration: newval = Sentinel for q in queues: q.put(newval) retval = myqueue.get() if retval is Sentinel: raise StopIteration yield retval return tuple(gen(q) for q in queues) I'm just throwing out my sketches here. I'm hoping the more experienced here can weigh in on these implementations. -- ___ Python tracker <https://bugs.python.org/issue34410> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue34410] Segfault/TimeoutError: itertools.tee of multiprocessing.pool.imap_unordered
Carlo Rosati added the comment: `for i in itertools.count()` in the first implementation I posted should be `while True`. I was using that for debugging. -- ___ Python tracker <https://bugs.python.org/issue34410> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue34410] Segfault/TimeoutError: itertools.tee of multiprocessing.pool.imap_unordered
Carlo Rosati added the comment: If what you've said is correct, would it make the most sense to create a Manager method which returns a Proxy to a tee'd iterator? -- ___ Python tracker <https://bugs.python.org/issue34410> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue27488] Underscore not showing Mac El Capitan
New submission from Monti Carlo: Trying to type in underscore and it just made a space... Downloaded 3.5.2 and it works fine. -- components: IDLE messages: 270205 nosy: Monti Carlo priority: normal severity: normal status: open title: Underscore not showing Mac El Capitan versions: Python 3.4 ___ Python tracker <http://bugs.python.org/issue27488> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10560] Fixes for Windows sources
Carlo Bramini added the comment: I have downloaded the latest sources with HG and, with the only exception of the variable "cookie" now conditionally declared with an "#ifdef HAVE_SXS", yes, all these fixes are still actual. -- status: pending -> open ___ Python tracker <http://bugs.python.org/issue10560> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10560] Fixes for Windows sources
Carlo Bramini added the comment: Hello, no problem, the fix on GetModuleHandle() can be avoided without problems if you want. Anyways, although nowadays the "hybrid" operating systems like Windows 9x/ME are dead and burried, in this particular case I would still suggest to use directly GetModuleHandleA(), because the instance to find is just "KERNEL32" and it is not made by esoteric characters. Normally, as developer for Windows platform, I would surely agree to use the wide char version, but due to the highly portable nature of Python, with my experience I learned that some particular conditions can make the cross compiling for Windows easier, if you do not explicitely add "-fshort-wchar". BTW, the ".dll" in the string of the parameter is redundant as you can see from MSDN page of GetModuleHandle(), there are also few other points in the sources of Python that can be "optimized", but afterall these are just "fine" improvements, not so much important if they are compared to other things... -- ___ Python tracker <http://bugs.python.org/issue10560> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue26125] Incorrect error message in the module asyncio.selector_events.
New submission from Carlo Beccarini:
Incorrect error message in the module asyncio.selector_events for the methods:
_SelectorSocketTransport.write
_SelectorSslTransport.write
_SelectorDatagramTransport.sendto.
The previous error was raising a Tuple:
TypeError: ('data argument must be byte-ish (%r)', )
Patched:
TypeError: data argument must be a bytes-like object, not 'str'
--
components: asyncio
files: patch.diff
keywords: patch
messages: 258294
nosy: Paradisee, gvanrossum, haypo, yselivanov
priority: normal
severity: normal
status: open
title: Incorrect error message in the module asyncio.selector_events.
versions: Python 3.4
Added file: http://bugs.python.org/file41624/patch.diff
___
Python tracker
<http://bugs.python.org/issue26125>
___
___
Python-bugs-list mailing list
Unsubscribe:
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue26125] Incorrect error message in the module asyncio.selector_events.
Changes by Carlo Beccarini : -- type: behavior -> versions: +Python 3.4 -Python 3.5, Python 3.6 Added file: http://bugs.python.org/file41625/patch.diff ___ Python tracker <http://bugs.python.org/issue26125> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue26125] Incorrect error message in the module asyncio.selector_events.
Carlo Beccarini added the comment: https://github.com/python/asyncio/pull/313 -- ___ Python tracker <http://bugs.python.org/issue26125> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue26157] Typo in asyncio documentation
Carlo Beccarini added the comment: Absolutely. -- nosy: +Paradisee ___ Python tracker <http://bugs.python.org/issue26157> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue26157] Typo in asyncio documentation
Changes by Carlo Beccarini : -- versions: +Python 3.4 ___ Python tracker <http://bugs.python.org/issue26157> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue26157] Typo in asyncio documentation
Changes by Carlo Beccarini : -- keywords: +patch Added file: http://bugs.python.org/file41662/patch.diff ___ Python tracker <http://bugs.python.org/issue26157> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue23512] The list of built-in http://text-processing.com/demo/sentiments is not alphabetical on https://docs.python.org/2/library/functions.html
Carlo Beccarini added the comment: Well, these built-in are considered as non essential. -- nosy: +Paradisee title: List of builtins is not alphabetical on https://docs.python.org/2/library/functions.html -> The list of built-in http://text-processing.com/demo/sentiments is not alphabetical on https://docs.python.org/2/library/functions.html ___ Python tracker <http://bugs.python.org/issue23512> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue23512] The list of built-in http://text-processing.com/demo/sentiments is not alphabetical on https://docs.python.org/2/library/functions.html
Carlo Beccarini added the comment: Maybe we could put them in another table below the current one. -- ___ Python tracker <http://bugs.python.org/issue23512> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue23512] The list of built-in functions is not alphabetical on https://docs.python.org/2/library/functions.html
Carlo Beccarini added the comment: diff -r 3019effc44f2 Doc/library/functions.rst --- a/Doc/library/functions.rst Mon Mar 02 11:17:05 2015 -0500 +++ b/Doc/library/functions.rst Mon Mar 02 21:13:27 2015 +0100 @@ -22,10 +22,10 @@ :func:`classmethod` :func:`getattr`:func:`map` |func-repr|_ :func:`xrange` :func:`cmp` :func:`globals`:func:`max` :func:`reversed` :func:`zip` :func:`compile` :func:`hasattr`|func-memoryview|_ :func:`round` :func:`__import__` -:func:`complex` :func:`hash` :func:`min` |func-set|_ :func:`apply` -:func:`delattr` :func:`help` :func:`next`:func:`setattr` :func:`buffer` -|func-dict|_ :func:`hex`:func:`object` :func:`slice` :func:`coerce` -:func:`dir` :func:`id` :func:`oct` :func:`sorted` :func:`intern` +:func:`complex` :func:`hash` :func:`min` |func-set|_ .. +:func:`delattr` :func:`help` :func:`next`:func:`setattr` .. +|func-dict|_ :func:`hex`:func:`object` :func:`slice` .. +:func:`dir` :func:`id` :func:`oct` :func:`sorted` .. === = == = .. using :func:`dict` would create a link to another page, so local targets are @@ -1699,6 +1699,11 @@ Python programmers, trainers, students and book writers should feel free to bypass these functions without concerns about missing something important. +=== = == = +.. Non-essentialBuilt-in Functions .. +=== = == = +:func:`apply`:func:`buffer` :func:`coerce` :func:`intern` +=== = == = .. function:: apply(function, args[, keywords]) -- Added file: http://bugs.python.org/file38304/functools.rst ___ Python tracker <http://bugs.python.org/issue23512> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue23512] The list of built-in functions is not alphabetical on https://docs.python.org/2/library/functions.html
Changes by Carlo Beccarini : Added file: http://bugs.python.org/file38305/functions.rst ___ Python tracker <http://bugs.python.org/issue23512> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue23512] The list of built-in functions is not alphabetical on https://docs.python.org/2/library/functions.html
Changes by Carlo Beccarini : Added file: http://bugs.python.org/file38307/functions.rst ___ Python tracker <http://bugs.python.org/issue23512> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue23512] The list of built-in functions is not alphabetical on https://docs.python.org/2/library/functions.html
Changes by Carlo Beccarini : Removed file: http://bugs.python.org/file38305/functions.rst ___ Python tracker <http://bugs.python.org/issue23512> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue23512] The list of built-in functions is not alphabetical on https://docs.python.org/2/library/functions.html
Changes by Carlo Beccarini : -- keywords: +patch Added file: http://bugs.python.org/file38316/issue23512.diff ___ Python tracker <http://bugs.python.org/issue23512> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue23512] The list of built-in functions is not alphabetical on https://docs.python.org/2/library/functions.html
Changes by Carlo Beccarini : Removed file: http://bugs.python.org/file38307/functions.rst ___ Python tracker <http://bugs.python.org/issue23512> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue46447] datetime.isoformat() documentation does not point to the risk of using it with naive datetime objects
New submission from Jean Carlo Machado : datetime.utcnow() already present a warning box describing the risk of using it without specifying timezone information. However, one might still have the same problem and never encounter this warning information by doing datetime.now().isoformat(). Or just by not reading the docs of datetime.utcnow, just the datetime.isoformat docs. By adding a similar warning to the datetime.isoformat() we could make the risk clearer and reduce the likelihood of errors. Is when calling isoformat() where people get confident to be producing ISO's. I just recently had an incident in my company where we produced naive datetimes using datetime.now() and serialized them using isoformat() while expecting them to be a transferrable ISO format. Nevertheless, the other system read the dates without Z in the end and interpreted it as local time. If you agree that this suggestion could be a good improvement to the docs, I can send a patch in the next 2 weeks. -- assignee: docs@python components: Documentation messages: 411046 nosy: docs@python, jeanCarloMachado priority: normal severity: normal status: open title: datetime.isoformat() documentation does not point to the risk of using it with naive datetime objects type: enhancement versions: Python 3.11 ___ Python tracker <https://bugs.python.org/issue46447> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue46447] datetime.isoformat() documentation does not point to the risk of using it with naive datetime objects
Change by Jean Carlo Machado : -- keywords: +patch pull_requests: +29032 stage: -> patch review pull_request: https://github.com/python/cpython/pull/30850 ___ Python tracker <https://bugs.python.org/issue46447> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue13917] Python 2.7.2 and 3.2.2 execl crash
New submission from Carlo Di Dato :
These lines make Python 2.7.2 and 3.2.2 crash
import os
os.execl("cmd.exe", "")
Regards
--
components: Windows
messages: 152428
nosy: shinnai
priority: normal
severity: normal
status: open
title: Python 2.7.2 and 3.2.2 execl crash
type: crash
versions: Python 2.7, Python 3.1
___
Python tracker
<http://bugs.python.org/issue13917>
___
___
Python-bugs-list mailing list
Unsubscribe:
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue13917] Python 2.7.2 and 3.2.2 execl crash
Changes by Carlo Di Dato : -- versions: +Python 3.2 -Python 3.1 ___ Python tracker <http://bugs.python.org/issue13917> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue29006] 2.7.13 _sqlite more prone to "database table is locked"
Gian-Carlo Pascutto added the comment: >Then we wait for someone that really knows why the change was done in the >first place. Python 2.7 had a regression compared to 2.6 where a SELECT after a COMMIT would silently return the wrong data: http://bugs.python.org/issue23129 http://bugs.python.org/issue10513 Neither exiting with a locked error nor producing the wrong data are particularly appealing results. Did 2.6 pass those sets that caused the attempted fix to get backed out? -- nosy: +Gian-Carlo Pascutto ___ Python tracker <http://bugs.python.org/issue29006> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue25356] Idle (Python 3.4 on Ubuntu) does not allow typing accents
New submission from Gian Carlo Martinelli: IDLE (using Python 3.4 on Ubuntu) does not recognize accent key presses (ex: ~, ^, '). This makes it impossible to program in some languages. -- components: IDLE messages: 252620 nosy: Gian Carlo Martinelli priority: normal severity: normal status: open title: Idle (Python 3.4 on Ubuntu) does not allow typing accents type: behavior versions: Python 3.4 ___ Python tracker <http://bugs.python.org/issue25356> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue25356] Idle (Python 3.4 on Ubuntu) does not allow typing accents
Gian Carlo Martinelli added the comment: 1) Do the keys work in the Ubuntu console? Yes. 2) Do the keys work in interactive python (not IDLE), started with 'python' at the console prompt. Yes. 3) In IDLE, go to Help->About IDLE. What is the Tk version. Best if 8.6.x, if before 8.5.18, upgrade. 8.6.1 4) Try typing in the text box, including the problem chars. What happens? Ran the program, all characters work perfectly. -- ___ Python tracker <http://bugs.python.org/issue25356> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue25356] Idle (Python 3.4 on Ubuntu) does not allow typing accents
Gian Carlo Martinelli added the comment:
Terry, first of all thanks for trying to solve this.
I usually start IDLE using Ubuntu's dash.
The problem is with more than just the three characters. Others that I have
tested and that don't work include "ç", "`", umlauts... There work in others
places in my system such as the console for example.
When I try ALT+M or CTRL+O, inside IDLE, these characters work.
This is a copy of my output. Seems OK
! " # $ % & ' ( ) * + , - . /
0 1 2 3 4 5 6 7 8 9 : ; < = > ?
@ A B C D E F G H I J K L M N O
P Q R S T U V W X Y Z [ \ ] ^ _
` a b c d e f g h i j k l m n o
p q r s t u v w x y z { | } ~
--
___
Python tracker
<http://bugs.python.org/issue25356>
___
___
Python-bugs-list mailing list
Unsubscribe:
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue25356] Idle (Python 3.4 on Ubuntu) does not allow typing accents
Gian Carlo Martinelli added the comment:
@Terry
Using 'Find in Files' (Alt+F3) works fine. I can type everything normally. Also
in the Output everything is fine.
Apparently the problem is only with diacriticals (I mentioned 'ç', but it is
working (I have a particular key for that in my keyboard... it is a Brazilian
keyboard)).
@Serhiy
The problem is both with standalone keys ('`~^) and accented characters (ãẽéáà
etc)
Today I found a very strange behaviour.
IF I start IDLE with a clean file, everything works fine.
If then I open a .py file, or save the new file as .py, after 3-5 seconds these
keys stop working. Very strange...
I hope I was clear in describing this.
@Ankit: check if this behavior is the same for you.
--
___
Python tracker
<http://bugs.python.org/issue25356>
___
___
Python-bugs-list mailing list
Unsubscribe:
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue25356] Idle (Python 3.4 on Ubuntu) does not allow typing accents
Gian Carlo Martinelli added the comment: Any additional input on this issue? -- ___ Python tracker <http://bugs.python.org/issue25356> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue23129] sqlite3 COMMIT nested in SELECT returns unexpected results
Gian-Carlo Pascutto added the comment:
I've ran into this as well, when a program that was running correctly with
PostgreSQL turned out to produce garbage with SQLite. Code to reproduce roughly
looks like this:
sel_cursor = conn.cursor()
sel_cursor.execute("SELECT prim_key_id FROM "
"somedb ORDER BY start_time ASC")
add_cursor = conn.cursor()
prim_keys = set()
row = sel_cursor.fetchone()
while row:
seq = row[0]
if seq in prim_keys:
raise RuntimeError
prim_keys.add(seq)
add_cursor.execute("INSERT INTO someotherdb "
"VALUES (?)",
seq)
conn.commit()
row = sel_cursor.fetchone()
conn.commit()
This will raise a RuntimeError because the SELECT will return the same primary
key value twice - something that's obviously impossible.
This exact bug has been filed once more already, and it seems to be an actual
regression in Python 2.7:
http://bugs.python.org/issue10513
Looking at the code there, I agree with the analysis in this message:
http://bugs.python.org/issue10513#msg150162
Either the pysqlite_do_all_statements should set reset_cursors=1 to warn the
user that the cursor has been reset, or it shouldn't reset them to begin with
(as Python <2.7 used to do).
I don't think there's any argument this isn't a (bad) bug: Python <2.7 works
correctly and later versions silently corrupt data.
--
nosy: +Gian-Carlo Pascutto
___
Python tracker
<http://bugs.python.org/issue23129>
___
___
Python-bugs-list mailing list
Unsubscribe:
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue10513] sqlite3.InterfaceError after commit
Gian-Carlo Pascutto added the comment: I believe http://bugs.python.org/issue23129 is a dupe of this. The patch here has been in "patch review" for 9 months. That seems fairly long for something that's a regression that potentially silently produces the wrong data. -- nosy: +Gian-Carlo Pascutto ___ Python tracker <http://bugs.python.org/issue10513> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
