futurize displaces sometimes "#!/usr/bin/env python" from first line

[wluebbe]

As can be seen from the test below the from __future__ ... statement goes to the first line if the shebang line is followed by a blank or a comment line.
If it is followed by a doc-string it is OK.

While futurizing Sage a few py-scripts were executed by bash and the import statements tried some screen-shots ... Quite surprising.

--- ./shebang-blank.py  (original)
+++ ./shebang-blank.py  (refactored)
@@ -1,3 +1,4 @@
+from __future__ import division
 #!/usr/bin/env python

 import math
--- ./shebang-comment.py    (original)
+++ ./shebang-comment.py    (refactored)
@@ -1,3 +1,4 @@
+from __future__ import division
 #!/usr/bin/env python
 # some comments
 # and more comments
--- ./shebang-docstring.py  (original)
+++ ./shebang-docstring.py  (refactored)
@@ -2,6 +2,7 @@
 """
 a doc string
 """
+from __future__ import division

 import math

Would you like to have my 3 small test scripts?
Are attachments possible?

[edschofield]

Thanks for the bug report, @wluebbe. I have pushed a fix (025c834) to the develop branch that seems to solve the problem.

A similar patch needs to be applied to handle source encoding declarations such as # -*- coding:utf-8 -*-.

[wluebbe]

Thanks, Ed! Tested the fix succesfully on the 3 small test scripts and on Sage.

Should I stay on the "develop" branch?

[edschofield]

You're welcome! :) The fix has just gone into v0.12.

We are moving to the git-flow model, where master should ideally remain in a workable state for patches with the tests always passing. So develop will move faster, and master will be used only for releases.