Re: Google App Engine and Facebook
This question belongs in Django-users, Django-developers is only for development of the django framework, not development with the framework. 2010/7/2 Binh > Hi, > > Has anyone here built a facebook canvas application using Django 1.* > and got it working on Google App Engine? > > If so, can you give pointers on where I can learn this? > > -- > You received this message because you are subscribed to the Google Groups > "Django developers" group. > To post to this group, send email to django-develop...@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-develop...@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.
Re: Django is not a serious framework, really
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 > 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.
Re: Django is not a serious framework, really
Hi, Jason, I suggest you go to the django-users list for help: http://groups.google.com/group/django-users This list is only for django core development (aka, the framework itself), not for people using Django. And, it's no bother, but you came on rather strong, with wording that real world information, directly contradicts, not only is Django used for a variety of sites, it is also used by some very high profile sites and corporations. Besides that, the documentation is worked on almost as hard as Django's core, very little auto generated content and it is checked, for each release, by a multitude of people. If you found an actual error in said documentation, it would be best to give detailed information and start a constructive conversation about the issue's, so that it can be resolved. Starting with a premise that mostly condenses down to "Django/Django Documentation is a 3de rate POS", isn't very constructive and will only serve to tick of the developers that put their free time into creating this application. But as someone else replied already and I just did again, when following the documentation point by point, the correct layouts and behavior, are obtained as expressed in the documentation. If you repost your problem to the appropriate list (django-users), I would also suggest you give a bit more information. Things like: Python version. OS you are using. (and I think in your case the language of the OS might be useful). Exact commands you used to. Etc. The more information the better. r/Jan 2012/4/11 Jason Ma > Hi Jan, >I don't mean the .pyc files in the folder, If it was that, > everything will be fine. Please read what I typed carefully. And > please test the case I just mentioned, I tested again and still the > same situation. It maybe the feature, but hope it will get more > user-friendly because we are all human being right? We will get more > fun if we get more helpful document. Forget it if it bother you. > > Regards, > Jason > > 在 2012年4月11日 下午8:27，Jan Schotsmans 写道： > > 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 > >> > >> 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
Re: Django is not a serious framework, really
I saw the Chinese date-stamp in his email and deducted the same, hence why I said it might be wise to add the language of his installation, so people are aware (but to django-users). Don't really know what serveral pages are, but I do understand language barrier problems :p (just kidding, hugz typo's) As for a Chinese documentation project, I think that might be something for the Chinese users, who are fluent in English, to do. I don't think many of the devs are versed in Mandarin or Cantonese, (other then the little Cantonese they might have picked up from watching movies out of Hong Kong XD). Personally, as I keep telling people in my lil country, even if it bothers you, try doing stuff in other languages, knowing them will only benefit you in the long run. I personally hate dubbed TV shows, especially children programs for over the age of 8. If they leave them in the native language, with subtitles, the kids will pick up the basics of the languages very easily and the more contact they have at a young age, with other languages, the more easily they'll learn new languages throughout their life. But, for older users, I can certainly understand it to be a potential source of frustrations, even more so, if you are professionally tasked to research the subject and don't have the time to get well versed in English. r/Jan 2012/4/11 bhuztez > The document clearly states that "You'll see a message for each > database table it creates". > > I guess Jason Ma had a hard time reading the document because it is > written in English. Native Chinese speakers who are not quite familiar > with English will feel desperate when they had to read serveral pages > of document in English. Just imagine how desperate will you be if you > have to read pages of document in Chinese when you just learned Ni > Hao. > > Django is getting more and more popular in China recently. More and > more people there are asking questions like how to do this or that in > Django, most of the time, it is just because it is too hard for them > to understand the document on their own. I propose that Django has a > Chinese translation of its document. Sure, there is a huge amount of > work. If core team decides to work on this, I would like to help. > > > Disclaimer: I do not know Jason Ma, I guess he is a Native Chinese > speaker because I googled his email found his email appears on some > Chinese website. > > > On 4月11日, 下午9时29分, Aymeric Augustin > wrote: > > Hi Jason, > > > > Le 11 avril 2012 14:10, Jason Ma a écrit : > > > > > I heavily doubted that whether the writers have tested that carefully. > > > > As one of the many people who replayed the tutorial from A to Z, > > checked every little detail, updated screenshots, etc. before the > > release of 1.4, I feel your feedback is rather unfair. > > > > > There are many people saying the Django is well-documented, do you > > > still think it is true? > > > > Django's documentation assumes that the reader: > > - has some familiarity with Python (e.g. knows what a __init__.py or a > > *.pyc file is) > > - is an autodidact and is able to investigate by himself when (s)he > > deviates from the recommended path and encounters an unexpected > > behavior (e.g. syncdb doesn't perform migrations). > > > > Honestly, if this doesn't match your expectations at all, then Django > > might not be the right framework for you. > > > > I still believe our documentation compares favorably to most > > open-source software entirely developed by volunteers in their free > > time. > > > > Best regards, > > > > -- > > Aymeric. > > -- > 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.
Re: extra files in startproject
Tbh, you can not go cater to this type of new users, that start badmouthing the project right out the gate, with the first hint of trouble, either becoming insulting, out right, on the developer list, or doing as you put in your example, posting bad things on their blogs. If Jason had sent a mail to the developers list stating, "this is the problem I'm having, this is my installation, any idea's?", then we wouldn't have had 10 people defend Django before one came up with "this may be a longshot to be confirmed with further system information, but this seems to be a problem that isn't related to Django itself, but to an unclean installation environment with full or partial, duplicate Django installations." I did respond to him to post his installation base and details about the system he is using, and so have others, but he hasn't responded since, even though there has been quite a decent discussion going about the source of the problem and a possible solution to protect installations against it happening, even though it isn't really Django's fault that package management systems cause the problem, nor is Django in the power to fix "ALL" package management systems that can cause this to happen and most certainly isn't able to protect against this behavior entirely, in case a manual/custom installation is done. Yes, you can make it as easy as as humanly possible for new users, but no, you shouldn't have to go out of your way to cater to users that act like this. 2012/4/13 Daniel Sokolowski > People won’t always read all the docs – it’s a fact – so sooner or > later some other new comer will experience this issue complain, gave up and > worse even blog his/hers negative experience. We do want the newbie > experience to be as painless as possible which means popularity and growth > of the framework - and ultimately continuation of our paying jobs. > > This thread was started by a newbie to the framework, putting aside the > confrontational tone it stated some valid concerns from a beginners > perspective – a very important perspective. > > I’ve been using django for a long time and had no idea about this > ‘distutils’ caveat; I do not understand or know how django installs setup > process works but am up for some kind of a warning/error directly to the > console. > > Thank you for reading my opinion. > > Daniel > *From:* Florian Apolloner > *Sent:* Friday, April 13, 2012 2:15 AM > *To:* django-developers@googlegroups.com > *Subject:* Re: extra files in startproject > > > > On Friday, April 13, 2012 6:49:32 AM UTC+2, Alex Ogier wrote: >> >> I have seen setup.py's that use remove_tree as part of a "clean" command >> to allow someone to run "setup.py clean && setup.py install" to obtain >> a pristine distribution idempotently, which I think is a good idea. >> > No, they should work on fixing distutils instead of creating solutions > which probably could break even worse. > > >> The alternative is to have everyone remember to "rm -rf" their >> site-packages django every time they run setup.py install which is a >> bit unsavory in my opinion. >> > Or just tell them to use either pip even for development installs or just > set their PYTHONPATH. > > >> If someone has managed to get extra files in their site-packages, >> because at any point they followed a tutorial on how to build from >> source, then their django installation is basically caput until they >> manually "rm -rf" a deep library path. One option is to document this >> and explain what to do >> > You made me lol, that approach is documented in the install guide: > https://docs.djangoproject.com/en/dev/intro/install/#remove-any-old-versions-of-django-- > If people would actually read the docs this issue wouldn't exist. FWIW > the docs also mention to symlink a dev checkout and don't tell you to run > setup.py > > >> That would mean listing somewhere the files from >> >> django/conf/project_template/ that should be included, which isn't >> very DRY, but is the only 100% solution I think. >> >> Given that the documentation shows how to do it properly I don't see any > point. Especially since this problem isn't related to the project_template > alone -- that's just where it's most visible. > > > >> So, that should give you some idea of the perils of not cleaning your >> output directories (or in this case, input directory). >> > We are aware of those, and fwiw: If you use git and switch branches it's > up to you to know how python works and how git clean works, or do you want > to suggest that django should rm al pyc files on startup?! > > >> My recommendation is to make "setup.py clean" do everything possible >> to ensure idempotent installation across any version, document that, >> and call it a day. >> > What's wrong with the current documented approach? (Aside from the fact > that people don't read it, but then again they won't read the setup.py > clean either). > > Regards, > Florian > -- > You received this message because you are subscribe
Re: please reopen ticket 15567
I can imagine several situation where you would like the user not to know that, until they talk to an administrator. -1 for me too, both giving away user info and giving info to the user that would be better given by a talk to an administrator. 2011/9/13 Cal Leeming [Simplicity Media Ltd] < cal.leem...@simplicitymedialtd.co.uk> > +1, if the user/pass is entered, that user is entitled so know what its own > permissions are. > > The error should give "You have insufficient access to this page" or > something like that. > > Cal > > > On Tue, Sep 13, 2011 at 6:12 PM, Florian Apolloner > wrote: > >> -1, This would leak information about the users (But I am sure that's >> discussed at length in the other threads) >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Django developers" group. >> To view this discussion on the web visit >> https://groups.google.com/d/msg/django-developers/-/5iy7pazGNGkJ. >> >> 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. > -- 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.
