Select to view content in your preferred language

Python Window Sections — Default sizing and position

468
1
12-17-2023 05:38 PM
Status: Closed
Labels (1)
Bud
by
Notable Contributor

The Python window in ArcGIS Pro makes me irrationally angry. As a new-ish Pro user, it's one of the reasons I haven't brought myself to fully learn Python. 

One thing that makes the Python Window fiddly to use is the placement and sizing of the sections. From my experience, most IDEs have a large prompt section at the top and a small transcript section at the bottom.

For example, PyScripter:

Bud_0-1702864025777.png


But the Python Window in ArcGIS Pro seems to be the opposite.

Bud_1-1702862951133.png

I would prefer to have a large area to type in, rather than a large area to read. Could the position and sizing of the prompt and transcript sections be changed by default?

  • Large prompt section at the top
  • Small transcript section at the bottom

Not to be confused with manually resizing the sections if needed: Vertically resize Python window sections.


Of course, let me know if I've missed something.

1 Comment
HannesZiegler
Status changed to: Closed

Hi @Bud, learning Python is a giant undertaking and understandably can be frustrating (we've all been there!). As noted in a related idea you submitted, the Python Window is an interactive terminal, not an IDE. Interactive terminals differ from an IDE experience and are not meant to replace IDEs. Instead, an interactive terminal is used to run Python code interactively. Think of it like a command line, where you run commands line by line and get results immediately (in the transcript area). The Python Window is an interactive terminal integrated into ArcGIS Pro, which gives you some unique benefits as outlined in the Python Window documentation.

Using the example of the PyScripter IDE, the Python Window is more like the small terminal window at the bottom of PyScripter (and this is where it often is in most other IDEs as well).

In conclusion, the feature you are requesting will not be implemented as it goes against well-established patterns in the development community. 

Good luck on your Python journey!