Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Functions and keeping code together #13

Open
demongolem opened this issue Nov 12, 2020 · 0 comments
Open

Functions and keeping code together #13

demongolem opened this issue Nov 12, 2020 · 0 comments

Comments

@demongolem
Copy link

In general, I am getting what I would expect which is very useful. However, functions are always a tricky one with jupyter notebook because (and correct me if I am wrong) an entire function must be kept together in the same cell, no matter how long that function might be. And when p2j runs into functions it tries to apply the same mechanisms as outside functions, which splits the functions up into multiple code cells which leads to errors.

Is there a mechanism or could there be a mechanism to treat the inside of functions differently?

Perhaps this all comes down to does jupyter encourage poor coding practices for the sake of rapid prototyping which is beyond the scope of this package.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant