➜
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.
Created on 2021-09-15 10:01 by Crowthebird, last changed 2022-04-11 14:59 by admin. This issue is now closed.
| Pull Requests | |||
|---|---|---|---|
| URL | Status | Linked | Edit |
| PR 28349 | closed | Crowthebird, 2021-09-15 10:03 | |
| Messages (8) | |||
|---|---|---|---|
| msg401822 - (view) | Author: Jeremiah Gabriel Pascual (Crowthebird) * | Date: 2021-09-15 10:01 | |
Add a flag named 'CO_FUTURE_REVOLT_AND_REMOVE_BARRY_FROM_BDFL' assigned to `0x2000000` that can be activated with 'from __future__ import remove_barry_from_BDFL'. Reverts the effects of 'from __future__ import barry_as_FLUFL' and adds the 'CO_FUTURE_REVOLT_AND_REMOVE_BARRY_FROM_BDFL' flag in indication that Barry has been overthrown from his position. Doing this before a 'from __future__ import barry_as_FLUFL' import will have no effect whatsoever. Redoing 'from __future__ import barry_as_FLUFL' will remove the flag and re-add the 'CO_FUTURE_BARRY_AS_BDFL' flag. There can be optional messages informing users of the change. |
|||
| msg401828 - (view) | Author: STINNER Victor (vstinner) *  |
Date: 2021-09-15 13:11 | |
'from __future__ import barry_as_FLUFL' is an easter egg. I don't see the point of 'from __future__ import remove_barry_from_BDFL'. |
|||
| msg401829 - (view) | Author: Jeremiah Gabriel Pascual (Crowthebird) * | Date: 2021-09-15 13:15 | |
Reverting the effects of 'from __future__ import barry_as_FLUFL' without exiting the compiler. |
|||
| msg401830 - (view) | Author: Jeremiah Gabriel Pascual (Crowthebird) * | Date: 2021-09-15 13:15 | |
*interpreter. |
|||
| msg401840 - (view) | Author: Serhiy Storchaka (serhiy.storchaka) * |
Date: 2021-09-15 14:01 | |
But why do you need to execute 'from __future__ import barry_as_FLUFL' in your interpreter at first place? Don't do this and you would not need to revert its effect. |
|||
| msg401843 - (view) | Author: Barry A. Warsaw (barry) * |
Date: 2021-09-15 15:03 | |
This bug made my day! :-D |
|||
| msg401845 - (view) | Author: Pablo Galindo Salgado (pablogsal) * |
Date: 2021-09-15 15:54 | |
I think this adds too much complexity for an Easter egg. The compiler flags have been proven to be quite brittle (see past bugs regarding them) so I don't want to add new ones of we can avoid it |
|||
| msg401858 - (view) | Author: Eric V. Smith (eric.smith) * |
Date: 2021-09-15 17:05 | |
I agree this should be rejected due to pointlessness and complexity. I'll give my usual advice: if you really want to see this happen, I suggest opening a discussion on the python-ideas mailing list. Then if there's consensus to go ahead, this issue can be re-opened. |
|||
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2022-04-11 14:59:50 | admin | set | github: 89365 |
| 2021-09-15 17:05:34 | eric.smith | set | status: open -> closed nosy: + eric.smith messages: + msg401858 resolution: rejected stage: patch review -> resolved |
| 2021-09-15 15:54:00 | pablogsal | set | messages: + msg401845 |
| 2021-09-15 15:03:31 | barry | set | nosy:
barry, vstinner, serhiy.storchaka, lys.nikolaou, pablogsal, Crowthebird messages: + msg401843 |
| 2021-09-15 14:01:44 | serhiy.storchaka | set | messages: + msg401840 |
| 2021-09-15 13:15:27 | Crowthebird | set | messages: + msg401830 |
| 2021-09-15 13:15:16 | Crowthebird | set | messages: + msg401829 |
| 2021-09-15 13:11:43 | vstinner | set | nosy:
+ barry, serhiy.storchaka, vstinner messages: + msg401828 |
| 2021-09-15 12:49:41 | Crowthebird | set | nosy:
+ pablogsal, lys.nikolaou components: + Interpreter Core, Parser |
| 2021-09-15 11:14:22 | Crowthebird | set | versions: - Python 3.10 |
| 2021-09-15 11:14:17 | Crowthebird | set | versions: + Python 3.10 |
| 2021-09-15 10:03:02 | Crowthebird | set | keywords:
+ patch stage: patch review pull_requests: + pull_request26762 |
| 2021-09-15 10:01:52 | Crowthebird | create | |