shmeedogg

5 ms·

1.
Evicted in San Francisco(priceonomics.com)
227 points by shmeedogg 13y ago|252 comments
2.
by shmeedogg 14y ago
Agreed, I think the distinction between a bound method or a function is irrelevant here. If we want explicit kwargs (a big 'if' since many of the suggestions in this thread are to give up on that idea), then we need some value to distinguis
3.
by shmeedogg 14y ago
> Whether a field is modifiable is often determined by the current user's access level and the current state of the object. So, putting such restriction at the function definition may have made things too rigid. True, let me try to clar
4.
by shmeedogg 14y ago
I'd love to see this integrated into the language and live along side of `None` (I can dream, can't I?) But until then, how can two different libraries agree to use the exact same instance of `NotSet` without some standard package defining
5.
by shmeedogg 14y ago
To my ear, this does sound the best. Thanks for the suggestion!
6.
by shmeedogg 14y ago
Interesting. I love the idea of not having to import an external library, but much like the `NotImplementedError` suggestion, it overloads a value that already has a specific meaning, in this case related to slice-notation. I'd worry that t
7.
by shmeedogg 14y ago
> whereas a function with a signature will need its arguments changed whenever the database schema changes. True there is some work in keeping the two synchronized, but there are benefits. First, unexpected arguments are immediately cau
8.
by shmeedogg 14y ago
The implementation here is just a suggestion, and trust me, it wasn't much effort ;-) The aspect that interests me is that this is a problem that crops up occasionally in different Python projects and there doesn't seem to be a recognized b
9.
by shmeedogg 14y ago
That example could probably use some clarification, but the idea is that `name` and `age` in that example are both nullable, so passing in `None` (setting the column to NULL) is different than omitting the value (leaving the column unchange
10.
by shmeedogg 14y ago
Uppercase was chosen to match Python's existing singletons, `True`, `False`, and `None`. Lowercase might look a little too much like a variable, and all-upper might look too much like a module-level const, IMHO.
11.
by shmeedogg 14y ago
Agreed. 'Empty' works, as does 'Blank' or 'Unassigned'.'Nil' is concise, but might be a little too easily confused with 'None' (especially so for someone coming from Ruby). I'd love an approach that used the standard library, but there does
12.
Notset: A Do-Not-Care value for Python(github.com)
30 points by shmeedogg 14y ago|38 comments
13.
Show HN: Mockstrap, a Twitter Bootstrap Sandbox(mockstrap.com)
2 points by shmeedogg 15y ago|1 comments
14.
by shmeedogg 16y ago
Fixed, thanks!
15.
by shmeedogg 16y ago
Oops, that's a typo in code that hasn't been deployed yet. Our regression suite missed it ;-)
16.
by shmeedogg 16y ago
reallyslowsite.com is designed to be a tool that developers can use to simulate how their application responds to expensive HTTP requests. You could use this, for example, to test that your mobile application is properly caching HTTP reques
17.
ReallySlowSite.com(reallyslowsite.com)
1 points by shmeedogg 16y ago|0 comments
18.
by shmeedogg 16y ago
http://longform.org/
19.
"A sleep(1) is put into all SSL_read() and SSL_write() calls..."(bugs.python.org)
105 points by shmeedogg 16y ago|50 comments