Hello, I would like to consult related issues encountered when reading the python language reference manual,
I am at this URL https://docs.python.org/zh-cn/3/bugs.html
Seeing the email address, I wonder if it can be used to consult such questions? Or please recommend a channel for consultation.
"Python Language Reference Manual"-Data Model Chapter-Static Method Object:
"Avoid converting function objects into method objects" refers to avoiding the methods defined in the class (ie: function objects) from being converted into instance methods when the instance object gets properties?
Why is it set up in python to encapsulate user-defined functions in a class to prevent them from being converted into instance methods? In what situations is this encapsulation generally used?
I wish to bring to your kind notice a bug in Python.
Given any matrix X. While trying to compute the CoVariance matrix of that
matrix X, Python does NOT compute the CoVarianceof the given matrix X.
Instead, Python comptes the CoVariance of the Transpose of the given matrix
This appears to be a bug in Python.
Please refer to the below website for a given matrix and what the result
should be after the computation of it's CoVariance. And I have provided a
screenshot of what Python is returning.
Please let me know if you have any questions.
In section 6.4 of the tutorial:
Yet another variation is to import the desired function or variable directly:
Again, this loads the submodule echo, but this makes its function echofilter() directly available
I think the last sentence of the describtion should be:
Again, this doesn't load the submodule echo, but this makes its function echofilter() directly available
Thanks and Best Regards,
I was going through the "Logging Cookbook" article, following perfectly...
until the section entitled "Dealing with handlers that block" attributed to
writer Vinay Sajip <vinay_sajip at red-dove dot com>.
I skimmed his discussion and figured that I could look at the code to
figure out which imports that he did not include in the code because
everything was making perfect sense.
Apparently one of the imports required was the code snippet for a module
recently above... yet there is no link in the doc to take me to a simple
article explaining how to take a module code and create a import module in
Thus, the Logging Cookbook became immediately IRRELEVANT in being a
reference article without having experience or knowledge in creating Python
Yes, I am working on a complex project for myself. and am ramping up as
quickly as I can, yet with a total of about 3 years managing python scripts
similar to DOS BAT files, I have no experience creating importable modules
Doing this complex project, I plan on designing MANY custom personal import
modules for myself, yet that has not become a required skill yet.
**Thus** to make the "Logging Cookbook** more useful, there should probably
be a link to a quick appendix article by Vijay describing how to create an
importable module from his long description about "Dealing with handlers
that block"... or after he presented the code for the module.
I still have a lot of the article to read and was REALLY enjoying the
coding knowledge that I was getting about the topic of logging... yet at
this point in the article, there is a MAJOR requirement in
knowledge which could be a simple appendix to the article, omitted from the
Thank you for addressing this issue. I came to this Python document
"Logging Cookbook" from IDLE reading Python documentation, and doing a
search for "logging". I am not really sure if I am reading an online
article or a downloaded file with online links in the footer of the "help"
subsystem. Yet,, I am very disappointed that Vijay's awesome article has a
stopping point where I cannot use the information presented because I do
not possess the knowledge and am not directed to a place to get the
Thank you for your attention to this problem that only needs a short
appendix or attachment at the bottom of the article... or a link to
"Creating local/private Modules Cookbook. ;)
c *in process*
c *unavailable* -> 864-999-9076
logging.handlers.SMTPHandler only uses the 'secure' argument when credentials are specified. https://docs.python.org/3/library/logging.handlers.html#logging.handlers.SM… says:
"To specify the use of a secure protocol (TLS), pass in a tuple to the secure argument. This will only be used when authentication credentials are supplied."
The docstring confirms this, but I can't find an explanation of the intent behind this behaviour. Perhaps it would be a good idea to describe this as well.