Hi everyone,
Here are a couple of issues in the release candidate.
*1) When using "run selection"*
Create a new .py file with the code
# No indentation between 'print i' and 'print i+1'
for i in range(10):
print i
*
*
print i+1
*
*
Put the focus on a regular python console (not ipython), select all the
text in the editor and use the "run selection or current block" button.
This yields an indentation error. This can probably be considered as a bug.
*Fix:* In base.py (widgets/sourcecode) line 416
# If there is a common indent to all lines, remove it
min_indent = 999
current_indent = 0
lines = text.split(ls)
for i in xrange(len(lines)):
line = lines[i]
if line.strip():
current_indent = _indent(line)
min_indent = min(current_indent, min_indent)
else:
lines[i] = ' ' * current_indent
text = ls.join([line[min_indent:] for line in lines])
*
*
It solves the problem for me. The number of space characters added to empty
lines has to be the current indentation, for the case of nested loops.
*2) Editor widget and debug toolbar*
*
*
The debug toolbar items are missing when separating the editor dock from
the main window.
*Fix:* In editor.py (plugins) line 903
*
*
self.dock_toolbar_actions = file_toolbar_actions + [None] + \
source_toolbar_actions + [None] + \
run_toolbar_actions + [None] + \
debug_toolbar_actions + [None] + \
edit_toolbar_actions
*3) Regarding issue
852<https://code.google.com/p/spyderlib/issues/detail?id=852&q=MS%3Dv2.3&colspec=ID%20MS%20Stars%20Priority%20Modified%20Cat%20Type%20Status%20Owner%20Summary>
*
With the first point corrected as mentioned above, the "hack" of
mixins.pydocumented already does the job to add the Matlab-like cell feature.
So I
don't really see why one should consider it as a hack, or why it would be
less maintainable than the current version.
- text = unicode(cursor0.selectedText())
- return len(text.strip()) == 0 or text.lstrip()[0] == '#'
+ text = unicode(cursor0.selectedText()).lstrip()
+ return text[:2] == '# %%' or text[:12] == '# <codecell>'
The thing is that with this modification, the behavior will already be the
one you want eventually, and this Matlab-like cell feature is the most
popular feature request in the tracker. To be rigorous, "block" should be
replaced by "cell" in doc strings, functions names, and menus.
I know that Carlos wants to add some graphical visualization of the cells
in the editor (horizontal lines and coloring), but with this modification,
the behavior of Spyder 2.2 would already be more consistent with what you
guys want to do in 2.3.
*4) No warning in the case of presence of lock files*
If spyder crashes and spyder.lock directory remains, spyder won't start
again, and no error message is displayed. It just fails to start. Maybe a
their should be at least an error message in the console or even better a
pop-up window.
Finally, I would really like to thank Carlos, Pierre and Jed for their
incredible work on this IDE. I think that spyder 2.2 will really become a
reference. You guys are going to become as famous as the creators of
ipython, or numpy. Spyder was the missing link in the scientific python
world and you created it.
Cheers,
Sylvain
--
You received this message because you are subscribed to the Google Groups
"spyder" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/spyderlib?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
