It seems to be a nice introduction to numpy, pandas, and matplotlib
Python Data Science Handbook: Full Text in Jupyter Notebooks
11–20 of 37 posts
Re: Python Data Science Handbook: Full Text in Jupyter Notebooks
#12Any reviews on this ?
For me, it is one of the best books for beginners. It covers almost completely from numpy, pandas, matplotlib/seaborn to ML algorithms.
Re: Python Data Science Handbook: Full Text in Jupyter Notebooks
#13Any reviews on this ?
This is the first book on the subject matter which I actually finished. When I started using it, I was completely noob in data analysis/ml.
Personally I'd say this is a good book. Sections dealing with Numpy, Pandas and Matplotlib are great.
However, I am hesitant to say the same about ML section. I felt like this book assumes some familiarity with general ML concepts. I also felt like ML chapters progressed a bit fast from beginning to the core of chapter.
In all, book is great. Sections on Numpy, Pandas etc are great. But as for ML section, don't use that section as an introduction/first course for ML.
Re: Python Data Science Handbook: Full Text in Jupyter Notebooks
#14Is there a way to run notebooks automatically, so you could regenerate notebooks like this after some library code changes or dependency upgrades and check that everything stillw orks?
Re: Python Data Science Handbook: Full Text in Jupyter Notebooks
#15Is there a way to run notebooks automatically, so you could regenerate notebooks like this after some library code changes or dependency upgrades and check that everything stillw orks?
Yep, Jupyter notebooks have an execution API, you can find more of it here - https://nbconvert.readthedocs.io/en/latest/execute_api.html. Hosted notebooks as a service is a growing area of investment and those services presumably use this API.
Re: Python Data Science Handbook: Full Text in Jupyter Notebooks
#16Is there a way to run notebooks automatically, so you could regenerate notebooks like this after some library code changes or dependency upgrades and check that everything stillw orks?
There's the nbval plugin for pytest. https://nbval.readthedocs.io/en/latest/ I've used that in one of my packages (https://github.com/qucontrol/krotov) to verify example notebooks on every push, on Travis CI
Re: Python Data Science Handbook: Full Text in Jupyter Notebooks
#17Any reviews on this ?
I have a fair amount of experience with pandas, and find the notebooks very help to refer to! I would say it's worth noting that his book is organized by technology (e.g. numpy, then pandas, then plotting), which makes it feel more like a technical reference, than a walk-through of basic to advanced DS activities. It's also worth checking out the notebooks for Wes McKinney's data science book. Daniel Chen doesn't hav…
An incredibly critical review of McKinneys book can be found here: https://medium.com/dunder-data/python-for-data-analysis-a-cr...
Re: Python Data Science Handbook: Full Text in Jupyter Notebooks
#18Is there a way to run notebooks automatically, so you could regenerate notebooks like this after some library code changes or dependency upgrades and check that everything stillw orks?
At the very least you can use the command line tool to run/export them.
Re: Python Data Science Handbook: Full Text in Jupyter Notebooks
#19I also recommend checking out the open source Automunge tool for automated data wrangling at automunge.com
Is this an advertisement?
Some ideas / questions: - The documentation on GH is unreadable like this - On GH it says "Patent Pending" so is this not open source after that or is that phrase just a joke? - How is it related to the mentioned Data Science Handbook?
Re: Python Data Science Handbook: Full Text in Jupyter Notebooks
#20Earlier quoted context omitted.
Or maybe you should spend time on it, by creating a fork with all the good PRs applied?
I would probably do that if the time investment was worth it. For example if it was something I was using on a day to day basis but not for leisurely/exploratory reading.
Even for leisurely reading, you expect an author to still be updating a book several years after it was published? What experience has led you to believe that's a reasonable expectation?