New submission from Gurmeet Singh:
This is the first time I am creating an issue. I may be doing something wrong.
I will correct that if you make me aware about it!
Issue with documentation:
Documentation page: http://docs.python.org/3/library/os.path.html
Entry: os.path.normpath(path
New submission from Gurmeet Singh:
Source page: http://docs.python.org/3/library/os.html
Entry: os.walk(...)
Ambiguity Source: Name of the argument TopDown and / or its description.
The TopDown name is misleading to me. I would suggest BFS or DFS instead.
TopDown false would imply to me
New submission from Gurmeet Singh:
Source page: http://docs.python.org/3/library/os.html
Entry: os.walk(...), os.fwalk()
These functions seems to be a generator functions. An expert like yourself may
have no trouble to make this out. But for novice (or for people out of touch)
like myself
New submission from Gurmeet Singh:
Incompletely explained documentation at 2 places:
1. http://docs.python.org/3/library/functions.html#open
The buffering argument is not correctly explained when setting to a positive
argument in binary mode.
2. http://docs.python.org/3/library/os.html
Gurmeet Singh added the comment:
Hi Terry,
I understand it is ok for you. I agree that you are not in favour of changing
the argument name. And you are correct that I must get familiar to the
convention that has been used. Further since you say, perhaps, I now feel that
it may be used
Gurmeet Singh added the comment:
The issue with buffering problem mentioned in my previous comment has been
raised as issue 17440.
However, I need to apologize again! The statement that buffering is not
implemented at all was incorrect - instead read1() was not implemented. See the
mentioned
New submission from Gurmeet Singh:
1. The read mode is not the default mode as mentioned in the docs.python.org.
In particular see the first Traceback below - b does not work (as it does in
C though) and
you are forced to use rb instead.
2. io.BufferedReader does not implement read1
Gurmeet Singh added the comment:
At the moment, I running late for creating a program - so I apologize that
immediately I would not able to work on creating a patch. Later though I may be
able to. I am sorry.
To avoid wasted work I think patch should be created only after someone (do
Gurmeet Singh added the comment:
Please read the comment completely.
For the first point
___
I apologize that there was no mistake in binary mode and I have read it
hastily. There is no ambiguity in the binary mode as you said. Reading hastily,
I felt '...(only usable in text
Gurmeet Singh added the comment:
I am sorry to reopen this issue, if you do not like this comment, then I will
reopen issues again.
I am not saying to change the convention of the documentation - I just
requested you to say something that would indicate that it is function that
gives result
Gurmeet Singh added the comment:
Please consider following before making a decision:
__
io.BufferedReader does not implement read1 (the last lines of trace
below)
It does. You made a mistake in your experiment (you called read1() on a FileIO
object, not a BufferedReader object
Gurmeet Singh added the comment:
Please consider following before making a decision:
io.FileIO does not implements single OS system call on read() - instead
reads a file until EOF i.e. ignores the arguments supplied to read()
Your experiments show otherwise, the argument supplied to read
Gurmeet Singh added the comment:
@Antoine - wait I will do it
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue17440
___
___
Python-bugs-list
Gurmeet Singh added the comment:
@Antoine
It worked. I was wrong to say read1() was not implemented. Sorry.
But please do consider other issues.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue17440
Gurmeet Singh added the comment:
I did the following to understand time taken for in memory copy:
1 fl = io.FileIO('c:/temp9/Capability/Analyzing Data.mp4', 'rb')
2 byt = fl.read(70934549)
3 byt2 = None
4 byt2 = byt[:]
5 fl.close()
6 fl = io.FileIO('c:/temp9/Capability/Analyzing Data.mp4', 'rb
Gurmeet Singh added the comment:
Sorry, typo in the last post - I meant in memory - memory copy not in place
memory copy.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue17440
Gurmeet Singh added the comment:
Thanks for letting me know about the optimization.
I trusted you that the system call is made once, though I looked up code to see
if size of the read in buffer is being passed to the C routine. I should
apologize though for raising this issue - since
17 matches
Mail list logo
