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.

Author denilsonsa
Recipients denilsonsa, pitrou, zbysz
Date 2011-12-16.11:28:36
SpamBayes Score 0.00081545056
Marked as misclassified No
Message-id <>
Zbyszek, I just looked at [1] and I disagree that the environment variable should have higher precedence. In fact, I believe it should have lower precedence, and should be used as a fallback.


Reason? Imagine a program is launched, and thus it has COLUMNS set to some value. While the program is running, the user resizes the terminal. I believe (though I have not tested) that the envvar will keep the old value, and this function would return wrong dimensions.

In my opinion, the system-specific code (termios/windll) should be tried first, and then the envvars (as fallback). If all else fails, maybe it would be better to return (None, None) and let the caller of this function handle that.
Date User Action Args
2011-12-16 11:28:37denilsonsasetrecipients: + denilsonsa, pitrou, zbysz
2011-12-16 11:28:37denilsonsasetmessageid: <>
2011-12-16 11:28:36denilsonsalinkissue13609 messages
2011-12-16 11:28:36denilsonsacreate