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 sbt
Recipients noxdafox, sbt
Date 2013-10-07.10:32:58
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1381141979.01.0.783752722289.issue19185@psf.upfronthosting.co.za>
In-reply-to
Content
I think "misuse" is an exageration.  Various functions change some state and return a value that is usually ignored, e.g. os.umask(), signal.signal().

> Global variables usage is a pattern which might lead to code errors and many 
> developers discourage from following it.

What sort of code errors?  This really seems a stylistic point.  Maybe such developers would be happier using class methods and class variables rather than functions and globals variables.

Out of interest, what do you usually do in your initializer functions?
History
Date User Action Args
2013-10-07 10:32:59sbtsetrecipients: + sbt, noxdafox
2013-10-07 10:32:59sbtsetmessageid: <1381141979.01.0.783752722289.issue19185@psf.upfronthosting.co.za>
2013-10-07 10:32:58sbtlinkissue19185 messages
2013-10-07 10:32:58sbtcreate