[issue45202] Add 'remove_barry_from_BDFL' future to revert effects of 'from __future__ import barry_as_FLUFL'

Eric V. Smith added the comment: 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

[issue45202] Add 'remove_barry_from_BDFL' future to revert effects of 'from __future__ import barry_as_FLUFL'

Pablo Galindo Salgado added the comment: 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 -- ___

[issue45202] Add 'remove_barry_from_BDFL' future to revert effects of 'from __future__ import barry_as_FLUFL'

Barry A. Warsaw added the comment: This bug made my day! :-D -- ___ Python tracker ___ ___ Python-bugs-list mailing list

[issue45202] Add 'remove_barry_from_BDFL' future to revert effects of 'from __future__ import barry_as_FLUFL'

Serhiy Storchaka added the comment: 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. -- ___ Python tracker

[issue45202] Add 'remove_barry_from_BDFL' future to revert effects of 'from __future__ import barry_as_FLUFL'

theeshallnotknowethme added the comment: *interpreter. -- ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue45202] Add 'remove_barry_from_BDFL' future to revert effects of 'from __future__ import barry_as_FLUFL'

theeshallnotknowethme added the comment: Reverting the effects of 'from __future__ import barry_as_FLUFL' without exiting the compiler. -- ___ Python tracker ___

[issue45202] Add 'remove_barry_from_BDFL' future to revert effects of 'from __future__ import barry_as_FLUFL'

STINNER Victor added the comment: 'from __future__ import barry_as_FLUFL' is an easter egg. I don't see the point of 'from __future__ import remove_barry_from_BDFL'. -- nosy: +barry, serhiy.storchaka, vstinner ___ Python tracker

[issue45202] Add 'remove_barry_from_BDFL' future to revert effects of 'from __future__ import barry_as_FLUFL'

Change by theeshallnotknowethme : -- components: +Interpreter Core, Parser nosy: +lys.nikolaou, pablogsal ___ Python tracker ___

[issue45202] Add 'remove_barry_from_BDFL' future to revert effects of 'from __future__ import barry_as_FLUFL'

Change by theeshallnotknowethme : -- versions: -Python 3.10 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue45202] Add 'remove_barry_from_BDFL' future to revert effects of 'from __future__ import barry_as_FLUFL'

Change by theeshallnotknowethme : -- versions: +Python 3.10 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue45202] Add 'remove_barry_from_BDFL' future to revert effects of 'from __future__ import barry_as_FLUFL'

Change by theeshallnotknowethme : -- keywords: +patch pull_requests: +26762 stage: -> patch review pull_request: https://github.com/python/cpython/pull/28349 ___ Python tracker

[issue45202] Add 'remove_barry_from_BDFL' future to revert effects of 'from __future__ import barry_as_FLUFL'

New submission from theeshallnotknowethme : Add a flag named 'CO_FUTURE_REVOLT_AND_REMOVE_BARRY_FROM_BDFL' assigned to `0x200` 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