Daniel Robinson

This bug is due to the way ParsePy currently saves Objects--by sending a PUT request with the entire object's data, thus resaving every field. The way other SDKs (such as...

I think this is a very good idea (and one that I believe Hayden's thought about as well). ~I believe this is the formula you're looking for (incorporating fees):~ EDIT:...

You can already do that by doing the calculation and placing a normal market order that fails if it gets worse execution than expected. The usefulness of adding this function,...

> I'm interested in your thoughts on front-running this type of transaction. I imagine that frontrunners would be incentivized to buy the first half of your order before you, then...

Good news: the formula I derived above was wrong, and the true formula is much simpler! (The error is that I was assuming the marginal price of adding to the...

+1. I agree that using `-` to drop columns in `select` is a little weird anyway. I might prefer a special function like `except` that works within `select` (much like...

I think the second is perfectly Pythonic. In an ordinary conditional, `if points` is more idiomatic than `if points != 0`, isn't it? I think `dfilter` should just be `filter`....

The `eval` option is definitely intriguing, assuming there aren't unavoidable performance or security implications. Maybe it could be an option, alongside functions/lambdas and Laters? So a mutate could be done...

While the first option would work and would be unambiguous if all queries were strings that were eval'd, I think we would still want to support a non-eval option. So...

Fair enough, although I'll note that the string evaluation method would save keystrokes on more complex expressions like `mutate(cost="price / carat")`.