@pitti: Ok, that is weird. Just tested on a trusty vm and I could not reproduce the problem.
When I reproduced it, I extracted qrcode from the deb, put the directory on PYTHONPATH and ran it.
I did that because, even though I was running trusty, I don't have sudo powers to install the package myself (this is a diskless station at my work, I use debian at home and thus could not reproduce there either), and I was trying to check if the python-qrcode package on trusty was compatible with something I'm developing.
When I did that, it gave me an ImportError (as is expected because of the missing qrcode/image/__init__.py that should make it not be considered a package) that I could fix by creating the missing file. Then I came here to report the "bug".
The question now is, why those 2 approaches are giving me different results? AFAIK, they should run equally.
@pitti: Ok, that is weird. Just tested on a trusty vm and I could not reproduce the problem.
When I reproduced it, I extracted qrcode from the deb, put the directory on PYTHONPATH and ran it.
I did that because, even though I was running trusty, I don't have sudo powers to install the package myself (this is a diskless station at my work, I use debian at home and thus could not reproduce there either), and I was trying to check if the python-qrcode package on trusty was compatible with something I'm developing.
When I did that, it gave me an ImportError (as is expected because of the missing qrcode/ image/_ _init__ .py that should make it not be considered a package) that I could fix by creating the missing file. Then I came here to report the "bug".
The question now is, why those 2 approaches are giving me different results? AFAIK, they should run equally.