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

Add support for jupyter notebook #210

Closed
wants to merge 3 commits into from

Conversation

pakio
Copy link

@pakio pakio commented Jul 2, 2020

Related Issue
#51, #186, #199

Detail
Add support for jupyter notebook.
To parse notebook to python, used nbconvert library which officially provided by Project Jupyter.

note
As known issue, .ipynb which uses magic command without % cause Error when parsing script with awk.process().
For now I just left comment to let the user notice it, if you have good idea to fix it, I will be appreciated if you tell me.


Sorry for continue reopening PRs, I finally could find the reason why my coverage decreased and fixed it, also checked if the ci and coverall works fine in my repo.

@coveralls
Copy link

Coverage Status

Coverage decreased (-0.5%) to 70.881% when pulling 5d57b4e on pakio:add_notebook_support into 060f52f on bndr:master.

@coveralls
Copy link

coveralls commented Jul 2, 2020

Coverage Status

Coverage decreased (-0.5%) to 70.881% when pulling 7fb8d45 on pakio:add_notebook_support into 060f52f on bndr:master.

@alan-barzilay alan-barzilay mentioned this pull request May 17, 2021
6 tasks
@@ -17,7 +17,7 @@
history = history_file.read().replace('.. :changelog:', '')

requirements = [
'docopt', 'yarg'
'docopt', 'yarg', 'nbconvert', 'ipython'

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@pakio
Copy link
Author

pakio commented Jul 17, 2022

Hi @jamesmyatt cc @alan-barzilay , sorry for being stale for a long time. I just started to work on it again, but seeing an issue related to nbconvert. (issue, failing test)
This could be resolved once I update the nbconvert version to latest or near-latest, but they are not supporting python 3.6 anymore.

Do you have any plan to stop supporting python3.6 in the near future?

@jamesmyatt
Copy link

jamesmyatt commented Jul 17, 2022

Im not a maintainer but Python 3.6 is EOL so dropping support makes sense.

Pereonally I'm in favour of small projects like this only supporting relatively few python versions for new releases. For example big projects often support 42 months of releases, like NEP29. But I would do less here. Remember that maintainers are volunteers.

If I were you, I'd remove 3.6 and possibly 3.7 if it makes it easier, and then ask if it's OK. Worst that can happen is you'll be asked to update it. Remember it's easier to ask forgiveness.

@pakio pakio closed this Jun 26, 2023
Fernando-crz pushed a commit to Fernando-crz/pipreqs that referenced this pull request Oct 9, 2023
Fernando-crz pushed a commit to Fernando-crz/pipreqs that referenced this pull request Oct 17, 2023
Fernando-crz pushed a commit to Fernando-crz/pipreqs that referenced this pull request Oct 17, 2023
Fernando-crz pushed a commit to Fernando-crz/pipreqs that referenced this pull request Oct 17, 2023
Commit rebased from bndr#210 .
Credits to: pakio https://github.com/pakio

fix coverage report bug

updated nbconvert version

fixed lint issues

add black formatting rules
mateuslatrova pushed a commit to pipreqsxp/pipreqs that referenced this pull request Nov 23, 2023
Commit rebased from bndr#210 .
Credits to: pakio https://github.com/pakio

fix coverage report bug

updated nbconvert version

fixed lint issues

add black formatting rules
mateuslatrova added a commit to pipreqsxp/pipreqs that referenced this pull request Nov 27, 2023
Commit rebased from bndr#210 .
Credits to: pakio https://github.com/pakio
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

Successfully merging this pull request may close these issues.

None yet

3 participants