Hi Jason, pyc are compiled py files ... it means you most likely ran the code before doing the "ls".
As for the structure of the directories, I'm fairly certain that its MySite first, then MyApp, not 2x mysite. Not going to speak on the database syncs, other then that they work fine for me. I'd also suggest you don't use titles like you do, don't post user problems in the developers list (this is for core django development discussions, not users having problems). If your comment with file layouts was regarding the ".pyc" files, might I suggest you first read a bit of the basics on Python. They aren't really essential, but if pyc files confuse and agitate you as much as your message title suggest, it might alleviate quite a bit of stress. r/Jan 2012/4/11 Jason Ma <rosegu...@gmail.com> > Hi, > I download and tried to use the Django 1.4 yesterday. I am a dummy > and I just follow the official document, but When I just start a > project. > I found that it is what I see from my computer: > > jason@jason-pc:~/workspace/hunqing$ tree . > . > ├── hunqing > │ ├── __init__.py > │ ├── __init__.pyc > │ ├── settings.py > │ ├── settings.pyc > │ ├── urls.py > │ ├── urls.pyc > │ ├── wsgi.py > │ └── wsgi.pyc > ├── __init__.py > ├── manage.py > ├── settings.py > └── urls.py > > but what doc say? > mysite/ > manage.py > mysite/ > __init__.py > settings.py > urls.py > wsgi.py > > If you're a beginner, what are you going to say, yes, F! Why I created > more files? I heavily doubted that whether the writers have tested > that carefully. Ok, forget that, We'll see and continue. > In the later chapter, we created two classes in the models.py in > polls, I do all the steps same as the doc except that one columns > name, mine is questions whereas the doc is question, so I want to test > the power of the syncdb, I modified the model.py and I just do the > python manage.py sql polls, that's ok, it is correct name this time. > So I just run it to change it in database using python manage.py > syncdb, it works too. But go to the db and see, the table is not > changed at all. I want to say F again now. That's what doc say: > > The syncdb command runs the SQL from sqlall on your database for all > apps in INSTALLED_APPS that don't already exist in your database. This > creates all the tables, initial data and indexes for any apps you've > added to your project since the last time you ran syncdb. syncdb can > be called as often as you like, and it will only ever create the > tables that don't exist. > > That's gr8, If you just create the tables that don't exist, why do you > syncdb successfully? One basic rule of database is consistence, if you > can't created the tables you want, why don't get alert? I am not a > good programmer though, I do know if you can't do something, just say > it. How can I know the error without any prompt? > > There are many people saying the Django is well-documented, do you > still think it is true? > > -- > Best wishes, > > Jason Ma > HP Enterprise Services > > -- > You received this message because you are subscribed to the Google Groups > "Django developers" group. > To post to this group, send email to django-developers@googlegroups.com. > To unsubscribe from this group, send email to > django-developers+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/django-developers?hl=en. > > -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com. To unsubscribe from this group, send email to django-developers+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
