fix: check force_speed by absence of property

[git-developer]

Fix for #162

[Ayush1325]

Found the problem. The force_speed property was originally set if -b was specified and was not a cli argument. Since it does not exist as an argument, args.force_speed is always false. It can be fixed as follows:

# Remove default value
 parser.add_argument('-b', '--baud', type=int, help='Baud speed (default = 500000)')

..

force_speed = False
if args.baud:
    force_speed = True
else:
    args.baud = 500000

[git-developer]

Thanks for your quick response, @Ayush1325! I'd like to encourage you to open a PR and add the changes there. I will close this one then. The reason is that I cannot judge if the changes make sense or even are syntactically OK (I'm not a python developer).

If that is not acceptable for you, I can add patches to this PR. I'd like to ask you for the exact location and content of the code changes, preferably in patch format.

[git-developer]

I noticed one thing about your proposal: the default baud rate of 500000 is already set in open(). I suggest to avoid this duplication.

[git-developer]

Closed for #165

[Ayush1325]

I have created a PR: #165

While it is true that it is already set in open(), args.baud is being used at many other places and thus needs to be set. Also since baud is the 2nd argument of the function, the default value cannot be removed there without some refactoring. So I have moved the default baud to a global constant for now.