Description of problem: Running sqlformat results in the message ImportError: No module named 'sqlparse'. This is because sqlformat runs with python3 (according to its first line which, in Fedora 21, is #!/usr/bin/python3) but the sqlparse module that is also part of the RPM is installed in the python2.7 tree. Version-Release number of selected component (if applicable): python-sqlparse-0.1.11-4.fc21.noarch How reproducible: 100% Steps to Reproduce: 1.run sqlformat 2. 3. Actual results: Traceback (most recent call last): File "/usr/bin/sqlformat", line 12, in <module> import sqlparse ImportError: No module named 'sqlparse' Expected results: [ERROR] No input data. Usage: sqlformat [OPTIONS] FILE, ... Additional info: $ head -1 /usr/bin/sqlformat #!/usr/bin/python3 $ rpm -ql python-sqlparse /usr/bin/sqlformat /usr/lib/python2.7/site-packages/sqlparse /usr/lib/python2.7/site-packages/sqlparse-0.1.11-py2.7.egg-info [...] On Fedora 20, the first line of sqlformat is #!/usr/bin/python.
This message is a reminder that Fedora 21 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 21. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '21'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 21 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
I've fixed this in master: http://pkgs.fedoraproject.org/cgit/python-sqlparse.git/commit/?id=1580d4dd5aa456110661c2d2dc0e739b7157e679 and built it for rawhide: http://koji.fedoraproject.org/koji/buildinfo?buildID=696240 hhorack as the package is buggy in F21, you could push the rawhide fix back all the way to F21 if you want. (If the package had been working on F21 I wouldn't push it back as it changes which package the user would need to install to get the sqlparse command).
Thanks, Toshio. I've back-ported it only to F23, where python 3 is considered default and won't probably change it in F22 and lower, unless somebody convince me it is a good idea to remove /usr/bin/sqlparse from python3-sqlparse package (which could break something on users' machines).
python-sqlparse-0.1.18-3.fc23 has been submitted as an update to Fedora 23. https://bodhi.fedoraproject.org/updates/FEDORA-2015-f1b99e85cd
python-sqlparse-0.1.18-3.fc23 has been pushed to the Fedora 23 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with $ su -c 'dnf --enablerepo=updates-testing update python-sqlparse' You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2015-f1b99e85cd
Fedora 21 changed to end-of-life (EOL) status on 2015-12-01. Fedora 21 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.
python-sqlparse-0.1.18-3.fc23 has been pushed to the Fedora 23 stable repository. If problems still persist, please make note of it in this bug report.