Hi Brett,
I've got a few questions about the specific design. Probably you know the
answers, it would be nice to have them in the PEP.
First, why not have a global hook? What does a hook per interpreter give
you? Would even finer granularity buy anything?
Next, I'm a bit (but no more than a bit)
I've sent my patch to issue tracker, since I can't fix some remains
TODOs by myself.
http://bugs.python.org/issue27350
On Fri, Jun 17, 2016 at 6:15 PM, INADA Naoki wrote:
> Hi, developers.
>
> I'm trying to implement compact dict.
> https://github.com/methane/cpython/pull/1
>
> Current status is
On Sat, Jun 18, 2016 at 11:32:52PM +0100, Obiesie ike-nwosu via Python-Dev
wrote:
> That is much clearer now.
> Thanks a lot Raymond for taking the time out to explain this to me.
> On a closing note, is this mailing list the right place to ask these kinds
> of n00b questions?
That depends wha
On Sat, Jun 18, 2016 at 6:17 PM, Brett Cannon wrote:
> Over on the "security SIG" thread, the point has been made that we seem to
> be hitting some limits in communication (Steve Dower said written
> communication, Guido said mailing lists/newsgroups). Based on the burnout
> we are seeing from th
Over on the "security SIG" thread, the point has been made that we seem to
be hitting some limits in communication (Steve Dower said written
communication, Guido said mailing lists/newsgroups). Based on the burnout
we are seeing from these centi-threads we need to try and come up with some
solution
Like it or not, written communication is all we have. However, I do think
we are running into some kind of limitation: the ancient concept of mailing
lists (or newsgroups). I would like to continue the discussion of this
limitation in the original thread.
PS. I think it's somewhat ironic that Stev
That is much clearer now.
Thanks a lot Raymond for taking the time out to explain this to me.
On a closing note, is this mailing list the right place to ask these kinds of
n00b questions?
Obi.
> On 18 Jun 2016, at 23:10, Raymond Hettinger
> wrote:
>
>
>> On Jun 18, 2016, at 2:04 PM, Obiesie
It's not just security discussions. The same thing happened with fspath,
tzinfo, and many others that I have erased from my own memory. distutils-sig
sees them often as well.
The whole thing seems like a limitation of written communication. There's no
way to indicate or define whether something
On Jun 18, 2016, at 03:30 PM, Cory Benfield wrote:
>Unless that SIG is empowered to take action
It wouldn't be, but there *is* a private security mailing list that is.
Christian was on it, and I'm sad that he got burned out. If you are willing
and able to help out there, please contact security
> On Jun 18, 2016, at 2:04 PM, Obiesie ike-nwosu via Python-Dev
> wrote:
>
> Hi,
>
> Could some one give a hand with explaining to me why we have a JUMP_ABSOLUTE
> followed by a JUMP_FORWARD op code when this function is disassembled.
> < snipped>
> From my understanding, once JUMP_ABSOLUTE
Python has a peephole optimizer which does not remove dead code that it
just created.
Victor
Le 18 juin 2016 23:14, "Obiesie ike-nwosu via Python-Dev" <
python-dev@python.org> a écrit :
> Hi,
>
> Could some one give a hand with explaining to me why we have a
> JUMP_ABSOLUTE followed by a JUMP_FOR
Hi,
Could some one give a hand with explaining to me why we have a JUMP_ABSOLUTE
followed by a JUMP_FORWARD op code when this function is disassembled.
>>> def f1():
... a, b = 10, 11
... if a >= 10:
... if b >= 11:
... print("hello world")
…
The disass
> On Jun 18, 2016, at 9:57 AM, Franklin Lee wrote:
>
> In the original discussion, I think they decided to reimplement set before
> dict.
I ended-up going in a different direction with sets (using linear probes to
reduce the cost of collisions). Also, after the original discussion, PyPy
imp
On Sat, 18 Jun 2016 at 07:30 Cory Benfield wrote:
>
> > On 18 Jun 2016, at 04:06, Brett Cannon wrote:
> >
> > Do we need a security SIG? E.g. would people like Christian and Cory
> like to have a separate place to talk about the ssl stuff brought up at the
> language summit?
>
>
> Honestly, I’m
>
> Ordered, or just initially ordered? I mean, "ordered if no deletion".
>
I implemented "ordered". Because:
* "orderd" is easier to explain than "ordered if no deletion".
* I don't want to split sparse index hash and dense entry array.
In case of very small dict, index hash (8byte) and firs
On 06/18/2016 07:30 AM, Cory Benfield wrote:
On 18 Jun 2016, at 04:06, Brett Cannon wrote:
Do we need a security SIG? E.g. would people like Christian and Cory like
>> to have a separate place to talk about the ssl stuff brought up at the
>> language summit?
Honestly, I’m not sure what we w
>
> pybench: https://gist.github.com/methane/cfad1427d87ceff9310350e78a214880
> benchmark: https://gist.github.com/methane/5eb11fdd93863813b222e795ca0bfc1f
>
> Is it acceptable?
latest result is here
https://gist.github.com/methane/22cf5d1dadb62bc87a15e9244a9d0ab8
--
INADA Naoki
__
In the original discussion, I think they decided to reimplement set before
dict.
The original discussion is here, for anyone else:
https://mail.python.org/pipermail/python-dev/2012-December/123028.html
On Jun 18, 2016 3:15 AM, "INADA Naoki" wrote:
> If builtin dict in both of PyPy and CPython is
> On 18 Jun 2016, at 04:06, Brett Cannon wrote:
>
> Do we need a security SIG? E.g. would people like Christian and Cory like to
> have a separate place to talk about the ssl stuff brought up at the language
> summit?
Honestly, I’m not sure what we would gain.
Unless that SIG is empowered t
> On 18 Jun 2016, at 11:38, Stephen J. Turnbull wrote:
>
> I see the security issue as a backyard swimming pool. The law may say
> you must put a fence around it, but even 6 year olds can climb the
> fence, fall in the pool, and drown. The hard-line security advocate
> position then is "the ri
Brett Cannon writes:
> Do we need a security SIG? E.g. would people like Christian and
> Cory like to have a separate place to talk about the ssl stuff
> brought up at the language summit?
Besides what Barry brought up about the potential for attractive
nuisance where people post security issu
Now I fixed failing tests (some tests relying to underlying layout).
Before posting it to bugs.python.org, I want to confirm I have chance to
it merged.
First big problem is language spec.
If builtin dict in both of PyPy and CPython is ordered, many people
will relying it.
It will force other P
22 matches
Mail list logo
