Mailing List Archive

neoPython : Fastest Python Implementation: Coming Soon
neoPython : Fastest Python Implementation: Coming Soon

Message ends.

/Flibble

--
????
--
https://mail.python.org/mailman/listinfo/python-list
Re: neoPython : Fastest Python Implementation: Coming Soon [ In reply to ]
On Thu, May 6, 2021 at 2:01 AM Mr Flibble
<flibble@i42.invalidwibblegrok.co.uk> wrote:
>
> neoPython : Fastest Python Implementation: Coming Soon
>
> Message ends.
>
> /Flibble
>

My breath: not being held.

Message ends.

ChrisA
--
https://mail.python.org/mailman/listinfo/python-list
Re: neoPython : Fastest Python Implementation: Coming Soon [ In reply to ]
On 05/05/2021 17:02, Chris Angelico wrote:
> On Thu, May 6, 2021 at 2:01 AM Mr Flibble
> <flibble@i42.invalidwibblegrok.co.uk> wrote:
>>
>> neoPython : Fastest Python Implementation: Coming Soon
>>
>> Message ends.
>>
>> /Flibble
>>
>
> My breath: not being held.
>
> Message ends.

Why? The currently extant Python implementations contribute to climate change as
they are so inefficient; CPython is so egregious it is best called a bag of
shite. Making a faster implementation isn't in the least bit a stretch.

Message ends.

/Flibble

--
????
--
https://mail.python.org/mailman/listinfo/python-list
Re: neoPython : Fastest Python Implementation: Coming Soon [ In reply to ]
On 05/05/2021 17:02, Chris Angelico wrote:
> On Thu, May 6, 2021 at 2:01 AM Mr Flibble
> <flibble@i42.invalidwibblegrok.co.uk> wrote:
>>
>> neoPython : Fastest Python Implementation: Coming Soon
>>
>> Message ends.
>>
>> /Flibble
>>
>
> My breath: not being held.
>
> Message ends.

Why? The currently extant Python implementations are so inefficient they
contribute to climate change; CPython is particularly egregious. Making a faster
implementation isn't in the least bit a stretch.

Message ends.

/Flibble

--
????
--
https://mail.python.org/mailman/listinfo/python-list
Re: neoPython : Fastest Python Implementation: Coming Soon [ In reply to ]
Hi,

On Wed, May 5, 2021 at 11:27 AM Mr Flibble <
flibble@i42.invalidwibblegrok.co.uk> wrote:

> On 05/05/2021 17:02, Chris Angelico wrote:
> > On Thu, May 6, 2021 at 2:01 AM Mr Flibble
> > <flibble@i42.invalidwibblegrok.co.uk> wrote:
> >>
> >> neoPython : Fastest Python Implementation: Coming Soon
> >>
> >> Message ends.
> >>
> >> /Flibble
> >>
> >
> > My breath: not being held.
> >
> > Message ends.
>
> Why? The currently extant Python implementations are so inefficient they
> contribute to climate change; CPython is particularly egregious. Making a
> faster
> implementation isn't in the least bit a stretch.
>
> Message ends.
>

Why do you use {C}Python in the first place if its so inefficient?
Why not use C or even Assembly?

And "coming soon" - is a little weird.
Why not say "coming 10 May 2021 at 23:59:59"?

/Message ends.

Thank you.


> /Flibble
>
> --
> ????
> --
> https://mail.python.org/mailman/listinfo/python-list
>
--
https://mail.python.org/mailman/listinfo/python-list
Re: neoPython : Fastest Python Implementation: Coming Soon [ In reply to ]
On 05/05/2021 17:33, Mark Lawrence wrote:
> On Wednesday, May 5, 2021 at 4:57:13 PM UTC+1, Mr Flibble wrote:
>> neoPython : Fastest Python Implementation: Coming Soon
>>
>> Message ends.
>>
>> /Flibble
>>
>> --
>> ????
> Dedicated to you and all like you https://www.youtube.com/watch?v=X15PsqN0DHc

ORLY? If anyone is thick around here it is the typical Python user such as yourself.

/Flibble

--
????
--
https://mail.python.org/mailman/listinfo/python-list
Re: neoPython : Fastest Python Implementation: Coming Soon [ In reply to ]
On 05/05/2021 17:36, Igor Korot wrote:
> Hi,
>
> On Wed, May 5, 2021 at 11:27 AM Mr Flibble <
> flibble@i42.invalidwibblegrok.co.uk> wrote:
>
>> On 05/05/2021 17:02, Chris Angelico wrote:
>>> On Thu, May 6, 2021 at 2:01 AM Mr Flibble
>>> <flibble@i42.invalidwibblegrok.co.uk> wrote:
>>>>
>>>> neoPython : Fastest Python Implementation: Coming Soon
>>>>
>>>> Message ends.
>>>>
>>>> /Flibble
>>>>
>>>
>>> My breath: not being held.
>>>
>>> Message ends.
>>
>> Why? The currently extant Python implementations are so inefficient they
>> contribute to climate change; CPython is particularly egregious. Making a
>> faster
>> implementation isn't in the least bit a stretch.
>>
>> Message ends.
>>
>
> Why do you use {C}Python in the first place if its so inefficient?
> Why not use C or even Assembly?
>
> And "coming soon" - is a little weird.
> Why not say "coming 10 May 2021 at 23:59:59"?
>
> /Message ends.
>
> Thank you.

But I don't use Python, I use C++ (probably the best programming language in the
world).

/Flibble

--
????
--
https://mail.python.org/mailman/listinfo/python-list
Re: neoPython : Fastest Python Implementation: Coming Soon [ In reply to ]
Hi,

On Wed, May 5, 2021 at 11:47 AM Mr Flibble <
flibble@i42.invalidwibblegrok.co.uk> wrote:

> On 05/05/2021 17:36, Igor Korot wrote:
> > Hi,
> >
> > On Wed, May 5, 2021 at 11:27 AM Mr Flibble <
> > flibble@i42.invalidwibblegrok.co.uk> wrote:
> >
> >> On 05/05/2021 17:02, Chris Angelico wrote:
> >>> On Thu, May 6, 2021 at 2:01 AM Mr Flibble
> >>> <flibble@i42.invalidwibblegrok.co.uk> wrote:
> >>>>
> >>>> neoPython : Fastest Python Implementation: Coming Soon
> >>>>
> >>>> Message ends.
> >>>>
> >>>> /Flibble
> >>>>
> >>>
> >>> My breath: not being held.
> >>>
> >>> Message ends.
> >>
> >> Why? The currently extant Python implementations are so inefficient they
> >> contribute to climate change; CPython is particularly egregious. Making
> a
> >> faster
> >> implementation isn't in the least bit a stretch.
> >>
> >> Message ends.
> >>
> >
> > Why do you use {C}Python in the first place if its so inefficient?
> > Why not use C or even Assembly?
> >
> > And "coming soon" - is a little weird.
> > Why not say "coming 10 May 2021 at 23:59:59"?
> >
> > /Message ends.
> >
> > Thank you.
>
> But I don't use Python, I use C++ (probably the best programming language
> in the
> world).
>

Posting in the python community implies that you are using {c}python.
Otherwise you will not be posting here.
And definitely would be waiting until you can show the "best python
implementation ever".

And C++ is also bad - Assembly is so much better and so much more efficient.

/Message ends.

Thank you.


> /Flibble
>
> --
> ????
> --
> https://mail.python.org/mailman/listinfo/python-list
>
--
https://mail.python.org/mailman/listinfo/python-list
Re: neoPython : Fastest Python Implementation: Coming Soon [ In reply to ]
> Why? The currently extant Python implementations contribute to climate change as they are so inefficient;

That same argument can be made for every triple-AAA video game, game console, etc.

Python is more efficient for some problem sets, and Python is less efficient for other problem sets.

Please feel free to come out with NeoPython. When you are done, and it is backward compatible with existing Python code, I’ll be happy to benchmark it against Native python. But don’t blame Python for global climate change. There are plenty of bigger “causations” to Global climate change, then a freakin’ computer programming language.

- Benjamin


--
https://mail.python.org/mailman/listinfo/python-list
Re: neoPython : Fastest Python Implementation: Coming Soon [ In reply to ]
I wish you best of luck, on top of everything else it looks like the
neopython namespace has already been eaten up by some crypto project

On Wed, May 5, 2021 at 11:18 AM Benjamin Schollnick <
bschollnick@schollnick.net> wrote:

> > Why? The currently extant Python implementations contribute to climate
> change as they are so inefficient;
>
> That same argument can be made for every triple-AAA video game, game
> console, etc.
>
> Python is more efficient for some problem sets, and Python is less
> efficient for other problem sets.
>
> Please feel free to come out with NeoPython. When you are done, and it is
> backward compatible with existing Python code, I’ll be happy to benchmark
> it against Native python. But don’t blame Python for global climate
> change. There are plenty of bigger “causations” to Global climate change,
> then a freakin’ computer programming language.
>
> - Benjamin
>
>
> --
> https://mail.python.org/mailman/listinfo/python-list
>
--
https://mail.python.org/mailman/listinfo/python-list
RE: neoPython : Fastest Python Implementation: Coming Soon [ In reply to ]
Chris,

I got the fastest python yesterday as it was so fast that it beat the one
coming tomorrow.

The trick is adding back the legs that evolution allowed to lapse.

Without bated breath,

Regardless,

Avi

-----Original Message-----
From: Python-list <python-list-bounces+avigross=verizon.net@python.org> On
Behalf Of Chris Angelico
Sent: Wednesday, May 5, 2021 12:02 PM
To: Python <python-list@python.org>
Subject: Re: neoPython : Fastest Python Implementation: Coming Soon

On Thu, May 6, 2021 at 2:01 AM Mr Flibble
<flibble@i42.invalidwibblegrok.co.uk> wrote:
>
> neoPython : Fastest Python Implementation: Coming Soon
>
> Message ends.
>
> /Flibble
>

My breath: not being held.

Message ends.

ChrisA
--
https://mail.python.org/mailman/listinfo/python-list

--
https://mail.python.org/mailman/listinfo/python-list
RE: neoPython : Fastest Python Implementation: Coming Soon [ In reply to ]
"Slow" is in the eye of the beholder and depends on the job the needs to be done. Where I work, we write scripts in Python that control our measuring instruments, make them acquire data and compute results, the Python script reads the results, compares results to limits, and eventually produces a lovely report.

In some scripts, we make the instrument acquire and save data and our Python script launches another program on the instrument that will read in the data and perform specified analysis. That program can take a couple of minutes to complete. If we have to do this for multiple runs we launch them at the same time and they finish at the same time, the time of one run. So we are doing easy multiprocessing using Python.

Now let's consider, if our controlling Python script were instead written in a highly optimized blazingly fast compiled language, how much faster could this script be? It would still have to wait for the instrument to compute results; if running a separate analysis program it would still have to launch it (perhaps several of them) and wait for until they finished. I doubt the compiled script would finish even a second faster.

I think this kind of application is just perfect for Python. We considered other (commercially supported) languages before we went with Python. I'm very happy that we did. We can find people who want to program in Python and already know Python. I haven't yet seen an employee complaint about our scripts being written in Python, and I don't expect to.

-- Joseph S.


Teledyne Confidential; Commercially Sensitive Business Data
--
https://mail.python.org/mailman/listinfo/python-list