This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Title: Coconut support
Type: enhancement Stage: resolved
Components: Versions: Python 3.8
Status: closed Resolution: postponed
Dependencies: Superseder:
Assigned To: Nosy List: Solomon Ucko, benjamin.peterson, brett.cannon, steven.daprano, yselivanov
Priority: normal Keywords:

Created on 2018-12-24 03:53 by Solomon Ucko, last changed 2022-04-11 14:59 by admin. This issue is now closed.

Messages (3)
msg332402 - (view) Author: Solomon Ucko (Solomon Ucko) Date: 2018-12-24 03:53
Any chance we could integrate [Coconut]( into Python? Any sain Python code should work with Coconut and Coconut allows making code *so* much more readable.

IMO, the reason not many people use Coconut is that they haven't heard of it and because of its lack of IDE support. (I would use it if it had more IDE support than just syntax highlighting.) The reason it has so little IDE support is that not many people use it. Making it a part of Python would alleviate these concerns.
msg332414 - (view) Author: Steven D'Aprano (steven.daprano) * (Python committer) Date: 2018-12-24 06:03
Do you have agreement from the maintainer(s) of Coconut that they are willing to put Coconut into the Python language and/or std library?

Given that Coconut is effectively a radically different language from Python (a superset of Python) this is not a small change. While it is at least possible that we would consider individual features from Coconut, integrating the two languages is unlikely. That would basically turn Python into Coconut and make Python obsolete.

In any case, as a radical change, possibly as big as the move from Python 2 to 3, this will absolutely need a PEP.

You say:

"Coconut allows making code *so* much more readable."

but that's your opinion, I'm sure that there are many people who don't like or appreciate the sort of functional idioms which Coconut specializes in.

But having said that, I personally do like *some* of the Coconut syntax. I think a more productive approach will be to propose *individual* enhancements, allowing each enhancement to be considered on its own merits, rather than suggesting the two languages be integrated. That sort of "everything or nothing" approach is almost certainly going to get the response "OK, nothing".

As for the IDE support, that's not our problem. We're not responsible for convincing IDEs to provide better support for every experimental third-party language.
msg332416 - (view) Author: Steven D'Aprano (steven.daprano) * (Python committer) Date: 2018-12-24 06:09
One more thing: if you intend to proceed with this, either as individual enhancements or a PEP, you should discuss them on the Python-Ideas mailing list first, to see how much or little community support the proposals have.

Until then, I'm closing this as "Postponed".
Date User Action Args
2022-04-11 14:59:09adminsetgithub: 79755
2018-12-24 06:09:39steven.dapranosetstatus: open -> closed
resolution: postponed
messages: + msg332416

stage: resolved
2018-12-24 06:03:32steven.dapranosetnosy: + steven.daprano
messages: + msg332414
2018-12-24 03:53:26Solomon Uckocreate