this post was submitted on 08 Nov 2024
234 points (97.2% liked)
Programmer Humor
32572 readers
200 users here now
Post funny things about programming here! (Or just rant about your favourite programming language.)
Rules:
- Posts must be relevant to programming, programmers, or computer science.
- No NSFW content.
- Jokes must be in good taste. No hate speech, bigotry, etc.
founded 5 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Jupyter notebooks can totally handled by git! If you use GitHub, it will even render them on the WebUI for you.
I'm my past job we had Azure-devOps, i tried to upload an jupyter notebook but it didn't recognized it was a jupyter notebook and show the file as a JSON and it was not nice to work with, I had to export the notebooks as python scripts to get it working fine. In my new job, I'll still waiting for the IT team to approve and set up something for me.
Don’t wait. Come talk to us. Yeah things are hectic with demands flooding in from all directions but we want to make your job easier and better
The ticket is already open and I guess on the queue, and I already have a couple of more important tickets at front (some databases I want to access directly from python, instead of having to use excel to generate the queries and the export from it).
I don't know if DevOps can render them. It certainly can't on my system. I would recommend not using the remote repository WebUI for that feature.
In this new job I'm also looking up for the devops access (they even have github completely blocked on the corporate network) and I'm hoping I can connect it somehow with VS Code (in the pass one I couldn't)
With jupyter notebooks in a devops perspective you could just build a process to export the notebooks to standard py files and then run them.
There are actually a lot of git hooks that will actually expoet/convert .ipynb to .py files automatically since notebooks don't work great with git.
VS code can export and import from a to jupyter notebooks, but there's some kind of bug and the imported notebooks always keep a ## % on each cell (not a high deal, but is annoying because subsequent exports/imports think they are cells to be created)