Peter Williams added the comment:
I'm experiencing a variation of this problem on a project where I'm trying to
make an application that will work with both 2.7.x and 3.4.x
and am mostly successful. The application uses a number of pickle files
and I want to make it so that it does
New submission from Peter Williams :
Quite often the names of subcommands are quite long so that their meaning is
clear. However, the downside to this is the increased typing the user of the
command must make. A compromise between clarity and brevity can be realized if
abbreviation of
Peter Williams added the comment:
The class I was pickling was a top level class but a field inside that class
had an instance of a nested class set as its value. The error message produced
indicated that the reason for failure was the inability of pickle to find the
class definition and (I
New submission from Peter Williams :
The built in type() function returns incorrect type names for nested classes
which in turn causes pickle to crash when used with nested classes as it cannot
find the nested class definitions from the using the string returned by type().
e.g. if I have an
New submission from Peter Williams :
At present, if a number (e.g. 2) of optional positional arguments
are defined (e.g. arg1 and arg2) argparse formats them as follows:
usage: program [arg1] [arg2]
in the usage message. I would like to suggest that a better format would be:
usage: program
