On Tue, Mar 23, 2021 at 12:40 PM Skip Montanaro
wrote:
> I've not attempted to make any changes to calling conventions. It
> occurred to me that the LOAD_METHOD/CALL_METHOD pair could perhaps be
> merged into a single opcode, but I haven't really thought about that.
> Perhaps there's a good
On 24/03/21 7:47 am, Chris Angelico wrote:
On Wed, Mar 24, 2021 at 5:35 AM Vijay Patel wrote:
>
Suggestion:
1. Big Set, Big Dictionary -
>
How would it be stored on disk? Would it be in some sort of database?
If so, check out a database access module
Also remember that virtual memory is a
> > So, neither "research" nor "production" seems to be a correct
> > descriptor.
>
> Not even government funding agencies distinguish between "research"
> and "itch-scratching" as long as you self-promote enough! :-) I agree
> with Paul, feel free to call it "research"!
Along similar lines,
> a) You're working with CPython bleeding edge.
> b) You find that (bleeding edge) adding extra chore.
> c) Nobody told you to work on bleeding (nor boss, nor a maintainer who
> said "I'll merge it once you've done"),
>
> Then: why do you complicate your task by working on bleeding edge?
> Could
23.03.21 07:55, Vijay Patel пише:
> Suggestion:
> 1. Big Set, Big Dictionary -
> During design time, i am considering this question. With limited RAM
> (example 4 GB), how can I store a dictionary/set of size greater than RAM.
>
> Is it possible to introduce Big Set / Big Dictionary which stores
On Wed, Mar 24, 2021 at 5:35 AM Vijay Patel wrote:
>
> Hi,
>
> (This is great language, sincere thanks to all!)
>
> I took a quick glance of https://devguide.python.org/langchanges/ (20.3.
> Suggesting new features and language changes), while writing this post.
>
> Please ignore this, if
Hi,
(This is great language, sincere thanks to all!)
I took a quick glance of https://devguide.python.org/langchanges/ (20.3.
Suggesting new features and language changes), while writing this post.
Please ignore this, if similar proposals are discussed earlier.
Suggestion:
1. Big Set, Big
Skip Montanaro writes:
> So, neither "research" nor "production" seems to be a correct
> descriptor.
Not even government funding agencies distinguish between "research"
and "itch-scratching" as long as you self-promote enough! :-) I agree
with Paul, feel free to call it "research"!
Steve
Hi Skip, thanks for the proto-PEP which makes for an interesting reading.
While reading the PEP, I had these questions:
1) I understand the goal is to make CPython faster. But this is not stated
explicitly. Is there a way to make this more explicit in the beginning, and
also how this would be
Hello Skip,
On Mon, 22 Mar 2021 17:13:19 -0500
Skip Montanaro wrote:
> Thanks for the response. I will try to address your comments inline.
>
> > I guess it should be a good idea to answer what's the scope of this
> > project - is it research one or "production" one? If it's research
> > one,
10 matches
Mail list logo
