[issue35026] Winreg's documentation lacks mentioning required permission at some points
New submission from George Fischhof : Winreg's documentation lacks mentioning required permission at some points Hi there, on page https://docs.python.org/3/library/winreg.html it is not mentioned in the description of the following functions: winreg.DeleteKey winreg.DeleteKeyEx winreg.DeleteValue that they require KEY_SET_VALUE when the registry key is opened. It is mentioned for example at: winreg.SetValue with the following text: The key identified by the key parameter must have been opened with KEY_SET_VALUE access. BR, George -- assignee: docs@python components: Documentation messages: 328034 nosy: docs@python, georgefischhof priority: normal severity: normal status: open title: Winreg's documentation lacks mentioning required permission at some points type: enhancement versions: Python 3.7 ___ Python tracker <https://bugs.python.org/issue35026> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue29224] OS related file operations (copy, move, delete, rename...) should be placed into one module
New submission from George Fischhof: Hi There, OS related file operations (copy, move, delete, rename...) should be placed into one module... As it quite confusing that they are in two moduls (os and shutil). I have read that one is higher level than other, but actually to use them I have to think which function can be found in which module. It is confuse for beginners, and makes the usage more complex instead of make it more simple (as Zen of Python says ;-) ) An alias could good, not to cause incompatibility. Best regards, George -- components: Library (Lib) messages: 285115 nosy: georgefischhof priority: normal severity: normal status: open title: OS related file operations (copy, move, delete, rename...) should be placed into one module type: enhancement ___ Python tracker <http://bugs.python.org/issue29224> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue29223] Settable defaulting to decimal instead of float
New submission from George Fischhof: Hi There, Settable defaulting to decimal instead of float It would be good to be able to use decimal automatically instead of float if there is a setting. For example an environment variable or a flag file. Where and when accuracy is more important than speed, the user could set this flag, and calculate with decimal numbers as learned in the school. I think several people would use this function Best regards, George -- components: Interpreter Core messages: 285114 nosy: georgefischhof priority: normal severity: normal status: open title: Settable defaulting to decimal instead of float type: enhancement ___ Python tracker <http://bugs.python.org/issue29223> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue28714] Addition to Documentation of configparser.ConfigParser.write()
George Fischhof added the comment: Hi, issue 28788 created as feature request BR, George -- status: open -> closed ___ Python tracker <http://bugs.python.org/issue28714> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue28788] Feature request: ConfigParser should be able to write config to a given filename, not only into file object
New submission from George Fischhof: Hi There, I started to use ConfigParser, and found that it has no write to file_name option, but xml paarser (ElementTree) has. This way ConfigParser works different than xml parsers, as when I use elementtree.write it will create a file with full and valid xml content. But ConfigParser is "able" ;-) to create file with invalid content (for example (this was my findings) creates duplicated sections. Because the handling of the file is in the user's hand. So it would be good for ConfigParser to handle file writing and the user!s code would became simplier: Feature request: ConfigParser should be able to write config to a given filename, not only into file object. (Like xml parser) Kind regards, George Fischhof -- components: Library (Lib) messages: 281636 nosy: georgefischhof priority: normal severity: normal status: open title: Feature request: ConfigParser should be able to write config to a given filename, not only into file object type: enhancement versions: Python 3.5 ___ Python tracker <http://bugs.python.org/issue28788> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue28714] Addition to Documentation of configparser.ConfigParser.write()
George Fischhof added the comment: Hi Berker, It is true, I agree ;-) But this way ConfigParser works different than xml parsers (for example elementtree from system lib), as when I use elementtree.write it wil create a file with full and valid xml content. But ConfigParser is "able" ;-) to create file with invalid content (for example (this was my findings) creates duplicated sections. So it could be a feature request for ConfigParser: It should be able to write config to a given filename, not only into file object. (Like xml parser) Kind regards, George -- ___ Python tracker <http://bugs.python.org/issue28714> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue28714] Addition to Documentation of configparser.ConfigParser.write()
Changes by George Fischhof : -- title: Addition to Documentation of configparser.ConfigParser.write() documentaion -> Addition to Documentation of configparser.ConfigParser.write() ___ Python tracker <http://bugs.python.org/issue28714> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue28714] Addition to Documentation of configparser.ConfigParser.write() documentaion
New submission from George Fischhof: Hi There, I used configparser.ConfigParser.write() to update a config file. And I found that my config wa duplicated. The file was opened with mode 'r+' I figured out that write (I mean the write method of configparser) writes at actual file position. I issued a file.seek(0) command before write and the result was good. So I think documentaion should advice to user to reopen the file with mode 'w' or to issue a file.seek(0) command before using the ConfigParser.write() I used the following python version on windows: Python 3.5.1 (v3.5.1:37a07cee5969, Dec 6 2015, 01:38:48) [MSC v.1900 32 bit (Intel)] on win32 affected documentation: https://docs.python.org/3.5/library/configparser.html#configparser.ConfigParser.write Best Regards, George Fischhof -- assignee: docs@python components: Documentation messages: 280960 nosy: docs@python, georgefischhof priority: normal severity: normal status: open title: Addition to Documentation of configparser.ConfigParser.write() documentaion versions: Python 3.5 ___ Python tracker <http://bugs.python.org/issue28714> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
