On 3/11/2019 10:54 PM, Inada Naoki wrote:
Hello,
some time ago I contributed a couple of patches to speedup shutil.copy*()
functions:
https://bugs.python.org/issue33671
https://bugs.python.org/issue33695
You retain copyright on the code you contributed.
I would like to backport both
On Tue, Mar 12, 2019 at 8:38 AM Giampaolo Rodola' wrote:
>
> Hello,
> some time ago I contributed a couple of patches to speedup shutil.copy*()
> functions:
> https://bugs.python.org/issue33671
> https://bugs.python.org/issue33695
> I would like to backport both functionalities so that they can
Things in the standard library are already covered by the PSF license so
that is what should be kept on backports from the stdlib to earlier
versions.
I do recommend keeping your backported stuff and new functionality separate
(separate packages ideally, but that'll depend on how intertwined
On 3/11/2019 4:35 PM, Giampaolo Rodola' wrote:
Hello,
some time ago I contributed a couple of patches to speedup
shutil.copy*() functions:
https://bugs.python.org/issue33671
https://bugs.python.org/issue33695
I would like to backport both functionalities so that they can be used
on Python 2.7
Hello,
some time ago I contributed a couple of patches to speedup shutil.copy*()
functions:
https://bugs.python.org/issue33671
https://bugs.python.org/issue33695
I would like to backport both functionalities so that they can be used on
Python 2.7 and <3.8 and put it on PYPI. In order to do so I
Parrot got rather further along than rattlesnake as a register based VM. I
don't think it every really beat CPython in speed though.
http://parrot.org/
On Mon, Mar 11, 2019, 5:57 PM Neil Schemenauer
wrote:
> On 2019-02-27, Victor Stinner wrote:
> > The compiler begins with using static single
On 2019-02-27, Victor Stinner wrote:
> The compiler begins with using static single assignment form (SSA) but
> then uses a register allocator to reduce the number of used registers.
> Usually, at the end you have less than 5 registers for a whole
> function.
In case anyone is interested on
I don't think that a thread about a release is the right place to discuss a
bug. Please open an issue at bugs.python.org
Victor
Le lundi 11 mars 2019, Joni Orponen a écrit :
> On Sun, Mar 10, 2019 at 7:50 AM Larry Hastings wrote:
>>
>> On 3/4/19 2:29 AM, Joni Orponen wrote:
>>
>> On Sat, Mar
On Tue, Feb 26, 2019 at 10:40:56PM -0800, Denton Liu wrote:
> On Tue, Feb 12, 2019 at 02:14:55AM -0800, Denton Liu wrote:
> > Hello all,
> >
> > A couple months back, I reported bpo-35155[1] and I submitted a PR for
> > consideration[2]. After a couple of reviews, it seems like progress has
> >
Hi folks,
Brett recently posted about the update to PEP 1 that added the PEP Sponsor
role, but folks may not have noticed that we've also made the amendments
needed to allow the PEP decision making process to restart:
https://github.com/python/peps/pull/896/files
This is the smallest change to
On Sun, Mar 10, 2019 at 7:50 AM Larry Hastings wrote:
> On 3/4/19 2:29 AM, Joni Orponen wrote:
>
> On Sat, Mar 2, 2019 at 7:08 AM Larry Hastings wrote:
>
>> This bug in bpo-33329:
>>
>> https://bugs.python.org/issue33329
>>
>>
>> This is also potentially affecting PGO builds of 2.7 on Debian
11 matches
Mail list logo
