-
-
Notifications
You must be signed in to change notification settings - Fork 405
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Improve documentation in tools submodule #212
Comments
stderr just looks better than sys.stderr.write or print >>sys.stderr, On Mar 18, 2013 11:15 PM, "Edward powell" notifications@github.com wrote:
|
I don't think that's really necessary. Sure it's neater, but it's not used very often and, when it is, it's within the core. Modules certainly shouldn't be printing to stderr, so that should probably be removed from the public-facing API. Certainly, stdout is unnecessary. Other issues in that file:
I don't know what all of this ought to be left until the next major version, since some of these would technically be breaking changes, even if tools was only just made to show up in the html documentation. I also wonder if we should combine tools and web in 4.0, since they're mostly for the same purpose... |
OutputRedirect is used in willie.py, it makes it possible to write stdio.log on linux/posix system, "killing" a process with signal number 0 doesn't do anything, but raises OSError if the process doesn't exist. Google it and check os.kill docs. check_pid is also used in willie.py and there are usecases for using it in modules as well. verify_ssl_cn does exactly what its name says: it verifies a cert cn (common name) to see if it matches, ie. if you try to connect to google.com you'd want the cn to be google.com and not maliciouswebsite.org. This is a security mechanism and modules that require secure connection might want to use it in the future to make sure there was no man-in-the-middle attack or DNS poisoning Ddict is a simple helper to create multi-dimensional dicts. |
For example, stderr is just documented "print to stderr". I'm not sure whether that function should be publicly visible, either. Many of these I think are things @elad661 wrote, so maybe he could help out with this.
The text was updated successfully, but these errors were encountered: