Opened 10 years ago

Closed 10 years ago

#23020 closed Bug (duplicate)

runserver auto-reload broken in 1.7.x (rc) on Mac OS X

Reported by: Stephen Burrows Owned by: nobody
Component: Core (Management commands) Version: 1.7-rc-1
Severity: Release blocker Keywords:
Cc: Stephen Burrows Triage Stage: Unreviewed
Has patch: no Needs documentation: no
Needs tests: no Patch needs improvement: no
Easy pickings: no UI/UX: no

Description

I assume this is a release blocker.

I am using a Mac OS X 10.9.4. I recently pulled down some changes, including the new --noreload option for runserver. Since then, runserver auto-reload has not been working. I am *not* using the --noreload option, and I emphatically *do* want the auto-reload behavior. This has been extremely irritating. Let me know if you need more information.

Change History (10)

comment:1 by Tim Graham, 10 years ago

Summary: runserver auto-reload broken in 1.7.x (rc)runserver auto-reload broken in 1.7.x (rc) on Mac OS X

Hm, I don't seem to have problems on Linux, but this was also reported on Windows (#22991). --noreload isn't a new option though. The latest change to runserver reloading was 1bb8ccdb9e70bee35759f2ada4d661481852ab95.

comment:2 by Collin Anderson, 10 years ago

Reloads fine for me when editing an admin.py on OS X 10.9.4. I tried both 1.7c1 and the latest stable/1.7.x. import pyinotify raises an ImportError so I don't have that installed.

comment:3 by Stephen Burrows, 10 years ago

You're correct that the no-reload option was added a while ago. That was a bad assumption on my part, since I just noticed it existed. ;-) I'll see if I can dig a little deeper.

I can confirm that the autoreloader is being run, which means that the issue is somewhere in *there*, not an issue getting there.

comment:4 by Stephen Burrows, 10 years ago

Okay... this is really weird. If I put something in the reloader script that prints to stdout, then the reloading works fine. But without that, it doesn't work.

Version 0, edited 10 years ago by Stephen Burrows (next)

comment:5 by Stephen Burrows, 10 years ago

Make that - if I put anything in the reloader script at all that gets executed period, then it works fine.

comment:6 by Stephen Burrows, 10 years ago

Removing cached pyc files does not help.

comment:7 by Stephen Burrows, 10 years ago

Reinstalling django also doesn't help.

Any chance the fact that I'm using a pip -e install in a virtualenv might be relevant?

comment:8 by Stephen Burrows, 10 years ago

I'll bisect it later.

comment:9 by Collin Anderson, 10 years ago

Hah! While debugging the windows ticket I noticed that *.pyc files were coming up. I have sys.dont_write_bytecode = True in all of my manage.py files. If I take that that out it stops working.

Last edited 10 years ago by Collin Anderson (previous) (diff)

comment:10 by Collin Anderson, 10 years ago

Resolution: duplicate
Status: newclosed

I can confirm it's the same issue as windows issue #22991

Note: See TracTickets for help on using tickets.
Back to Top