Queue code cell execution Pycharm Pro, Scientific View

Answered

In Jupyter it is possible to start executing the first code cell and then queuing the execution of, for example, the next 3 code cells, so that when the execution of first has finished, the execution of the next starts.

This seems to not be possible in Pycharm's Pro Edition newly introduced scientific mode (View -> Scientific Mode), where iof I start the execution of one cells, I can't click a different cell to execute, as it displays a message saying "Previous execution still running".

Is there a way in Pycharm to emulate Jupyter's behavior?

10 comments

Hi Eikama,

Unfortunately, it is not possible to do in the scientific mode.

It is possible when using Jupyter in PyCharm. The cells will be executed in the order in which you run them. We are also working on the redesign of Jupyter support from scratch in PyCharm, it will be more powerful and stable. 

Please let me know if you have any questions.

0

Hi, thanks for your answer.

I find Jupyter in terms of workflow efficiency to be well inferior to PyCharm's Scientific Mode - if it were not for the missing code cell execution queuing, which unfortunately ruins the experience.

I'm sure a number of other devs would be very keen to switch to Scientific Mode over Jupyter (as Scientific Mode offers the full set of workflow enhancing feature of PyCharm, many of which are still lacking in Jupyter), if the basic code cell execution queuing would be available.

Thus I created a feature request here: https://youtrack.jetbrains.com/issue/PY-32545

Please let me know of there is anything else I can do to help getting code cell execution queuing working in Scientific Mode.

0

Thank you for sharing your experience and for creating a feature request, we really appreciate it!

>Please let me know of there is anything else I can do to help getting code cell execution queuing working in Scientific Mode.

You could persuade more people to vote for the feature request in order to increase priority.

0

My pleasure. I know a few data scientists as well as PhD colleagues who would like to see such a feature, as this is currently preventing them form transition from Jupyter LAb to PyCharm . I assume they have to create an account in order to vote?

How many votes does a feature typically need until it has a chance to become considered for implementation? (I think it's implementation is not too difficult, since it is not a crazy, new feature and build on top of existing functionality by just needing to keep a few lines of code in memory until dumping them to the console - just mentioning it, in case implementation difficulty plays a role here)

0

>I assume they have to create an account in order to vote?

Correct.

>How many votes does a feature typically need until it has a chance to become considered for implementation?

There is no specific number of voices. But it still depends on its amount in a way and release planning. Sorry, cannot provide more accurate information.

0

The link to the feature request appears to be dead.
I could not find the feature request manually.
Instead I upvoted this, which request the same functionality: https://youtrack.jetbrains.net/issue/PY-31820

0

@Lukas Fiederer Thanks for pointing this out! I had stopped watching progress on this, after nothing happened, even after my request gathered a few upvotes.

@Jetbrains: DID YOU DELETE MY FEATURE REQUEST??? I was not notified that a pending deletion would happen. Going through my mails I can see the last change happened on 4th March 2019, when a certain Dmnitry Trofimov updated "Project: PyCharm -> [error]". There was no error there, as the other request that Lukas linked to points out!!     
And what happened to the upvotes that feature request had already gathered? Not cool!!

0

Hello Eikama,

There was probably something wrong with one of the updates of the ticket. I can assure you that we do not delete any issues.
Could you please attach a screenshot showing this updated "Project: PyCharm -> [error]"?
We will investigate it.

0

@Serkey Just click on my link form my post above from 5 November, which I reproduce below:

https://youtrack.jetbrains.com/issue/PY-32545 

0

@Eikama

It appears that the issue was moved to another project which is private. However, you should have been granted access.

We now moved it back https://youtrack.jetbrains.com/issue/PY-32545
Sorry for the confusion.

0

Please sign in to leave a comment.