Mailman 3 June 2013 - Pandas-dev

github pulse
by Phillip Cloud June 27, 2013

June 27, 2013

is there something weird in gh pulse? there's no way that i have 63 commits in the past week. i only have 98 commits overall and git log --oneline --no-merges --author='Phillip Cloud' --since='1 week ago' | wc -l yields 14 just want to make nothing fishy is going on... -- Best, Phillip Cloud

2 1

can we revive the nightly builds?
by Jeff Reback June 26, 2013

June 26, 2013

https://github.com/pydata/pandas/issues/3777#issuecomment-20010594

3 2

Upcoming release as 0.12 instead?
by Wes McKinney June 26, 2013

June 26, 2013

This release already getting quite large, and jam-packed with new functionality like pandas.json. The release numbers are indeed fairly arbitrary but there's good psychology around "the release merits an upgrade"; any thoughts? - Wes

3 5

Getting more community feedback into the GH issue tracker
by yoval p. June 25, 2013

June 25, 2013

tl;dr version: how about adding a pd.report_issue()/pd.feedback() function? *steps on soapbox* 9 times out of 10, GH issues are what brings about code changes in pandas, whether it's bugfixes or features. I'm very proud to be a commiter on an OSS that has a proven track record of being extremely responsive to users in support and in feature enhancements. I think that's what makes pandas such a great OSS project just as much as technical excellence, versatility and plain ol' just feeling good in your hand (behave). How can get we get feedback from more users of pandas, specifically those without a GH account and turn it into GH issues? Experience shows it's surprisingly often that the issue/features suggested by users are fairly simple to implement, if only we hear about it. Those kinds of changes immediately translate into making our users more productive. Which is a large part of what fosters such a fanatical community, which we do love so. Not everyone has a GH account and while SO is great (+ @hayd, @jreback et al migrate things over as needed) that also covers only a certain kind of pandas user. Is it enough? are we missing out on our silent users? I suspect some (many?) pandas users hit a snag or have an idea for a feature and we never hear of it, to our dismay. We're certainly not anxious about having lots of open issues, so why not? Would integrating some feedback mechanism directly into the library help fix this? It could be a dialog or a web page, launchable directly from the console that either redirects users directly to the "new issue" page, but could also let them just send in some structured text that we can send somewhere and review. Bad idea? Good idea? is SO all we need? do you have a better idea? So many things in pandas are oneliners. why isn't feedback one as well? yoval

3 2

docs - clipboard reading not working for some reason?
by Jeff Reback June 21, 2013

June 21, 2013

change, I have xclip installed (also xsel), but don't think that's used.... http://pandas.pydata.org/pandas-docs/dev/io.html#clipboard

1 0

Getting my attention
by Wes McKinney June 18, 2013

June 18, 2013

hey all, really excited to see so much rapid development going on in pandas the last few months. you guys are the best! I've figured out that I've been missing a lot of @wesm mentions since I created an email filter as the chattiness of github has increased (see attached plot of smoothed "issue chattiness over time"). Don't be less chatty! I finally fixed my gmail filter to not hide threads that contain an @wesm in them so I will be a bit more responsive to questions/queries from now on. thanks, Wes

1 0

docs
by Jeff Reback June 14, 2013

June 14, 2013

Chang can u install xclip on your doc build machine (I believe u r on Linux) the new clipboard in docs uses this thxs Jeff I can be reached on my cell 917-971-6387

2 2

0.11.1
by Jeff Reback June 6, 2013

June 6, 2013

congrats to Phillip! all of the html parsing has been merged in and clean (and fallback is now pretty nice) docs have lots of warnings/instructions so seems ok other than the single remaining issue about plotting I think 0.11.1 ready 2 go

2 2

pydata membership
by Phillip Cloud June 6, 2013

June 6, 2013

Hey guys, I was wondering how I can become a member of the pydata organization on GitHub. Jeff and I had a 2 second conversation about this on GitHub <https://github.com/pydata/pandas/pull/3741>, but I wasn't sure what the next steps were so I thought I would bring it up on the mailing list. -- Best, Phillip Cloud

2 2

Fwd: [Bug 1181905] Re: tr elements are not parsed correctly
by Phillip Cloud June 3, 2013

June 3, 2013

This is the reply I got from the lxml people about an "incorrect" parse of the failed bank list page. It wasn't actually an incorrect parse, the page has invalid markup and lxml makes no promises about that. Moral of the story: only use html5lib when parsing HTML tables. Should I reopen the lxml functionality then, with a big honking error in the documentation telling users to tidy up the HTML they want to parse if they want to use lxml or just scrap the lxml functionality entirely? No need to clutter up the codebase. -- Best, Phillip Cloud ---------- Forwarded message ---------- From: scoder <1181905(a)bugs.launchpad.net> Date: Sun, Jun 2, 2013 at 2:14 AM Subject: [Bug 1181905] Re: tr elements are not parsed correctly To: cpcloud(a)gmail.com The HTML page doesn't validate, even my browser shows me an HTML error. The <td> tag you are looking for is not inside of a <tr> tag, so it's actually correct that the last two tests in your script fail because they are looking for something that's not there. If you think that the parser in libxml2 should be able to fix this HTML error automatically, rather than just parsing through it, please file a bug report for the libxml2 project. Alternatively, adapt your script to the broken HTML or use an HTML tidying tool to fix the markup. ** Changed in: lxml Status: New => Invalid -- You received this bug notification because you are subscribed to the bug report. https://bugs.launchpad.net/bugs/1181905 Title: tr elements are not parsed correctly Status in lxml - the Python XML toolkit: Invalid Bug description: Python : sys.version_info(major=2, minor=7, micro=5, releaselevel='final', serial=0) lxml.etree : (3, 2, 1, 0) libxml used : (2, 9, 1) libxml compiled : (2, 9, 1) libxslt used : (1, 1, 28) libxslt compiled : (1, 1, 28) See the attached script. The url http://www.fdic.gov/bank/individual/failed/banklist.html is not parsed correctly by lxml. the element containing 'Gold Canyon' is just left out, while all of the other elements seem to be there. To manage notifications about this bug go to: https://bugs.launchpad.net/lxml/+bug/1181905/+subscriptions

3 15