#8147 closed (fixed)
Development server reloading on Jython
| Reported by: | Leo Soto M. | Owned by: | nobody |
|---|---|---|---|
| Component: | Core (Other) | Version: | dev |
| Severity: | Keywords: | jython | |
| Cc: | Triage Stage: | Unreviewed | |
| Has patch: | yes | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | no | UI/UX: | no |
Description
The existing development server reloading code uses a process forking approach, which works well on CPython but is not very applicable on Jython, where the JVM startup time and the loose of HotSpot optimizations caused by respawning the Jython process are not desiderable. Not to mention that some spawnve POSIX flags aren't supported yet.
So, I've implemented an alternative (and IMHO, simpler) reloader strategy for Jython, which is helped by Jython itself. The Jython bits have been recently commited so this will work out of the box.
It also includes a small refactoring of autoreload.py, to avoid code duplication.
Attachments (1)
Change History (3)
by , 16 years ago
| Attachment: | jython-reloader.diff added |
|---|
comment:1 by , 16 years ago
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
Note:
See TracTickets
for help on using tickets.
(In [8235]) Made auto-reloading for the dev server a little more friendly in the Jython
case. Patch from Leo Soto. Fixed #8147.
In passing, also corrected a typo when reloading .pyo files. Fixed #8157.