How can i keep test data in django testing

[Sub Zero]

 

I am using django 1.8 and it says to use --keepdb to save test database

https://docs.djangoproject.com/en/1.8/topics/testing/overview/#the-test-database

I am doing that and database is there but everytime i see it and it is 
empty and has no data in it.

Is there any way that i can preserve that so that i can see whats in there
 

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-users+unsubscr...@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at http://groups.google.com/group/django-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/ab63d509-20e7-4b5d-8afe-207a130bf8dc%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Issues Upgrading to django 1.8 and migrating from south

[Marcela Campo]

Hi all,
  I am upgrading an app from django 1.5 + south to 1.8. I am having some 
issues when faking migrations with the recommended procedure here 
https://docs.djangoproject.com/en/1.8/topics/migrations/#upgrading-from-south

I am using postgres with postgis extension and engine 

 'ENGINE': 'django.contrib.gis.db.backends.postgis',


I followed the procedure indicated in the docs, solved circular 
dependencies issues etc. I tried locally and worked fine, but now in 
another environment I get the following error

 File 
"/home/deploy/marcela-dev/src/hhenv_1_8/local/lib/python2.7/site-packages/django/core/management/__init__.py",
 
line 338, in execute_from_command_line
utility.execute()
  File 
"/home/deploy/marcela-dev/src/hhenv_1_8/local/lib/python2.7/site-packages/django/core/management/__init__.py",
 
line 330, in execute
self.fetch_command(subcommand).run_from_argv(self.argv)
  File 
"/home/deploy/marcela-dev/src/hhenv_1_8/local/lib/python2.7/site-packages/django/core/management/base.py",
 
line 390, in run_from_argv
self.execute(*args, **cmd_options)
  File 
"/home/deploy/marcela-dev/src/hhenv_1_8/local/lib/python2.7/site-packages/raven/contrib/django/management/__init__.py",
 
line 41, in new_execute
return original_func(self, *args, **kwargs)
  File 
"/home/deploy/marcela-dev/src/hhenv_1_8/local/lib/python2.7/site-packages/django/core/management/base.py",
 
line 441, in execute
output = self.handle(*args, **options)
  File 
"/home/deploy/marcela-dev/src/hhenv_1_8/local/lib/python2.7/site-packages/django/core/management/commands/migrate.py",
 
line 91, in handle
connection.prepare_database()
  File 
"/home/deploy/marcela-dev/src/hhenv_1_8/local/lib/python2.7/site-packages/django/contrib/gis/db/backends/postgis/base.py",
 
line 39, in prepare_database
cursor.execute("CREATE EXTENSION IF NOT EXISTS postgis")
  File 
"/home/deploy/marcela-dev/src/hhenv_1_8/local/lib/python2.7/site-packages/django/db/backends/utils.py",
 
line 79, in execute
return super(CursorDebugWrapper, self).execute(sql, params)
  File 
"/home/deploy/marcela-dev/src/hhenv_1_8/local/lib/python2.7/site-packages/django/db/backends/utils.py",
 
line 64, in execute
return self.cursor.execute(sql, params)
  File 
"/home/deploy/marcela-dev/src/hhenv_1_8/local/lib/python2.7/site-packages/django/db/utils.py",
 
line 97, in __exit__
six.reraise(dj_exc_type, dj_exc_value, traceback)
  File 
"/home/deploy/marcela-dev/src/hhenv_1_8/local/lib/python2.7/site-packages/django/db/backends/utils.py",
 
line 62, in execute
return self.cursor.execute(sql)
django.db.utils.InternalError: PostGIS is already installed in schema 
'public', uninstall it first


my env is

ubuntu 15.04
python 2.7.9
postgres 9.4.1
Django==1.8.2
psycopg2==2.6


Any ideas why this could be happening? Any help appreciated!

Thanks!
Marcela



-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-users+unsubscr...@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at http://groups.google.com/group/django-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/3d380142-895d-47aa-a063-6309cc10bd5f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

StackOverflow Question: Trouble with updating "To Do Task" objects already existing in database

[Gregory Desrosiers]

Hi there!

This is my first post in this group, and even though I did took a look at 
the About section, I can't tell what the rules are.

Anyway, I have a website where I'm implementing a "To Do List" using HTML, 
CSS, jQuery, and Django for me to learn about using a Django server and 
database. The tasks are saved as objects in the server, where each one has 
a string denoting what it is, as a label, and a Boolean value, as a 
checkbox, for whether or not that task is done.

I posted my question as a StackOverflow question: 
http://stackoverflow.com/questions/30514359/django-trouble-with-updating-a-booleanfield-with-my-todochecklisttask-model

Could you please take a look and help me out?

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-users+unsubscr...@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at http://groups.google.com/group/django-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/a3ce1a1c-f26d-4b6e-b29a-251b07b28ee9%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Why the extra minute in PostgreSQL when using time zone info?

[Daniel Grace]

I used this function, seemed to tidy up the problem:

from datetime import datetime
from pytz import timezone

def utcDtTm(self, dt_tm):
tz = timezone('Europe/London')
return tz.normalize(tz.localize(dt_tm)).astimezone(timezone('UTC'))

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-users+unsubscr...@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at http://groups.google.com/group/django-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/12a0ab90-8108-46b4-8e90-5aadedbb3d2c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Why the extra minute in PostgreSQL when using time zone info?

[Daniel Grace]

I am creating some test data for a DateTimeField using the following 
function:

def rndDtTm(self):
uktz = timezone('Europe/London')
year = 2015
month = 6
day = randint(1, 30)
hour = randint(0, 23)
minute = 30 * randint(0, 1)
return datetime(year, month, day, hour, minute, 0, 0, tzinfo = uktz)

When I look at the PostgreSQL field in pgAdminIII the times are either 1 or 
31 minutes past the hour:
2015-06-10 22:01:00+01
2015-06-12 21:31:00+01

I was expecting them to be 0 or 30 minutes past the hour.  Why the extra 
minute?

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-users+unsubscr...@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at http://groups.google.com/group/django-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/156ff7ce-9252-4384-9eaa-7e4b23a3880c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Django post response method post not allowed

[Filipe Ximenes]

I assume you are using Django REST Framework.
ListAPIViews only accepts GET requests, because well, it's supposed only to
list stuff. If you need to add data, try the CreateAPIView, or depending on
what you want, a ListCreateAPIView.

On Thu, May 28, 2015 at 10:58 AM, Shekar Tippur  wrote:

> Hello,
>
> I am trying to post a request via curl.
>
> curl -H  "Authorization: Bearer $usertoken" -X POST -d
> '{"username":"foo1","object":"XYZ","prefs":"likes"}' http://
> ${endpoint}/setProfile/
>
> Here is the entry in my urls.py
>
> url(r'^setProfile/', AddToUserProfile),
>
>
> class AddToUserProfile(generics.ListAPIView):
> queryset = UserPrefs.objects.all()
> serializer_class = UserPrefSerializer
>
>
> class UserPrefSerializer(serializers.ModelSerializer):
> class Meta:
> model = UserPrefs
> fields = ('id', 'prefs', 'obj_id', 'user_id')
> depth = 1
>
>
> I get a response - {"detail":"Method \"POST\" not allowed."}
>
>
> Is there anything else I need to specify?
>
>
> - Shekar
>
>  --
> You received this message because you are subscribed to the Google Groups
> "Django users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to django-users+unsubscr...@googlegroups.com.
> To post to this group, send email to django-users@googlegroups.com.
> Visit this group at http://groups.google.com/group/django-users.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/django-users/d8db1691-e60d-4a46-9598-47227bd4c6e9%40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>



-- 


*Filipe Ximenes*+55 (81) 8245-9204

*Vinta Software Studio*http://www.vinta.com.br

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-users+unsubscr...@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at http://groups.google.com/group/django-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/CAA-QWB3Zkc8%2BuVFcA8oD5M_9SAKMv6QAKboPGyUY2C2pBQn%3DwA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Testing a new app

[Bill Freeman]

If the "new" app doesn't need services from the larger app in order t work,
but rather the other way around, why not leave it separate, and later, just
make it an install requirement for the larger app?

On Thu, May 28, 2015 at 5:54 AM, Klaas Feenstra  wrote:

> Using GIT would be the way of working..
>
> On Thu, May 28, 2015 at 4:24 AM, DZ  wrote:
>
>> Greetings,
>>
>>  I want to start a new app that if it works out I will tie into a larger
>> django app. I do not really want the worlds to mix at the start just in
>> case I need scrap and start it over a few times. I was thinking the best
>> approach would be to create this first as a stand alone app and then when I
>> have the details worked out bring it under the larger app. When I bring it
>> under the larger app I know I would start the data over and use south to
>> bring the worlds together. I am developing under windows, django, python,
>> mysql, and I use south as my db migration tool. Does anyone forsee any
>> problems with this approach? Sorry if the question seems obvious or simple
>> just would like to travel the path of lower resistance as Im working out
>> the features/models of this new app.
>>
>> Thanks for any advice.
>>
>> DZ
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "Django users" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to django-users+unsubscr...@googlegroups.com.
>> To post to this group, send email to django-users@googlegroups.com.
>> Visit this group at http://groups.google.com/group/django-users.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/django-users/81557fc6-48c7-4cea-ae9a-c5b49be06f82%40googlegroups.com
>> 
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>  --
> You received this message because you are subscribed to the Google Groups
> "Django users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to django-users+unsubscr...@googlegroups.com.
> To post to this group, send email to django-users@googlegroups.com.
> Visit this group at http://groups.google.com/group/django-users.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/django-users/CAJcivaembcZ%3DNtNxiWP%3Dr8e%3DHTfZfFLn4jYDCedcKiqS_vsb0A%40mail.gmail.com
> 
> .
>
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-users+unsubscr...@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at http://groups.google.com/group/django-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/CAB%2BAj0s2PnCaDnbR1_JU1r4mJh6reoeAOucL1-K6UR%3DTKO80sg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Django post response method post not allowed

[Shekar Tippur]

Hello,

I am trying to post a request via curl. 

curl -H  "Authorization: Bearer $usertoken" -X POST -d 
'{"username":"foo1","object":"XYZ","prefs":"likes"}' 
http://${endpoint}/setProfile/

Here is the entry in my urls.py

url(r'^setProfile/', AddToUserProfile),


class AddToUserProfile(generics.ListAPIView):
queryset = UserPrefs.objects.all()
serializer_class = UserPrefSerializer


class UserPrefSerializer(serializers.ModelSerializer):
class Meta:
model = UserPrefs
fields = ('id', 'prefs', 'obj_id', 'user_id')
depth = 1


I get a response - {"detail":"Method \"POST\" not allowed."}


Is there anything else I need to specify?


- Shekar

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-users+unsubscr...@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at http://groups.google.com/group/django-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/d8db1691-e60d-4a46-9598-47227bd4c6e9%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: django handling requests - getting CSRF verification failed. Request aborted.

[Shekar Tippur]

Larry,

I think I needed to append as_view() to the url.

url(r'^setProfile/', AddToUserProfile.as_view()),


I will try the other curl option as well.

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-users+unsubscr...@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at http://groups.google.com/group/django-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/bf15c7d0-fbf1-4825-ae94-f15e2bf30697%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: django handling requests - getting CSRF verification failed. Request aborted.

[Larry Martell]

On Thu, May 28, 2015 at 9:31 AM, Shekar Tippur  wrote:
> Hello,
>
> I am trying to post a request via curl. I get a CSRF verification failed
> message.
>
> Here is the entry in my urls.py
>
> url(r'^setProfile/', AddToUserProfile),
>
>
> class AddToUserProfile(generics.ListAPIView):
> queryset = UserPrefs.objects.all()
> serializer_class = UserPrefSerializer
>
>
> class UserPrefSerializer(serializers.ModelSerializer):
> class Meta:
> model = UserPrefs
> fields = ('id', 'prefs', 'obj_id', 'user_id')
> depth = 1
>
>
> I have read on previous posts that I need to add a
> context_instance=RequestContext(request)
>
>
> How do I add it and what is the right way to handle this?

I have done it like this:

curl -H "Cookie: csrftoken=mycsrfToken" -X POST -d
'csrfmiddlewaretoken= mycsrfToken&...'

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-users+unsubscr...@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at http://groups.google.com/group/django-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/CACwCsY4RDx-ZrAgd8V8%3DBifHrvn%2BbSg2OM0BWYEJNPrwqn2u5w%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

django handling requests - getting CSRF verification failed. Request aborted.

[Shekar Tippur]

Hello,

I am trying to post a request via curl. I get a CSRF verification failed 
message.

Here is the entry in my urls.py

url(r'^setProfile/', AddToUserProfile),


class AddToUserProfile(generics.ListAPIView):
queryset = UserPrefs.objects.all()
serializer_class = UserPrefSerializer


class UserPrefSerializer(serializers.ModelSerializer):
class Meta:
model = UserPrefs
fields = ('id', 'prefs', 'obj_id', 'user_id')
depth = 1


I have read on previous posts that I need to add a 
context_instance=RequestContext(request)


How do I add it and what is the right way to handle this?


- Shekar

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-users+unsubscr...@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at http://groups.google.com/group/django-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/ed9461e1-7e8e-4794-af37-6cb63120b775%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Django Test Coverage

[Gergely Polonkai]

Hello,

IMHO it is much better to see the coverage values for everything (even
tests.py). Your actual case, for example, shows that only 98 lines are
running from your 100 lines long tests.py. This may mean that there is a
condition somewhere in your test cases that never evaluates to true.

If you want to see the lines that are not covered, assuming you are using
the “standard” coverage.py tool, you can use the command `coverage html` so
it will generate a HTML version of the coverage info. In case you can’t
access such HTML files, you can use either `coverage report --show-missing`
to see line numbers that are not covered, or `coverage annotate modulename`
to create an annotated version of your module file that will show you
different execution information in your source files.

Kind regards,
Gergely

2015-05-28 13:18 GMT+02:00 Dharmit Shah :

> Hello all,
>
> I have a django app which is full REST APIs created using Django Rest
> Framework.
>
> In tests.py, I am testing fthe APIs using self.client.post and
> self.clilent.get. I use coverage tool to figure out the test coverage
> but it seems to check the coverage in a way I don't really understand.
>
> When I check test coverage for just views.py file, it says 37% and
> when I do that for tests.py, it says 98%.
>
> Is there a way to determine test coverage only by looking at views.py
> and checking how many of the views in it are tested in tests.py?
>
> Or is it an unreasonable expectation?
>
> Regards,
> Dharmit.
>
> --
> You received this message because you are subscribed to the Google Groups
> "Django users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to django-users+unsubscr...@googlegroups.com.
> To post to this group, send email to django-users@googlegroups.com.
> Visit this group at http://groups.google.com/group/django-users.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/django-users/CAJQZradk25770YeOGjHT4tBRaJsrexo578pt7xnHFRKZ0hAWFg%40mail.gmail.com
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-users+unsubscr...@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at http://groups.google.com/group/django-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/CACczBUJZ6r6KEWg8Q7DWWVeC79hYSi9J3L%2BfEUTk87N4APUwnA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Get newly created object id and then save the object in different DB?

[Ashutosh Das]

In Django function based view I can get newly created object id and again 
save that object to different database in this way :

data = Password(username=username, password=encrypted_pass,
  note=encrypted_note,added_at=timezone.now())
 data.save()
 Id = data.id
 data.pk = None
 data.save(using='backup')

But how can I do the same thing in Class based view ? Here is my view :

class AddData(LoggedInMixin, CreateView):
model = Password
success_url = '/dashboard'
template_name = 'forms/add.html'
fields = ['site_url', 'username', 'email', 'password', 'note']

def form_valid(self, form):
form.instance.added_at = timezone.now()
return super(AddData, self).form_valid(form)

def form_invalid(self, form):
return self.render_to_response(self.get_context_data(form=form))


-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-users+unsubscr...@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at http://groups.google.com/group/django-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/042e6c2a-686f-4c00-89d7-7215589e22cf%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Django Test Coverage

[Dharmit Shah]

Hello all,

I have a django app which is full REST APIs created using Django Rest Framework.

In tests.py, I am testing fthe APIs using self.client.post and
self.clilent.get. I use coverage tool to figure out the test coverage
but it seems to check the coverage in a way I don't really understand.

When I check test coverage for just views.py file, it says 37% and
when I do that for tests.py, it says 98%.

Is there a way to determine test coverage only by looking at views.py
and checking how many of the views in it are tested in tests.py?

Or is it an unreasonable expectation?

Regards,
Dharmit.

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-users+unsubscr...@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at http://groups.google.com/group/django-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/CAJQZradk25770YeOGjHT4tBRaJsrexo578pt7xnHFRKZ0hAWFg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Testing a new app

[Klaas Feenstra]

Using GIT would be the way of working..

On Thu, May 28, 2015 at 4:24 AM, DZ  wrote:

> Greetings,
>
>  I want to start a new app that if it works out I will tie into a larger
> django app. I do not really want the worlds to mix at the start just in
> case I need scrap and start it over a few times. I was thinking the best
> approach would be to create this first as a stand alone app and then when I
> have the details worked out bring it under the larger app. When I bring it
> under the larger app I know I would start the data over and use south to
> bring the worlds together. I am developing under windows, django, python,
> mysql, and I use south as my db migration tool. Does anyone forsee any
> problems with this approach? Sorry if the question seems obvious or simple
> just would like to travel the path of lower resistance as Im working out
> the features/models of this new app.
>
> Thanks for any advice.
>
> DZ
>
> --
> You received this message because you are subscribed to the Google Groups
> "Django users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to django-users+unsubscr...@googlegroups.com.
> To post to this group, send email to django-users@googlegroups.com.
> Visit this group at http://groups.google.com/group/django-users.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/django-users/81557fc6-48c7-4cea-ae9a-c5b49be06f82%40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-users+unsubscr...@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at http://groups.google.com/group/django-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/CAJcivaembcZ%3DNtNxiWP%3Dr8e%3DHTfZfFLn4jYDCedcKiqS_vsb0A%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Testing a new app

[DZ]

Greetings,

 I want to start a new app that if it works out I will tie into a larger 
django app. I do not really want the worlds to mix at the start just in 
case I need scrap and start it over a few times. I was thinking the best 
approach would be to create this first as a stand alone app and then when I 
have the details worked out bring it under the larger app. When I bring it 
under the larger app I know I would start the data over and use south to 
bring the worlds together. I am developing under windows, django, python, 
mysql, and I use south as my db migration tool. Does anyone forsee any 
problems with this approach? Sorry if the question seems obvious or simple 
just would like to travel the path of lower resistance as Im working out 
the features/models of this new app.

Thanks for any advice.

DZ

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-users+unsubscr...@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at http://groups.google.com/group/django-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/81557fc6-48c7-4cea-ae9a-c5b49be06f82%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.