Hello David,
This reasoning makes sense.
You say that watchman "keeps triggering the command once an event occurs". This
is correct; as a consequence "the command" must stop the currently running
instance of the development server and start a new one. This requires
overhauling significantly
Hi David,
I wouldn't bother with the wsgiwatcher repo; it's proof-of-concept code
from one sprint's worth of hacking, not used by anyone. Look at hupper
instead, it is based on wsgiwatcher, but much changed, and actually used
in production.
Carl
On 04/02/2017 04:27 PM, qingnian...@gmail.com
Hi Aymeric,
I feel like using Watchman might be the easiest solution. It keeps
triggering the command once an event occurs, so autoreload.py does not need
to restart the server in case of a syntax error. Pywatchman does not work
on Python 3 and has some dependency problems, so I'm planning to
Hi Carl,
I don't quite understand why get_module_paths() in your wsgiwatcher
project is returning a list of python module paths. I thought it would
return the directory that needs to be monitored. Could you please tell me
how this part works? Thanks.
David Ma
On Thursday, March 30, 2017 at
Hello,
On 1 Apr 2017, at 05:52, qingnian...@gmail.com wrote:
> For the pure-Python solution, I might implement a standalone autoreloader
> based on Carl's work and replace the current one. Does this look good to you?
Perhaps.
It depends on the details (features, installation requirements,
Hi Aymeric,
Thanks for this detailed and informative response! I will try to figure
out the difficulties of integrating Watchman during the weekend. For the
pure-Python solution, I might implement a standalone autoreloader based on
Carl's work and replace the current one. Does this look good
On Thursday 30 March 2017 22:01:00 qingnian...@gmail.com wrote:
> Hi Carl,
> Thanks for mentioning this awesome project! I saw it in one of the
> discussions but did not take a close look. I'll definitely check this
> out and try to integrate wsgiwatcher/watcher.py into Django.
>
> On Thursday,
Hi Brice,
Thanks for the suggestion! I'm not sure whether if I can successfully
implement a library like you've mentioned, so for now I might stick with
the Watch* libraries available. I really love the goals you've listed and
would add these to my proposal.
David Ma
On Thursday, March 30,
Hi Carl,
Thanks for mentioning this awesome project! I saw it in one of the
discussions but did not take a close look. I'll definitely check this out
and try to integrate wsgiwatcher/watcher.py into Django.
On Thursday, March 30, 2017 at 7:47:13 AM UTC-7, Carl Meyer wrote:
>
> Anyone working
Anyone working on this project should at least be aware of
https://github.com/Pylons/hupper (based on work David Glick and I
originally did in https://github.com/carljm/wsgiwatcher), which aims to
be a framework-agnostic solution to this problem for any Python web
project. Docs at
Hello,
> On 29 Mar 2017, at 01:05, qingnian...@gmail.com wrote:
>
> the best library to replace Watchdog is Watchman, a library that supports
> both of these three platforms (for Windows it's still in the alpha stage.)
Django currently doesn't use Watchdog. Watchdog is a cross-platform Python
Hi, I'm David Ma, a first-year Science student from the University of
British Columbia. I'm a enthusiastic Django developer and have four years
Python programming experience. I've read through the posts about replacing
the current autoreloader and would like to work on this task during GSoC. I
12 matches
Mail list logo
