mcdonc

18 ms·

1.
The NixOS Conflict in Under 5 Minutes(chrismcdonough.substack.com)
9 points by mcdonc 2y ago|0 comments
2.
by mcdonc 13y ago
But it has Zope in its name!!!111!! ;-)
3.
by mcdonc 13y ago
It's best to keep object records small when using ZODB. This does mean you need to do some planning about object structure. Objects that inherit from "persistent.Persistent" are kept as separate records in ZODB, so you can
4.
by mcdonc 13y ago
It does not unpickle every time you get something from cache. It maintains a first-level in-memory LRU per-thread object cache which is the actual Python object (not its pickle representation). In practice, that means you don't need
5.
What's New in Pyramid 1.3 (Python 3 web framework) (docs.pylonsproject.org)
5 points by mcdonc 15y ago|0 comments
6.
by mcdonc 15y ago
The pragma wouldn't really work. It'd have to work in all old versions of Python to make any sense, and it doesn't. For unicode literals in particular, it should just be true in Python 3.3+ that u'' = '' out of the box.
7.
by mcdonc 15y ago
Amen, 2to3 in practice for anything but the smallest library is effectively unusable due to speed. Even if it weren't, I'm not much of a fan of maintaining generated code. That's an imposition I'm not really willing to put up with.
8.
by mcdonc 15y ago
Your original post (and to an extent your reply above) was a bit dismissive, I think. Dismissiveness is not really a unique sentiment here; I see a lot of posts along the lines of "well yes he's complaining but it's a break with the past a
9.
by mcdonc 15y ago
http://docs.python.org/release/3.2.2/library/stdtypes.html#b... And this annoying feature: http://docs.python.org/dev/howto/pyporting.html#indexing-byt...
10.
by mcdonc 15y ago
Well, the author has direct experience porting and maintaining (very popular, well-written, well-tested) Python libraries, so I think it bears more weight than the platitudes I hear from "the other side" of "it will all work out in the end,
11.
by mcdonc 15y ago
It's not splitting hairs at all. It's the definition of the pattern. The pattern was created for stateful UI systems, and it can't be emulated with request-response frameworks without UI state kept on the client side. But that said, the f
12.
by mcdonc 15y ago
Wow, great way to take criticism! Thank you.
13.
by mcdonc 15y ago
The order the decorators are run at import time is explicit. Everybody loves module-scope programming and import-time side-effects! What's wrong with you man? ;-)
14.
by mcdonc 15y ago
this ^^
15.
by mcdonc 15y ago
Bottle and Flask actually allow for this too. Bottle's variant: @route('/hello/:name', method='GET') def hello_get(name): return 'Hello %s' % name @route('/hello/:name', method='POST') def hello_post(name): ret
16.
by mcdonc 15y ago
In a more traditional Pyramid app it would be done more like: from pyramid.view import view_config from pyramid.response import Response from paste.httpserver import serve @view_config(route_name='hello') def hell
17.
by mcdonc 15y ago
Seems appropriate to link this here: https://docs.pylonsproject.org/projects/pyramid/1.2/designde...
18.
by mcdonc 15y ago
Comments with critical, dogmatic hyperboles in them like this drive me nuts in general. Here are the hyperboles in this comment with the translations to normal English. - "saddled with any dependency baggage" == "has no dependencies" - "be
19.
Pyramid (Python Web Framework) v1.1 Released(docs.pylonsproject.org)
2 points by mcdonc 15y ago|0 comments
20.
by mcdonc 15y ago
Still a troll.
21.
by mcdonc 15y ago
indeed, kick-ass
22.
by mcdonc 17y ago
Got it. "Advertising" problem, not an actual problem then.
23.
by mcdonc 17y ago
I'm the primary author of said nonsense. I didn't do TDD on this project, for the record. So was my mistake in actually writing these tests or was it just advertising them? ;-)