Argument convention in PyTorch
I am new to PyTorch and while going through the examples, I noticed that sometimes functions have a different convention when accepting arguments. For example transforms.Compose receives a list as its argument:
conventions
Is there a standardized method to swap two variables in Python?
In Python, I’ve seen two variable values swapped using this syntax:
Python __str__ versus __unicode__
Is there a python convention for when you should implement __str__() versus __unicode__(). I’ve seen classes override __unicode__() more frequently than __str__() but it doesn’t appear to be consistent. Are there specific rules when it is better to implement one versus the other? Is it necessary/good practice to implement both?
Why are shared libraries executable?
Why have almost all the shared libraries in /usr/lib/ have the executable permission bit set? I don’t see any use case for executing them. Some do manage to hook-up some form of main function to print a short copyright and version note, but many don’t do even that and segfault upon execution.
File extensions for unix shell scripts
For the .sh file extension type, see Bourne shell.