Ok, think I may have found it: the site runs fine in Chrome’s incognito (porn) mode. So I strongly suspect I’ve got some kind of extension that’s interfering with it (like Do Not Track or something). EDIT It’s Collusion’s “block known tracking sites” feature.
From Django documentation for url url(regex, view, kwargs=None, name=None) This function is an alias to django.urls.re_path(). It’s likely to be deprecated in a future release. Key difference between path and re_path is that path uses route without regex You can use re_path for complex regex calls and use just path for simpler lookups
From django doc: SQLite is meant to be a lightweight database, and thus can’t support a high level of concurrency. OperationalError: database is locked errors indicate that your application is experiencing more concurrency than sqlite can handle in default configuration. This error means that one thread or process has an exclusive lock on the database … Read more
In django, named capturing groups are passed to your view as keyword arguments. Unnamed capturing groups (just a parenthesis) are passed to your view as arguments. The ?P is a named capturing group, as opposed to an unnamed capturing group. http://docs.python.org/library/re.html (?P<name>…) Similar to regular parentheses, but the substring matched by the group is accessible within … Read more
The issue here is that you’re not running any web dynos. You can tell Heroku to do this via: This will force Heroku to spin up a web dyno, thereby executing your gunicorn command.
You can set environmental variables in Pycharm’s run configurations menu. Open the Run Configuration selector in the top-right and cick Edit Configurations… Find Environmental variables and click … Add or change variables, then click OK You can access your environmental variables with os.environ
You need to add the package containing the executable pg_config. A prior answer should have details you need: pg_config executable not found
Django 2.0 removes the django.core.urlresolvers module, which was moved to django.urls in version 1.10. You should change any import to use django.urls instead, like this: Note that Django 2.0 removes some features that previously were in django.core.urlresolvers, so you might have to make some more changes before your code works. See the features deprecated in 1.9 for details on those additional changes.
manage.py should live in the root project folder, so if you cd into C:Users/arpchauh/PycharmProjects/post_blog, you should be able to run the command.
You can use events = venue.event_set to go the other way. Note that venue.event_set is a manager object, like Event.objects, so you can call .all, .filter, .exclude and similar on it to get a queryset. See the Django documentation