r...@zedat.fu-berlin.de (Stefan Ram) writes:
> Ethan Carter <ec1...@somewhere.edu> wrote or quoted:
>>Can you think of anything I'm missing?
>
> The correctness of a program as a solution to an assignment
> depends on the exact wording of the assignment, so it's a
> bit difficult to say without seeing it.
You're right. There's no written statement. The exercise was suggested
by the teacher while in class. It was something like ``write a program
that copies text files by getting source and destination via the
command-line.''
>> """Copies text file named S to text file named D."""
>
> This is not entirely clear, since case is significant in Python
> ("S" is not the same as "s"), and it is ambiguous whether it refers
> to a file actually named "S" or to a file whose name is provided as
> a str object bound to the name "s" in the function's source code.
This is how docstrings are traditionally written in GNU EMACS ELISP
code---they upcase argument names of the procedure being documented. I
can't recall who taught me this, but I believe it was Robert Chassel in
his book ``An Introduction to Emacs Lisp'' that's included in the GNU
EMACS itself.
But, yeah, if the Python community doesn't do that, it's all what you
say.
Thanks for your attention!
PS. Is it just me or there's just us in this used-to-be-very-active
group? Thanks for being my teacher here. Have a good day!
--
https://mail.python.org/mailman3//lists/python-list.python.org
