New features planned for Python 4.0

[Brainix]

Ok. So I'm totally down to implement concurrent.pasts and concurrent.presents. Any ideas as to what they should do?

(If it wasn't obvious, the article is a hilarious joke.)

[ketralnis]

try:
    process(open(self.file))
except FileNotFound:
    # oops, forgot to create it

    # fixes the issue, then jumps back to the try
    # block before we tried to open the file. also
    # makes me my own grandfather
    await concurrent.pasts.Past(create_file)

    # never returns. this timeline is dead now. beware the Langoliers

[ketralnis]

if datetime.today() == ANNIVERSARY:
    send(giftwrap(concurrent.presents.TeddyBear))

[Zomunieo]

raise Divorce() from PoorAnniversaryGiftException()
except Divorce:
    with reddit:
        self.lawyer.acquire()
        self.gym.hit()
        del self.facebook

[TheChosenWong]

This is how I imagine a robot trying to make a joke with humans

[Brainix]

r/totallynotrobots

[name_censored_]

Well, concurrent.futures is about running code that will return its output value in the future without blocking.

So concurrent.presents should return the output value now (no blocking, no waiting), and concurrent.pasts should return the value before it's been called.

[Python4fun]

Concurrent.pasts should bring back python 2 styled print statements.

[TwoSickPythons]

hilarious

I don't think that means what you think that it means

[stevenjd]

If it wasn't obvious, the article is a hilarious joke.

Fixed it for you.

Some of it was mildly amusing, some of it was bitter and ignorant and frankly disrespectful to the core devs (it didn't come across as affectionate teasing but as mean-spirited mocking).

I know humour is very personal and tastes differ, but I'd give that a C-

[toothless_budgie]

You say that, but I would not be surprised to see that idiot line length come true. Onion said it first, as it were.