django-extensions Google Group

Re: mongoengine added support for shell_plus

v.oostv...@gmail.com (trbs) — Sun, 19 May 2013 15:52:13 UT

Hi,
I like the addition. I'm thinking that I might spend some time making some
kind of 'plugin' architecture for this.
But isn't the code missing the assignment of mongoengine objects to
imported_objects so make them available in the shell ?
Also please make a pull request this this so it's easier to integrate.

mongoengine added support for shell_plus

nullwri...@gmail.com (Tomtom Henriquez) — Fri, 17 May 2013 22:54:04 UT

Hello, I added a experimental mongoengine support for shell_plus.
Here is my case and why. In the company I am working on we use both
postgresql and mongo (with mongoengine). It is a pain to write the import
everytime for the mongoengine Documents (since they don't get imported into
the shell of course).

RE: [django-extensions] Re: sqldiff postgres bigserial patch

j...@carroll.com (Jim Carroll) — Thu, 07 Mar 2013 14:13:55 UT

Wow - I think you take the prize for the greatest Django add-on AND fastest
response !

Jim C.

[mailto:django-extensions@goog legroups.com] On Behalf Of trbs
Sent: Thursday, March 07, 2013 9:02 AM
To: django-extensions@googlegroups .com

Thanks, your patch has been applied.

Re: sqldiff postgres bigserial patch

v.oostv...@gmail.com (trbs) — Thu, 07 Mar 2013 14:01:44 UT

Thanks, your patch has been applied.
I'll try to do a new release on pypi within a couple of hours so people can
update their requirements files.

sqldiff postgres bigserial patch

j...@carroll.com (JimC) — Thu, 07 Mar 2013 13:04:34 UT

We've recently migrated from Django 1.3 -> 1.5, and of course upgraded to
the latest django-extensions. One thing we noticed was that the sqldiff
command does not correctly understand postgres tables with bigserial
fields. The result is that every invocation of sqldiff generates SQL
changes -- and worse, the changes are not valid postgres code.

Re: clean_pyc doesn't seem to work

v.oostv...@gmail.com (trbs) — Tue, 23 Oct 2012 12:39:46 UT

No your not :)
The get_project_root() function in django_extensions.management.u tils is
doing the wrong thing.
Since you use a 'settings' directory instead of a file it wrongly assumes
that the root of your project is 'boilerplate/settings' instead of
'boilerplate'.
Could you please submit an issue for this in github ?

clean_pyc doesn't seem to work

lacrymol...@gmail.com (Tomas Neme) — Tue, 23 Oct 2012 12:32:26 UT

Hello. I'm wondering if I'm doing something wrong, but running
clean_pyc seems to have no effect. I've tried this both on 0.9+dj1.3
and 1.0+dj1.4

Is there something I'm overseeing?

(env-1.4)lacrymology@Roller:bo ilerplate$ ./manage.py clean_pyc
(env-1.4)lacrymology@Roller:bo ilerplate$ find boilerplate/ -name

Re: [django-extensions] Re: Broken database commands

chriss...@gmail.com (Chris Spencer) — Fri, 17 Feb 2012 13:54:20 UT

Ok, thanks. I've submitted the pull request. The changes were actually
pretty minor, but it's my first one on Github, so if I left anything
out, or you need more detail, please let me know.

Re: Broken database commands

v.oostv...@gmail.com (trbs) — Thu, 16 Feb 2012 18:39:22 UT

No, I think the reason is more that none of the regular committers use
these commands.

If you create a pull-requests to fix these, we will try to merge them
as soon as possible.

Broken database commands

chriss...@gmail.com (Cerin) — Thu, 16 Feb 2012 16:23:38 UT

Are the sqlcreate and reset_db commands deprecated? Both are broken in
the current release (at least for PostgreSQL), and after looking at
the code they both seem to do the same thing (i.e. drop and recreate
the database).

I've been using a similar script to manage my databases, but django-
extensions looked like an interesting toolkit, so I investigating

Re: Pull request with a new print_settings command

msabr...@gmail.com (Marc) — Mon, 24 Oct 2011 04:43:51 UT

I've updated it now so that it supports multiple output formats:

[link]

Pull request with a new print_settings command

msabr...@gmail.com (Marc) — Thu, 20 Oct 2011 19:18:14 UT

Here's a pull request with perhaps the simplest Django management
command ever:

[link]

Cheers,
Marc

how can I use ipdb with runserver_plus?

tschm...@sacfoodcoop.com (Tony Schmidt) — Fri, 05 Aug 2011 16:48:46 UT

Can someone help me configure this? I love the werkzeug debugger but
it just provides pdb by default with django-extensions.

Thanks.

Re: runscript path issue

fja...@gmail.com (Fred Janon) — Wed, 08 Jun 2011 02:18:09 UT

A colleague helped me on that one, we got the runscript to work with that
command:
python manage.py runscript --verbosity 2 dbmigration
Note that there is no .py extension in the command.
The dbmigration.py file has a "def run()" function that gets called by
runscript and is in the scripts folder.

runscript path issue

fja...@gmail.com (Fred Janon) — Tue, 07 Jun 2011 10:03:04 UT

I can't figure out why my runscript command doesn't work, I can't figure out
what path I should put in. Here is the directory structure and the commands
with the verbose option, I am trying to get dbmigration to be executed. I
created the __init__.py file as indicated in the wiki page. It's empty.
I created the scripts directory and put the __int__.py file in it as well as