Lele Gaifax added the comment:
Hey, recompiling current master against readline 8.1 gives an interpreter where
this is already working: rl_operate_and_get_next() is bound to Control-o in the
standard emacs keymap!
http://git.savannah.gnu.org/cgit/readline.git/tree/emacs_keymap.c?h=readline
Lele Gaifax added the comment:
Apparently, now the operate-and-get-next function has been moved to the
readline library, so hopefully it will be easier to get its advantage.
See point 2.j in https://lwn.net/Articles/839213/
--
___
Python tracker
Lele Gaifax added the comment:
I rebased my work on current master of the cpython git repository, cherry
picking the changes from the old branch (that was based on a at the time
unofficial git mirror of the mercurial repository).
To avoid any ambiguity I called it "issue8_3
Lele Gaifax added the comment:
Luckily the referenced branch is still around on GH:
https://github.com/lelit/cpython-hg-mirror/tree/issue8_2
As the name says, it is not related to modern CPython' git repo though.
--
___
Python tracker
<ht
Change by Lele Gaifax :
--
keywords: +patch
pull_requests: +9141
stage: needs patch -> patch review
___
Python tracker
<https://bugs.python.org/issu
New submission from Lele Gaifax :
$ python3.7 msgfmt.py -o test.mo test.po
msgfmt.py:199: DeprecationWarning: tostring() is deprecated. Use tobytes()
instead.
output = generate()
--
components: Demos and Tools
messages: 322001
nosy: lelit
priority: normal
severity: normal
status
Lele Gaifax <lelegai...@gmail.com> added the comment:
Thank you Berker, I'm sorry I could not find the time to investigate the
problem by myself.
--
___
Python tracker <rep...@bugs.python.org>
<https://bugs.python
Lele Gaifax <lelegai...@gmail.com> added the comment:
Sorry, I could not find an easy enough way to compile against SQLite 3.8.7.1,
being on Debian sid myself (3.22). I hope to find some time to try harder.
--
___
Python tracke
Lele Gaifax <lelegai...@gmail.com> added the comment:
I suspect this won't land in 3.7...
Let me know if I can do something to make that happen, or instead if I should
try to rebase the change on top of current master and rectify references to the
Python v
Lele Gaifax <lelegai...@gmail.com> added the comment:
Thank you Serhiy, ok: will simplify the method, hopefully tomorrow.
--
___
Python tracker <rep...@bugs.python.org>
<https://bugs.python
Lele Gaifax <lelegai...@gmail.com> added the comment:
You are right, thank you.
--
resolution: -> not a bug
stage: -> resolved
status: open -> closed
___
Python tracker <rep...@bugs.python.org>
<https://bu
Lele Gaifax <lelegai...@gmail.com> added the comment:
I need advice on Serhiy's proposal of dropping support to plain file name (see
also https://github.com/python/cpython/pull/4238#discussion_r155725986).
Wrt the other point I filed issue
New submission from Lele Gaifax <lelegai...@gmail.com>:
The function calls ``sqlite3_open()`` that, if I understand its documentation
correctly[#], returns a new connection object in all cases (that is, even on
errors) with the only exception of "out of memory" (in wh
Lele Gaifax <lelegai...@gmail.com> added the comment:
Just to keep the door open, I'm willing to to whatever is needed to see this
accepted and merged.
--
___
Python tracker <rep...@bugs.python.org>
<https://bugs.python
Lele Gaifax <lelegai...@gmail.com> added the comment:
As suggested by Brett Cannon, I closed the original PR#377 and opened a new one
against a rebased version of the implementation.
--
___
Python tracker <rep...@bugs.python.or
Change by Lele Gaifax <lelegai...@gmail.com>:
--
pull_requests: +4203
___
Python tracker <rep...@bugs.python.org>
<https://bugs.python.org/issue27645>
___
_
Lele Gaifax <lelegai...@gmail.com> added the comment:
Reasonable and quite simple to implement: done in commit
https://github.com/lelit/cpython/commit/960303f9eb394e2ba91d10e5e674997a48811ac2
--
___
Python tracker <rep...@bugs.python.or
Lele Gaifax <lelegai...@gmail.com> added the comment:
I rebased my v2 set of changesets into a new branch:
https://github.com/lelit/cpython/tree/sqlite-backup-api-v3
I really don't know if anybody is interested beyond me, I did everything has
been suggested/requested, and honestly
Lele Gaifax added the comment:
Monthly offer to do whatever is needed to easy the path to adoption :-)
--
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/i
Lele Gaifax added the comment:
Is there any chance this could be accepted for Python 3.7?
--
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/i
Lele Gaifax added the comment:
Thank you Aviv, I applied your suggestions and opened a PR.
--
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/i
Lele Gaifax added the comment:
Now that we are is officially on GH, would you welcome a PR rebasing this patch
on top of the master branch?
--
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/i
Lele Gaifax added the comment:
Yay, Yury is too fast!! :-)
--
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/issue29271>
___
___
Pyth
Lele Gaifax added the comment:
FWIW, the problem afflicts other functions, for example the following script
exhibits a similar difference:
import asyncio
async def coro():
print(asyncio.Task.all_tasks())
print(asyncio.Task.all_tasks(None))
loop = asyncio.get_event_loop
Changes by Lele Gaifax <lelegai...@gmail.com>:
--
nosy: +lelit
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/issue29271>
___
__
Lele Gaifax added the comment:
Ok, thank you.
--
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/issue28830>
___
___
Python-bugs-list
New submission from Lele Gaifax:
At https://hg.python.org/cpython/rev/52038705827d#l1.18 there is an "as part"
where probably a "are part" was meant.
--
assignee: docs@python
components: Documentation
messages: 281977
nosy: docs@python, lelit
priority: normal
sev
New submission from Lele Gaifax:
Python 3.6+ is stricter about escaped sequences in string literals.
The documentation need some improvement to clarify the change: for example
https://docs.python.org/3.6/library/re.html#re.sub first says that “Unknown
escapes such as \& are left a
Lele Gaifax added the comment:
I guess the chance of getting this merged before the 3.6 betas is very low, but
if there is *anything* I could do to raise it, please tell :-)
--
___
Python tracker <rep...@bugs.python.org>
<http://bugs.p
Changes by Lele Gaifax <lelegai...@gmail.com>:
Removed file: http://bugs.python.org/file44083/ac-doc-typos.patch
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python
Lele Gaifax added the comment:
Re-uploaded the patch file, without spurious stuff.
--
Added file: http://bugs.python.org/file44084/ac-doc-typos.patch
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/i
Lele Gaifax added the comment:
Yes, sorry about that, picked the wrong file :-|
I will renew the patch shortly!
--
components: -Documentation
versions: -Python 3.5
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/i
New submission from Lele Gaifax:
The attached patch, available also as
https://github.com/lelit/cpython/commit/9e33f33e87ad594daae71ccdbe6f0a5c5f8aca65,
fixes a few typos in the Argument Clinic howto document.
--
components: Argument Clinic
files: ac-doc-typos.patch
keywords: patch
Lele Gaifax added the comment:
Ok, the agreement is fullfilled.
--
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/issue27645>
___
___
Lele Gaifax added the comment:
WRT to the agreement form, I guess I'll have to compile it even if I already
contributed to Python decades ago (ObjC, readline, NeXT support...), right?
Will try to do whatever is needed in the next days
Lele Gaifax added the comment:
For the documentation see
https://github.com/lelit/cpython/commit/bd82f8de9800ae40b33ddf1e4b7d72f10bc9c10e
or the attached patch.
--
Added file: http://bugs.python.org/file43930/issue27645-doc.patch
___
Python tracker
Changes by Lele Gaifax <lelegai...@gmail.com>:
--
keywords: +patch
Added file: http://bugs.python.org/file43928/issue27645.patch
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python
Lele Gaifax added the comment:
Here is a preliminary implementation:
https://github.com/lelit/cpython/commit/b7456eb6a55568639a41efb5d88ab4d9b3c20337
--
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/i
New submission from Lele Gaifax:
It would be nice if the sqlite3 stdlib module could expose the SQLite Online
Backup API.
I'm willing to implement it, as encouraged by Paul Moore.
See also: https://mail.python.org/pipermail/python-dev/2016-July/145570.html
--
components: Extension
Lele Gaifax added the comment:
I addressed Martin's comments (thank you!) in
https://github.com/lelit/cpython/commits/issue8_2, removing pointless
usage of a macro and avoiding usage of module's state to store the "next line
index", keeping it in a plain static variable.
Let m
Lele Gaifax added the comment:
Daniel, are these misplaced comments, or should your quite big attachments
tell me something I'm missing?
--
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/i
Lele Gaifax added the comment:
In
https://github.com/lelit/cpython/commit/3e5e557a876831a99c21f5a173623cb05ff48abf
I reimplemented the functionality in a slightly different and hopefully better
way, rebasing it on current master.
IANAL, but I think that the new approach is different enough
Lele Gaifax added the comment:
I will try to address your concerns.
--
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/issue8>
___
___
Lele Gaifax added the comment:
The patch does not apply cleanly anymore, with current 3.6a3.
If there is any chance it could be taken into consideration, I will try to
rebase it on top of current version.
@Berker: as I don't use Rietveld, is it possible for me to reach the comment
you
New submission from Lele Gaifax:
Bash implements an handy extension to the history/readline library called
operate-and-get-next bound by default to Ctrl-O that lets you repeat an
arbitrary sequence of input lines possibly editing some of them.
This patch adapts the extension to the Python
New submission from Lele Gaifax:
The documentation of namedtuple, near the end, talks about implementing
enumerated constants and says “Enumerated constants can be implemented with
named tuples, but it is simpler and more efficient to use a simple class
declaration“.
Maybe it should mention
46 matches
Mail list logo