Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

From Python to Numpy

labri.fr

Post reply on HN
Print view View original

31–40 of 55 posts

Re: From Python to Numpy

#31

Post by syntaxing »

Nicolas-Rougier wrote: post #23
syntaxing wrote: post #17

Does anyone have a recommendation for something similar to this but for Python itself? I have been trying to find something that is not necessarily an intro or crash course book but a book with tips, great explanations, and neat examples (which this e-book(?)/site has). I see that the author has responded to a couple comments here. Thank you for your great work! It's always great to have a nice reference material wit…

Thank you. For some Python introduction, you can have a look at the end of this page: https://github.com/rougier/Scipy-Bordeaux-2016/blob/master/i...

Thank you for the suggestion!

Re: From Python to Numpy

#33

Post by bcbrown »

syntaxing wrote: post #17

Does anyone have a recommendation for something similar to this but for Python itself? I have been trying to find something that is not necessarily an intro or crash course book but a book with tips, great explanations, and neat examples (which this e-book(?)/site has). I see that the author has responded to a couple comments here. Thank you for your great work! It's always great to have a nice reference material wit…

I'm skimming through Effective Python, and so far I think it's a pretty good "best practices" guide for intermediate Python developers.

Re: From Python to Numpy

#34

Post by omaranto »

tomrod wrote: post #26
JeremyBanks wrote: post #10

Earlier quoted context omitted.

Optimizing for super-rare users who have a deliberate desire for long lines is less important than optimizing for the vastly-more-common case that the browser's size is large as an artifact of content the user was viewing on a previous site, but the user still prefer a sane line length for text content.

Citation that these users are super rare? Almost everyone I've had conversations with on the subject bemoan too large margins on websites.

That's odd. I wonder if these people that like looong lines are mostly younger people that have read more from screens than books (but not so young that they've read more from phones than computer screens :))? A book with very long lines would be super weird.

Re: From Python to Numpy

#35

Post by zellyn »

Anyone (author) know what was used to generate the cover image of cubes and shadows?

Edit: it's sketchup - there's a .skp file in the data/ subdirectory of the github repo for the book.

Re: From Python to Numpy

#36

Post by skadamat »

syntaxing wrote: post #17

Does anyone have a recommendation for something similar to this but for Python itself? I have been trying to find something that is not necessarily an intro or crash course book but a book with tips, great explanations, and neat examples (which this e-book(?)/site has). I see that the author has responded to a couple comments here. Thank you for your great work! It's always great to have a nice reference material wit…

Hey I work at Dataquest (dataquest.io) and we have a lot of intermediate & advanced Python content. It's all done through an in-browser coding environment which lets us do answer checking and so on.

Re: From Python to Numpy

#37

Post by NoahTheDuke »

bcbrown wrote: post #33
syntaxing wrote: post #17

Does anyone have a recommendation for something similar to this but for Python itself? I have been trying to find something that is not necessarily an intro or crash course book but a book with tips, great explanations, and neat examples (which this e-book(?)/site has). I see that the author has responded to a couple comments here. Thank you for your great work! It's always great to have a nice reference material wit…

I'm skimming through Effective Python, and so far I think it's a pretty good "best practices" guide for intermediate Python developers.

Seconded. `Effective Python` is a fantastic resource detailing a lot of the ways Python differs from other languages and how to write to the language's strengths.

I'm no hot shit, but it definitely moved me from 'middling hobbyist' to 'semi-capable dev'.

Re: From Python to Numpy

#38

Post by joshvm »

syntaxing wrote: post #17

Does anyone have a recommendation for something similar to this but for Python itself? I have been trying to find something that is not necessarily an intro or crash course book but a book with tips, great explanations, and neat examples (which this e-book(?)/site has). I see that the author has responded to a couple comments here. Thank you for your great work! It's always great to have a nice reference material wit…

There's Fluent Python from OReilly which is a pretty good follow-on for people who are comfortable with the basics and want to know dig into some more advanced features:

http://shop.oreilly.com/product/0636920032519.do

Re: From Python to Numpy

#40

Post by darkseas »

grej wrote: post #11

As someone who has used numpy for many years and written a great deal of production code using it, I was surprised when I read through this and saw some numpy tricks that I didn't know regarding the speeds of various operations! This is really a fantastic reference that provides a deeper level of understanding of what numpy does under the hood. One thing I will highlight that the author just touched on briefly, is th…

Can I ask how intensively you have used Numba and over what period? I'm interested in how Numba has progressed over the last few years, with a view to using it over Cython.

My team and I looked at Numba a year ago or so for optimisation of a fairly large calculation, and found that the speed-ups were impressive where they worked, but were not consistent or predictable.

We used Cython for large parts, and while there was boilerplate and incantations, the gains were achievable, incremental and certain. The annotation tools were also quite helpful for identifying bottlenecks where Cython code could be effective.

Incidentally, once we decided that Cython was our go-to tools, we often wrote simple looping code rather than vectorised code because it was simpler to transition to Cython, alá Julia.

Post reply on HN