Yep django-toolbar is great! My aim with this was, like you said, to provide the history of multiple requests, but also to provide finer-grained profiling with the decorator and context manager. Not only do they capture execution time but they also capture the queries that were executed whilst they were active. The aim was extra visibility all round really.
Not at the moment. Silk doesn't actually save anything down until right at the end of the cycle i.e. in process_response of the middleware. Had to do this to avoid issues with atomic transactions. I certainly don't mind adding this as a feature if people would find that useful - perhaps by detecting that no request is in process and then commiting profile data on the fly if that's the case.
Thats a great question... that def shouldn't be there. render_to_response is actually dynamically profiled i.e. the decorator is applied at runtime via configuration in settings.py. This looks like its probably a bug with that. Cheers, will look into it
Yep, just upgraded mine to Mavericks and had absolutely no issues. You just need to make sure you buy components that are tried and tested by the hackintosh community.
Never. To upgrade to Mavericks I just created a USB installer using unibeast, booted from USB and followed the usual OSX install process. All my files and apps were left untouched.
I do a lot of heavy Django work and first glance I really like the syntax. Much cleaner that what I'm used to. I will def give this a try at some point and comment further.
Why the name PonyORM btw? I know it's superficial but I much prefer the name SQLAlchemy - has more meaning.
The idea of Pony ORM is to provide a Pythonic way to work with the database. We think that the generator syntax is very concise and convenient.
It is named Pony because a pony is a small, smart and powerful creature - these are the features which our mapper has.
Our goal is to provide non-leaky abstraction and good user experience.
Looks like it's down, and the official links for download don't seem to work anymore. It's available here on github tho: https://github.com/mozilla/Fira
Has anyone actually been rejected for this yet? How do we know there isn't a whitelist already? We're submitting in a weeks time - with mogen - so I guess there is only one way to find out...
Nobody is being rejected for this issue — Apple seems to be ignoring it as overzealousness from the validator. It's just a validation warning, but you'd be amazed how upset some developers get about it.
We've had numerous issues filed about it on the MagicalRecord issue tracker (which is what prompted me to hassle Wolf about it in the first place).
Its def slower. I do like atom, however I tend to end up doing a lot of heavy log crunching. Atom will stutter and crash whereas sublime breezes through anything I can throw at it.
