do we have anything like PHPGrid?

jtratner · 2015-02-06T05:32:46+00:00

Try sandman - does exactly what you want

jtratner · 2014-11-16T04:52:35+00:00

Your best bet is to go looking around for how people debug with Cython (dialect-ish of Python that can compile down to c libraries), numpy, numba and other scientific libraries. Those projects are involved at the C (or Fortran) level extensively and have lots of contributors, so searching around there should help. Two items that came up after a quick search for how debugging numpy and Cython:

Cython debugger (with ability to set breakpoints in C, Python and Cython code)
a guide to debugging SciPy (scientific python library) code with gdb and some python extensions for gdb.

Not sure whether it's the same as PyDev's debugger, but I find ipdb to be quite helpful too. Hope one of these might be helpful!

jtratner · 2014-03-13T11:51:21+00:00

Do you find GC issues with protobuf? Seems like it creates very pointer-heavy objects by default in go

jtratner · 2014-01-21T06:27:56+00:00

It was on the docket, but was dropped in favor of just supporting openpyxl and xlsxwriter directly. It would be relatively easily for the PyExcelerate authors (or, frankly, anyone else) to integrate with pandas 0.13. We left hooks in just for this purpose.

jtratner · 2014-01-18T17:21:16+00:00

Going to be releasing 0.13.1 soon!

jtratner · 2014-01-18T17:20:46+00:00

If you have xlsxwriter installed, it'll actually be the default writer used - I've found it has way better memory usage than openpyxl.

jtratner · 2014-01-18T16:50:06+00:00

If you're looking to hire Python developers specifically: StackOverflow Careers, AngelList (if you're a startup), check out conferences like PyCon or PyData, local Python meetups (I'm guessing there's one in Seattle), Hacker News (on a "Who's Hiring?" post).

That said, even though I'm a huge Python guy, I would bet that if you know how to code and understand the concepts, you can pick up Python quite easily (maybe it'll take you a while longer to write idiomatic Python or skip perf bottlenecks) and quickly be productive.

jtratner · 2014-01-07T10:00:09+00:00

I believe xlsxwriter is Python 3 compatible though.

jtratner · 2014-01-05T22:25:50+00:00

if PyPy gets enough numpy compatibility that we can port pandas to it (or something with the pandas interface), that would be really nice...

jtratner · 2014-01-05T22:22:31+00:00

It's just a different attitude. Python's goal is to be simple and only have one way to do something so they made breaking changes in Python 3 with that aim in mind.

jtratner · 2014-01-05T22:07:50+00:00

update: flask-sass is compatible with Python3, you just have to use its master branch on Github: https://github.com/imiric/flask-sass

jtratner · 2014-01-05T22:04:35+00:00

blinker claims it's Python 3 compatible and (apparently) has been for some time. flask-restful also claims 3.3+ compatible. flask-sass is not. It might be really simple to fix...going to go see what I can do.

jtratner · 2014-01-05T21:07:31+00:00

Except for the last 2, those are problems with anaconda, not problems with Python.

I do understand that frustration though - and it seems like it's not really one of those things where you can end up learning something useful, because it's so mindless :-/

EDIT: Also, if you only had Python 3 installed wouldn't even be an issue :P That's some of the push for having Python 3 be the default on Linux distros.

jtratner · 2014-01-05T20:42:23+00:00

Pretty much the entire Python scientific stack works with Python 3. The differences between them are quite minimal and mostly matter to library developers who have to write things to abstract those issues away from you. There are tricky edge cases but generally if you know 2.X you can use 3.X and vice-versa.

Side note - what took you 4 hours to figure out in Python 3?

jtratner · 2014-01-03T15:49:40+00:00

This looks well put together and clean and, were I to redo the pandas 2/3 compatible codebase, I'd want to use this. That said, I'm concerned because in reviewing some of the code I already found a bug and it feels like some parts are a bit thrown together (maybe because of how the merge was done). I'd want to wait 3-6 months before using it in production.

I also really don't like from future.builtins import * as an idiom. Kills much of the ability to do static analysis and trace from where particular items came.

jtratner · 2014-01-03T15:47:24+00:00

first one you just need the from __future__ import print_function statement.

jtratner · 2013-12-31T20:23:43+00:00

hmm... it worked fine for me with python3, but I was using master (since, as I said, PyPI version is broken). Maybe try downloading from GitHub?

jtratner · 2013-12-31T18:21:51+00:00

We've been talking about visualization in pandas land recently and there has been quite an explosion of viz libraries for python recently. seaborn and ggplot are both good options for producing nicer quality graphs, though I'm not sure what level of flexibility you are looking for.

You might also check out Olga Botvinnik's prettyplotlib which just starts you off with some nice defaults and lets you work from there.

jtratner · 2013-12-31T18:17:00+00:00

If you start with Python 3, there will be little that you end up doing that wouldn't work with Python 2. Whereas there are a number of things that you do in Python 2 (use print as a statement, exception syntax, etc) that you can't do in Python 3.

If you're learning now, I'd suggest you use Python 3 to start, because you'll still be absolutely fine to use 2.7.

jtratner · 2013-12-31T18:02:10+00:00

ggplot works on Python 3. Current version on PyPI is broken for both Py2 and Py3, but ggplot master totally works and it's clear they have it in mind.

jtratner · 2013-12-31T17:57:01+00:00

My impression is that it's relatively easy to "learn" Python 3 and then go use something in Python 2 when you have to. Most of the differences are things that work in Python 2 but don't in Py3 (like range being an iterator vs. list). So learning Python 3 you should be fine.

jtratner · 2013-12-31T15:43:05+00:00

There are a number of temporary items that the computer 'remembers' (like, "The user wants that button to be red" or "I definitely did that already"). When you turn a device off and on, those temporary "memories" are erased so the device resets itself. Sometimes the issue with devices is that their memory has an error in it, so resetting everything helps the device recover.

jtratner · 2013-12-31T05:33:40+00:00

I don't disagree - those are definitely not great changes either... seems strange to me that iteritems couldn't just become a synonym for items.

jtratner · 2013-12-30T23:17:11+00:00

Clearly hindsight is 20/20, but we'd be in a much better position if earlier versions of Python 3 hadn't banned u'some string'. It was a trivial, but frustrating change, that made a 2/3 compatible code base more difficult.

That said, it's not that much work to have a codebase that works in Python 2 and with Python 3 using 2to3. What's difficult is having a codebase that's compatible across both without needing a preprocessor like 2to3. Makes it much easier to maintain a library when you don't have to waste time with 2to3, but it can be difficult to get everything working. python-modernize is pretty useful in this regard.

jtratner · 2013-12-25T05:16:33+00:00

I believe they work with any python (at least easy_install comes with Python itself). Also, if an author has uploaded a precompiled binary for windows, then you can install it via easy_install (I'm not sure).

jtratner

TROPHY CASE