[issue41379] Configparser is not reading Indended Sections as Mentioned in Docs
Change by Vignesh Rajendran : -- components: +Library (Lib) ___ Python tracker <https://bugs.python.org/issue41379> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue41379] Configparser is not reading Indended Sections as Mentioned in Docs
New submission from Vignesh Rajendran :
https://github.com/jaraco/configparser/issues/55
Please check the Bug is raised also in Github,
Sections can be intended is specified in the documentation.
When I read the indented section, its throwing section not found an error in
python 3.8
as per Documentation https://docs.python.org/3/library/configparser.html
[You can use comments]
like this
; or this
[Sections Can Be Indented]
can_values_be_as_well = True
does_that_mean_anything_special = False
purpose = formatting for readability
but this is not working.
check this
https://stackoverflow.com/questions/62833787/how-to-read-indentated-sections-with-python-configparser/62836972?noredirect=1#comment76192_62836972
if i read an indented section, its showing section not found.
my file:
[section]
a = 0.3
[subsection]
b = 123
import configparser
conf = configparser.ConfigParser()
conf.read("./test.conf")
a = conf['section']['a']
print(a)
Output of a:
0.3
[subsection]
b = 123
Expected a : 0.3 only
But Section b is not found
--
messages: 374160
nosy: Vignesh Rajendran
priority: normal
severity: normal
status: open
title: Configparser is not reading Indended Sections as Mentioned in Docs
type: behavior
versions: Python 3.8
___
Python tracker
<https://bugs.python.org/issue41379>
___
___
Python-bugs-list mailing list
Unsubscribe:
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue33244] Overflow error
New submission from Vignesh <vigneshprasant...@gmail.com>: Help me to recover this... -- assignee: terry.reedy components: IDLE files: New Doc 2018-04-09.pdf messages: 315107 nosy: Vignesh, terry.reedy priority: normal severity: normal status: open title: Overflow error type: behavior versions: Python 2.7, Python 3.4 Added file: https://bugs.python.org/file47525/New Doc 2018-04-09.pdf ___ Python tracker <rep...@bugs.python.org> <https://bugs.python.org/issue33244> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue8751] Threading and KeyError: 51
New submission from Vignesh vigne...@mail.med.upenn.edu: I have a python script which runs a particular script large number of times (for monte carlo purpose) and the way I have scripted it is that, I queue up the script the desired number of times it should be run then I spawn threads and each thread runs the script once and again when its done. Once the script in a particular thread is finished, the output is written to a file by accessing a lock (so my guess was that only one thread accesses the lock at a given time). Once the lock is released by one thread, the next thread accesses it and adds its output to the previously written file and rewrites it. I am not facing a problem when the number of iterations is small like 10 or 20 but when its large like 50 or 150, python returns a KeyError: 51 telling me element doesn't exist and the error it points out to is within the lock which puzzles me since only one thread should access the lock at once and I do not expect an error. This is the class I use: class errorclass(threading.Thread): def __init__(self, queue): self.__queue=queue threading.Thread.__init__(self) def run(self): while 1: item = self.__queue.get() if item is None: break result = myfunction() lock = threading.RLock() lock.acquire() ADD entries from current thread to entries in file and REWRITE FILE lock.release() -- components: IDLE messages: 105981 nosy: Vignesh.K priority: normal severity: normal status: open title: Threading and KeyError: 51 versions: Python 2.5 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue8751 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
