h0arry / pyscripter Goto Github PK

What steps will reproduce the problem?
1. Open several documents.
2. Press CTRL-TAB once.
3. Press CTRL-TAB once another time.

What is the expected output? What do you see instead?
The second CTRL-TAB should go back to the previously-active document.
Instead, it goes to the "next" document among all the open documents; too
bad that "next" means nothing to the user, which is better off just using
the mouse to navigate.

What version of the product are you using? On what operating system?
1.7.2.6.

Please provide any additional information below.
I consider this a high-priority enhancement. Having CTRL-TAB go to the
"next" document in the order in which files were opened makes it pretty
useless, since documents are often opened in random orders. If the user
wants to quickly switch among 2 or 3 files, he is forced to use the mouse,
while it could use the CTRL-TAB, were it implemented correctly.

Notice that the correct behaviour is precisely described (and rationalized)
here:
http://en.wikipedia.org/wiki/Alt-Tab

What steps will reproduce the problem?
1. Multi thread started.
2. Program terminated.

What is the expected output? What do you see instead?

After program terminated, those threads have kept activated.

What version of the product are you using? On what operating system?

PyScripter 1.8 and internal python engine.
PyScripter 1.8 and remote python engine.(Rpyc)

Please provide any additional information below.

Presently I use the remote engine. And the engine has been initialized in
every execution.

Please could you change de location of the pyscripter.ini file in the same 
folder where pyscripter.exe is located ?

This is more helpfull.

On startup, PyScripter currently restores the set of files you had open the
last time you shut down successfully. The problem is if you have to force
kill the process, the current set isn't remembered.

To reproduce:
1. Start PyScripter.
2. Open a few files.
3. Run this script:
      while 1: pass
4. Kill PyScripter and reload it.

What steps will reproduce the problem?
1. Define the following function:

def foobar(b="Hello, world", c=0):
    pass

2. Try typing "foobar(" and wait for the suggestion to appear.

What is the expected output? What do you see instead?
I would expect the suggestion to report the default argument as "Hello,
world". Instead, I see "****, *****" (all characters are substituted with
*). Moreover, PyScripter is confused by the comma in the string, as you can
see by the fact that it displays in bold only the first part of the string. 

What version of the product are you using? On what operating system?
PyScripter 1.8.0.0 on Windows

When the filter of the File explorer is set to ActivrScript all works ok
but then you close pyscripter, then change the directory and edit another 
file in another directory, It should be better that the filter updates to 
the current new directory instead of memorizing the last used directory.

At least i think so.

Incremental search in the editor possibly borrowing the design of Firefox
search.

Redefining Ctrl-A to “word left”, Ctrl-F to “word right” does not work, 
and
perform the (windows?) default action: “select all” and “find”, 
respectively.
Some more: Ctrl-Z, Ctrl-C, Ctrl-S.
It probably affects all (windows?) default GUI keystrokes.

Header & footer position (left/center/right) and font not saved

What steps will reproduce the problem?
1. file->page setup->Header&footer
2. move header/footer content to left or right box, change font size or
style (bold/italic)
3. press ok
4. exit application

What is the expected output? What do you see instead?
Settings are reverted to defaults after application restart: header and
footer in centre, 10points, etc.

What version of the product are you using? On what operating system?
v1.7.2.0 on WinXPsp2

Please provide any additional information below.
Once selected, “Shadow” checkbox for header seems to be stuck and even when
unchecked, is restored after application restart.

Ability to edit a file by opening more than one window or view.  Any changes in 
a window are 
immediately reflected in the other views of that file. 

I prefer to keep the debug windows (Watches, Breakpoints, etc.) in tabs at
the bottom instead of as floating palettes, but I do like to rearrange the
tabs frequently while I'm debugging depending on the problem I'm looking
at. It requires extreme patience and care to rearrange the tabs without
accidentally breaking out the window (and if I fail, it's painfully
difficult to restore the palette to tab form, in part because of bug 46).
This is a dance I go through frequently throughout the day, so I'd
appreciate if there were a way to "lock" the tabs in place so they could be
moved around at will without detached. Perhaps holding down a modifier such
as Ctrl would activate this mode (although I'd strongly prefer if they were
locked by default and you had to hold down a modifier to detach them!).

I use code templates heavily, so I'm often creating new ones. Without fail,
every time I create a new one, I end up doing it twice--because I always
forget to hit Update before I hit OK. It seems far more intuitive to me to
just have the updates take effect when OK is pressed and remove Update
altogether.

What steps will reproduce the problem?
1. type "len"
2. type "("
3. type "str"
4. type "("

What is the expected output?:
len(str())

What do you see instead?:
len(str()

What version of the product are you using? On what operating system?
v1.7.1.2 on WinXPsp2

Please provide any additional information below.
Also fails with unmatched baces, i.e. "[" or "{":
type "len([" -> see len([) 
expected: len([])

1. Open two files (A and B) in PyScripter
2. With a single copy operation (from the shell or explorer), overwrite
both of them with other two different files.
3. Switch back to PyScripter. A messagebox will appear telling that A (or
B) is changed and asking if the user wants to rewrite.
4. After pressing Yes, the file is reloaded, but the modification of B is
not detected.


I would expect the editor to popup multiple consecutive messagebox for each
changed files. Or in alternative, a single dialog showing all changed files
together, asking whether I want to reload them (and which of them) or not
(Komodo does this).


PyScripter 1.7.2.5 under Windows.

Since we are at it, I would love an option called "automatically reload all
changed files without asking, unless they currently have unsaved
modifications in PyScripter, in which case please ask me". Other editors
have this option, because when working with a SCM it's VERY important to
NEVER miss an update operation. It's usually *much* better to even *lose*
unsaved modifications rather than missing an external update (which you
could then revert without noticing); this is because usually there are only
a few unsaved modifications (programmers do save very often, this is not
Word :)). So really, asking if you want to reload or not when working with
SCM is like asking "do you really want to ignore this update and screw the
repository?".

It would be great if Find in Files supported string replacements. 

Please provide any additional information below.
Some programming editors (like Visual Studio and Komodo) have a nice
feature: when you open a new file (through the usual File/Open, CTRL+O),
the starting directory in the dialog will be the *same* of the file
currently opened in the editor.

This is interesting because the open file dialog of Windows does not have a
LRU control to quickly jump to recently-used directories. So, when you
navigate away from a commonly-used directory for some reason (typical: open
a file in Python\Lib), it is a bit of a pain to navigate back to the project.

Instead, if you know you can do it, you can just select a file in the
project before pressing CTRL+O. This way, the correct directory will be
automatically selected.

This can't surely be *worse* than the current behaviour, and it works much
bettere in many cases. I suggest you implement this in PyScripter as well.

Implement post mortem debugging

What steps will reproduce the problem? Type the following code:
class test:
    def __init__(self):
        self.a_multiline_string = """this is
a multi line string"""
    def method1(self):
        """a method belonging to the class "test"
        but not recognised as such by Code Explorer.
        Interpreted correctly though"""

What is the expected output? What do you see instead?
In Code Explorer "method1" does not belong to the class "test".
It is interpreted correctly by internal/external Python.

What version of the product are you using? On what operating system?
1.8.0.0 on WinXPsp2

Please provide any additional information below.
A side note. Pressing "tab" on the line below 'a multi line string"""'
adds two spaces on first key press and two tabs on the second.
Neither is the desired effect :-) but my editor options might be messed up.
Screenshoot attached.

Please, could you swap the positions of buttons of indentation in the 
editor toolbar, this is not a mayor issue but easy to "correct", it is 
more "correct" that the left button "move" the code to the left (dedent) 
and the rigth button "move" the code to the rigth (increase indent).

I thin that this is easy an practical.

What steps will reproduce the problem?
1. Open a Python file in ANSI format (latin-1)
2. Change the -*- coding line to "UTF-8".
3. Save it.
4. Look at the Edit/File format menu.

What is the expected output? What do you see instead?
The file format menu should show "UTF-8" selected (or "UTF-8 NO BOM" in my
case since I disabled BOM in the options), but it still shows ANSI.

What version of the product are you using? On what operating system?
1.7.2.6, Windows.

What steps will reproduce the problem?
1. Run a script as an External Run

When it finishes the output window says
"Process "Pyhton Interpeter" terminated, ExitCode: 00000000"

Pyhton should be spelled Python :)

-Josh

Please, use JCreator from  http://www.jcreator.com/
as a model of an incredible tool.

Jcreator is easy, simple but very powerfull.

I think that pyscripter must follow the same way

Also, there is a lot of features that could be copied from JCreator

Also, and indeed the look that actually is very close, but JCreartor has a 
more homogeneous look

I use the interpreter window to output diagnostic information while running
tests, and I find it less distracting to begin each test run with a clean
slate. As far as I can tell, the only way to clear the window right now is
via the context menu's "Clear All" item. Two additional options would make
this perfect for me:

1. Support automatic clearing of the output if an exception did *not* occur
during the script run. I do want to study the output if a problem happened,
but if everything succeeded, I rarely have reason to look.

2. Support "Clear Interpreter Output" as an action that can be bound to a
keystroke. This would enable fast clearing of the window in cases when an
error *did* occur after I've finished studying the output.

What steps will reproduce the problem?
1. Start PyScripter

What is the expected output? What do you see instead?
There is a small gap between Debug toolbar and Editor toolbar (see attached
picture)
Since the tool bar order/positions are not saved between sessions, this gap
occurs on every program start.


What version of the product are you using? On what operating system?
v1.7.1.2 (also present in versions 1.5.1 & 1.7.1)

Please provide any additional information below.
This bug is purely cosmetic and does not seem to affect functionality.
Tested on WinXPsp2/default Classic Theme

Hello,

I suggest adding a feature "replace in files", which is basically a
"replace" applied to all matches found by a "find in files" (either across
open files only, or in directories). Visual Studio has this feature and it
is very handy when doing renames across a whole project.

What happens when the program should do a replace in a file which is
currently not opened in the IDE? Visual Studio basically has an option for
this in the dialog, called

- The file is automatically opened, and the modification kept in memory
(you then need "save all" to flush everything to disk).
- The file is silently modified on disk.

Given how much time I spend on the computer, I run at a high font DPI in
Vista to ease eye strain. Unfortunately, the tabs in PyScripter (for both
files and the debugger) do not respect the font size. 

To test it out, you can change the dpi in Vista with these steps:

1. Open Control Panel
2. Click Optimize Visual Display under Ease of Access.
3. Click "Change the size of text and icons" under "Make things on the
screen larger."

I realize this may be a pain to fix if it's a bug in whatever UI toolkit
you're using, so I'd gladly settle for a PyScripter-specific option!

As soon as a GeneratorExit exception is thrown in a script, the debugger
fails. Stepping no longer works, and the script runs to completion without
stopping at future breakpoints. Python throws GeneratorExit automatically
whenever a generator is destroyed, so this happens pretty frequently.

To reproduce, put a breakpoint on the first line below and try stepping
through:

a = (a for a in ())
del a
print "hey"

When you have the Find window open, pressing Ctrl+H (the Replace keystroke)
should add the replace options. This is how Visual Studio 2005 behaves, and
it's very handy when you inadvertently hit the find keystroke when you're
intending to replace.

When you middle click on a file tab at the bottom, the file should close,
just as tabs behave in Firefox and in Visual Studio 2005.

Summary says it all, I think. This is consistent with Visual Studio and
would make creating new watches significantly faster.

Add a Project Manager to PyScripter

Currently, Code Explorer shows only the imported module, regardless if the
whole module (i.e. import sys) or only part of it (from math import log,
sqrt) was imported.

Proposed enhancement:
make a distinction between various import statements. 
Individually imported methods can be shown using a different colour and/or
icon (may be with an appended () i.e. “log()”.)
The tooltips can be changed to “method(or class) imported from <module
name> at line N” and “class imported at line N”.
There is no need to repeat the module/function name in the tooltip (as done
now), because it it already visible under the cursor :-) . It may be useful
to put the original module name if it was imported using the “as” statement.

Moving a debugger palette (such as Variables or Call Stack) that is
free-floating around the screen is painfully slow (and the window outline
flickers repeatedly). This is under a dual core 2.33ghz with 2GB of ram and
256MB video ram, so I don't think it's just my system. I think it may be
related to Vista, however, because I don't recall experiencing this on my
XP machine.

The find feature doesn't wrap automatically when the end of the document is
reached, nor does there seem to be an option to enable this behavior.

What steps will reproduce the problem?
1. Make a folder with a few py files in it
2. Open pyscripter 
3. browse the folders with the file explorer tree in the pyscripter

What is the expected output? What do you see instead?
py files in the folder are visible only if the folder contains subfolders
not if it only contains py files

What version of the product are you using? On what operating system?
1.7.2.0

What steps will reproduce the problem?
1. Push the "refresh" button in the todo list onto a large project tree.

What is the expected output? What do you see instead?
I would like the todo list to be refreshed in background. Instead, the
mouse cursor becomes a hourglass and the whole program stops accept input
until it's done.

What version of the product are you using? On what operating system?
1.7.2.6.

Please provide any additional information below.
It's a low-priority enhancement, of course.

What steps will reproduce the problem?
1. create a function:
def test():
    pass
    #"""This should not be PyDOC!"""

What is the expected output? 
No PyDOC (as returned by __doc__ method)

What do you see instead?
Code Explorer shows the string.

What version of the product are you using? On what operating system?
v1.7.2.4 on WinXPsp2

Please provide any additional information below.
Even commented out strings (starting witth #""") are taken.
Everything is fine if PyDOC is present.
May be calling directly __doc__ method would be the most canonical way to
fix the bug. 

Some info on PyDOC conventions: http://www.python.org/dev/peps/pep-0257/

What steps will reproduce the problem?
1. Crate a new keystroke
2. Forget to check "Apply to all editors" box when pressing "ok"
3. Quit the application

What is the expected output? What do you see instead?
On the next start the keystroke does not exist.

What version of the product are you using? On what operating system?
v1.7.2.0 / WinXPsp2

Please provide any additional information below.
The keystroke assignment are logically for all editors. The checkbox should
not exist on this tab or be ignored when saving this information (or be
constitutively selected, but it will create complication when moving from
one tab to an other)

What does the "Update" button do?

What is the expected output? What do you see instead?

I want to see the colors of the original IDLE.

I use pyscripter, but some times it is more easy to simply open a short 
file with IDLE.

Due to IDLE has a classical colors for python syntax, I think  that at 
least pyscripter must let me personalize the sintax coloring to the colors 
used by IDLE but this is not possible now because there is not much colors 
to chose, indeed it is impossible to chose the colors of python original 
IDE.

Thus, I am going crazy when a see the file in IDLE and then in pyscripter 
because they look a lot of different being the same file.

This is no crucial but a aestetical enhacement which is not present in any 
other python IDE.

thanks...

What steps will reproduce the problem?
1. Create a multi-line todo:

# TODO: this is a multi-line
# todo item which will not be parsed.

2. Open the TODO window


I would like to see the whole multi-line todo in the window correctly, but
only the first line is displayed.

Hello,

at my company, we have a convention that all Python source files needs to
be always full trimmed (no trailing spaces whatsoever at any line).
PyScripter has an IDE options called "trim trailing spaces", but I'm not
sure what it is supposed to do since it does not seem to work.

What steps will reproduce the problem?
1. Move the caret to the end of an indented line.
2. Press ENTER. The new line will have leading spaces to match up the
previous line's indentation.
3. Now save the file. 

What is the expected output? What do you see instead?

I would expect PyScripter to always trim trailing spaces when I save a
file. Instead, it can be seen that the save file does have trailing spaces.

What version of the product are you using? On what operating system?

1.8.0.0.

Please provide any additional information below.

If this option does something else, please consider adding an option to
trim all trailing spaces when the file is saved. It would help me a lot and
other editors do have it. Thanks in advance!

Hello,

I would love an option to tell PyScripter to *always* auto-reload files
which were externally modified (unless they have unsaved modifications). In
my environment, where I always use CVS/SVN and other SCMs, asking what to
do is useless: if you don't reload, you lose updates. I suspect many others
would find such an option very reasonable.

Thanks!

Code folding is a great way to look at your source without being
overwhelmed by it. Please add folding (even if just at the function level
for now)

Thanks,
Josh

Implement a remote interpreter and debugger that will allow PyScripter to
work with and debug GUI programs such as wxPython.

If do you want that your pyscripter looks like the standar IDLE python 
editor please use the attached file as you pyscripter.ini

It would be nice to be able send pieces code from the IDE to the shell for
execution.
Here are some suggestions for buttons and/or ctrl- sequences to do this:
1> Send current line
2> Send selection
3> Send balance
3> Send all
The first two are the important ones.

José Cláudio Faria's superb Tinn-R, a GPL'd IDE for R written in Delphi,
has this capability. It is based on Tinn, a very simple/elegant ASCII editor. 

http://www.r-project.org/
http://www.sciviews.org/Tinn-R/
http://tinn.solarvoid.com/

In fact, Tinn-R might serve a source of code and/or ideas for pyscripter.

    jab

It seems to be possible to define double keystrokes for two different actions.
What steps will reproduce the problem?
1. Define keystroke Ctrl+Q 0 for any action
2. press Add
3. Define keystroke Ctrl+Q 0 for some other action
4. press Add

What is the expected output?
A warning dialog box and keystroke rejected.

What do you see instead?
Duplicate action for the keystroke is accepted.

What version of the product are you using? On what operating system?
v1.7.2.3 on WinXPsp2

Please provide any additional information below.
The first entered action seems to be used.

Currently PyScripter uses
%USERPROFILE%\Application Data\PyScripter\Updates\
to store updates. these updates tend to accumulate over time (especially if
one faithfully updates to every beta :-) )
May be using %TEMP%\PyScripter would be more appropriate, given the
temporary nature of these files. Also, being placed in %TEMP% these files
can be cleaned automatically by the OS or 3rd party tools, may be even by
PyScripter itself, if it sees that the update file version is =< than its.

In the same vein, perhaps PyScripter.ini should be stored in
%USERPROFILE%\Application Data\PyScripter\ by default.

PyScripter should automatically call gc.collect() after running a script.
Take the following script:

class File(file): pass
f = File("c:/users/blake/temp/pyscripter.txt", "w")
f.file = f  # Create circular ref

Because a reference cycle is created, the file will not be freed, which
means Windows prevents it from being deleted. It's not too much of a pain
in this case to call gc manually in the interpreter, but if the objects in
question have finalizers, the collector won't break the cycles, and I need
to break them explicitly.

This happens often when using the debugger to track down test failures and
aborting a debug session when the problem is found. Since the script
doesn't run to completion, known cycles are not broken, and files created
during the test are not deleted. Because the file objects still exist, I
can't manually delete the test files, and often the fastest option is to
restart PyScripter.

1. Define this function:

def AAA(aa,   # BUG
        bb):
    pass

2. Type AAA(


The code tips should display "aa, bb", instead it displays "aa, #, ***,
bb", which is wrong. It looks like it's confused by the comment.

I'm on PyScript 1.7.2.5.