On Fri, Jul 18, 2014 at 7:32 PM, Daniel Pyrathon wrote:
> *- Started on my GMail Store*
> While I was waiting for review, I have started an implementation of my
> GMail store. The implementation is documented here (
> https://docs.google.com/document/d/1yp2_skqkxyrc0egdRv6ofnRGCI9nmvxDFBkCXgy0Jwo
Hi All,
As usual, here are my updates:
*- Formalised pull request, looking for a formal review*
Last week I published the wiki page for my meta implementation. This week I
have been working on improving internal code documentation, optimising a
few bits and bobs, and added the formal documentat
2014-07-18 17:43 GMT+02:00 Naveen Yadav :
> when code is changed that line executed, should not it stop executing but
it keep on listening if code is changed or not.
> what happens behind the scene, when sys.exit(3) is executed.
IIRC the development server forks a process to run the server and use
sys.exit() method is used to exit the python interpreter
I have been going through the Django source code in file
*django/utils/autoreload.py*def reloader_thread():
ensure_echo_on()
while RUN_RELOADER:
if code_changed():
*sys.exit(3) # force reload*
Just had a look at django-nap, nice concept but it sadly seems to have
suffered the same over-engineering fate as the others (DRF, Piston,
Tastypie etc). Happy to discuss why in a separate thread, but probably
off topic for this one.
At present I'm just looking for proposals to introduce request
i
Sounds like you're heading for a cleaner version of the Publisher pattern
in django-nap...?
On 18 July 2014 07:34, Cal Leeming [Simplicity Media Ltd] <
cal.leem...@simplicitymedialtd.co.uk> wrote:
> Hello,
>
> Currently implementing a method dispatcher (e.g. a single URL that
> goes to different
