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

'New' Python modules of 2015

blog.rtwilson.com

Post reply on HN
Print view View original

51–60 of 137 posts

Re: 'New' Python modules of 2015

#51

Post by sandGorgon »

gh02t wrote: post #48
wclax04 wrote: post #33

Earlier quoted context omitted.

It slightly lags, but you can include pip requirements in an environment.yml file, and they install normally. I really only use conda for the non-python bits of our stack: numpy/scipy/pandas etc - packages that are a pain to install on Heroku.

It's also pretty straightforward to set up your own Conda package tree. Nice for packaging your app for deployment or making sure you have very precise dependencies. http://conda.pydata.org/docs/custom-channels.html

I think deployment is a solved problem with docker. Its libraries like blas,etc that are a huge pain. I'm not sure why static linked bumpy is not possible - even anaconda could not achieve it.

Re: 'New' Python modules of 2015

#53

Post by StavrosK »

wesleyy wrote: post #42
scrollaway wrote: post #4

Not really 2015 but Q! https://pypi.python.org/pypi/q Print-debugging on steroids. This really does make things so much easier, especially when dealing with huge apps you don't have time to learn. Not just useful as a dev but also as a sysadmin.

What's the advantage of Q over pdb?

First of all, pudb is fantastic, just use it over pdb all the time.

q is for when you want to log data, pudb is for when you want to step through and evaluate lines in-context. It's very possible that you'll want to use both together.

Re: 'New' Python modules of 2015

#54

Post by sandGorgon »

dwiel wrote: post #34
sandGorgon wrote: post #32

Earlier quoted context omitted.

So I have been considering this. does conda track pypi or does it lag it? I have been concerned about moving over my requirements.text for a webapp with lots of dependencies

We have to use a mix of pypi and conda since quite a few of our dependencies are not in conda. We have a script which checks conda first, then falls back to pypi, all from one requirements.txt

Why not conda all the way? Anything of concern?

Incidentally is the buildscript of anaconda itself opensource? Couldn't find it anywhere.

Re: 'New' Python modules of 2015

#55

Post by StavrosK »

Hands down, my favorite new library is schema:

https://pypi.python.org/pypi/schema

Here's a schema I use in production, see how readable it makes the parameters of the API and how quick all the validation and normalization is:

https://www.pastery.net/mhwwnv/

At the end, you get an object called data, and you can do data.title, data.language, etc, and be sure that everything is as you expect.

Re: 'New' Python modules of 2015

#56

Post by chestervonwinch »

teekert wrote: post #26

I'm feeling a lot of love for Pandas. Any (biology related) project I work on starts with multi-headered dataframes and ends in beautiful Seaborn graphs. In combination with Jupyter notebook I breeze through large data sets while leaving a perfect trail of what goes on in the data pipeline. Python is great.

For those interested, you can also get nice styles with just matplotlib (including seaborn style) using stylesheets:

http://matplotlib.org/users/style_sheets.html

Re: 'New' Python modules of 2015

#57

Post by [deleted] »

StavrosK wrote: post #55

Hands down, my favorite new library is schema: https://pypi.python.org/pypi/schema Here's a schema I use in production, see how readable it makes the parameters of the API and how quick all the validation and normalization is: https://www.pastery.net/mhwwnv/ At the end, you get an object called data, and you can do data.title, data.language, etc, and be sure that everything is as you expect.

[deleted]

Re: 'New' Python modules of 2015

#58

Post by lsh »

StavrosK wrote: post #55

Hands down, my favorite new library is schema: https://pypi.python.org/pypi/schema Here's a schema I use in production, see how readable it makes the parameters of the API and how quick all the validation and normalization is: https://www.pastery.net/mhwwnv/ At the end, you get an object called data, and you can do data.title, data.language, etc, and be sure that everything is as you expect.

Any relation to the Clojure Schema? https://github.com/Prismatic/schema

Re: 'New' Python modules of 2015

#59

Post by StavrosK »

lsh wrote: post #58
StavrosK wrote: post #55

Hands down, my favorite new library is schema: https://pypi.python.org/pypi/schema Here's a schema I use in production, see how readable it makes the parameters of the API and how quick all the validation and normalization is: https://www.pastery.net/mhwwnv/ At the end, you get an object called data, and you can do data.title, data.language, etc, and be sure that everything is as you expect.

Any relation to the Clojure Schema? https://github.com/Prismatic/schema

Possibly? It certainly looks similar.

Re: 'New' Python modules of 2015

#60

Post by gh02t »

sandGorgon wrote: post #51
gh02t wrote: post #48

Earlier quoted context omitted.

It's also pretty straightforward to set up your own Conda package tree. Nice for packaging your app for deployment or making sure you have very precise dependencies. http://conda.pydata.org/docs/custom-channels.html

I think deployment is a solved problem with docker. Its libraries like blas,etc that are a huge pain. I'm not sure why static linked bumpy is not possible - even anaconda could not achieve it.

If you've ever tried to dive into the NumPy build process you'd see why. It's unbelievably complicated... not that they really could do it better given that they are compiling about a billion scientific libraries and support alternatives and optimizations (like MKL).
Post reply on HN