Re: Should ugettext_lazy return instanceof unicode? Or are reusable apps responsible for calling force_text a lot?
hi. IMHO here single line on your app and code like
# -*- coding: utf-8 -*-
put it explicity in calling app of your source code.
or could use (for python 2.7)
[1] https://docs.python.org/2/library/codecs.html#module-codecs
.ps i used this with python-sphinx and solve lot of issues with pt-BR
strings.
--
gilberto dos santos alves
+55(11)9-8646-5049
sao paulo - sp - brasil
2016-10-21 18:49 GMT-02:00 Mike Edmunds <medmu...@gmail.com>:
> A user has reported an issue
> <https://github.com/anymail/django-anymail/issues/34> with a Django
> reusable app I maintain, where they're passing my app a ugettext_lazy
> object that I ultimately pass to the requests package. Because
> instanceof(lazystr, unicode) is False, requests and urllib.urlencode
> mis-handle the text, leading to a UnicodeEncodeError or an
> incorrectly-encoded query string.
>
> I'm wondering what the right fix for this is:
>
>1. Should the result of ugettext_lazy somehow inherit from unicode? If
>indeed the "result of a ugettext_lazy() call can be used wherever you would
>use a unicode string" (docs
>
> <https://docs.djangoproject.com/en/1.10/topics/i18n/translation/#working-with-lazy-translation-objects>),
>then it would seem to be a problem that isinstance(lazystr, unicode) isn't
>true. Both requests
>
> <https://github.com/kennethreitz/requests/blob/v2.11.1/requests/models.py#L96-L97>
>and urllib.urlencode
><https://github.com/python/cpython/blob/2.7/Lib/urllib.py#L1351> (also
>py3 urllib.parse.urlencode
><https://github.com/python/cpython/blob/3.6/Lib/urllib/parse.py#L875>)
>use instanceof tests to detect text strings. (And unfortunately, that's
>probably
>
> <http://stackoverflow.com/questions/1303243/how-to-find-out-if-a-python-object-is-a-string>
>a lot more common than duck-typing in this case.)
>2. Or should my reusable app be calling force_text on *everything* it
>might receive from its callers before passing on to other packages?
>Essentially saying, lazy strings are really only valid while inside the
>Django world, and a (currently-undocumented) responsibility of reusable
>apps is to convert all lazy strings before handing them off to other
>(non-Django) python code.
>3. Or should I just be telling my app's users to call force_text
>themselves if they're using ugettext_lazy? (Not thrilled with this idea, as
>missing it can lead to very subtle errors. See the 'p4' example below. And
>this might warrant a clarification to "... can be used wherever you would
>use a unicode string..." in the docs.)
>4. Or...?
>
> Here's an (extremely pared-down) example demonstrating the specific
> problem:
>
> # My reusable app passes several string params from the caller to requests:
> import requests
> def my_reusable_app(params):
> return requests.post('http://example.com', params=params)
>
> # Code in the calling app:
> from django.utils.translation import ugettext, ugettext_lazy
> response = my_reusable_app({
> 'p1': u"alpha\u0391", # works correctly
> 'p2': ugettext(u"beta\u0392"), # works correctly
> 'p3': ugettext_lazy(u"gamma\u0393"), # requests: UnicodeEncodeError "in
> position 0" (!)
> 'p4': ugettext_lazy(u"ASCII"), # urlencode: generates
> "p4=A=S=C=I=I" rather than "p4=ASCII"
> })
>
> print(response.request.url)
>
> The UnicodeEncodeError in p3 results from requests.models._encode_params
> <https://github.com/kennethreitz/requests/blob/v2.11.1/requests/models.py#L96-L97>
> not realizing the ugettext_lazy object is unicode, and failing to encode it
> to utf-8 before handing off to urlencode.
>
>
> If you comment p3 out, the exception goes away, but urlencode
> <https://github.com/python/cpython/blob/2.7/Lib/urllib.py#L1351> fails to
> realize the p4 ugettext_lazy object is text, and incorrectly encodes it as a
> sequence of individual character params.
>
>
> [Above is all Python 2.7, but also applies to python3; substitute "str"
> wherever I wrote "unicode". Django 1.8--1.10, and probably others.]
>
>
> Thanks for any advice. Happy to take a shot at proposing doc changes, if
> that's the right answer.
>
>
> Mike
>
>
> --
> You received this message because you are subscribed to the Google Groups
> "Django developers (Contributions to Django itself)" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to django-developers+unsubscr...@googlegroups.com.
> To post to this group, send email to django-developers@googlegr
Re: Need help with MySQL 5.7 crashing on Django's Jenkins
hummm! thanks. i will continue search for more precise aswers and solutions. regards. 2016-08-02 17:27 GMT-03:00 Tim Graham <timogra...@gmail.com>: > I'm not sure exceeding max_connections is the issue. We have up to 8 > executors on each machine and the tests aren't running in parallel, so I > think we wouldn't have more than 8 connections unless running the tests can > open more than 1 connection? Also, we don't expect 8 all executors to all > be running MySQL builds at the same time. > > In looking at innodb_buffer_pool_instances, I see that it only takes > effect if innodb_buffer_pool_size is greater than 1GB (defaults to 128MB). > Is the buffer pool stored on disk? We moved the datadir from /var/lib/mysql > to /mnt/mysql_tempfs which is a 2GB tmpfs, so I'm wondering if we need to > increase that tmpfs accordingly. > > MySQL docs say, "For best efficiency, specify a combination of > innodb_buffer_pool_instances and innodb_buffer_pool_size so that each > buffer pool instance is at least 1GB." We have 14GB of RAM on the Jenkins > machine -- if we have to dedicate 8 GB to MySQL, that seems too much. > > https://dev.mysql.com/doc/refman/5.6/en/innodb-multiple-buffer-pools.html > > Here's the result of the queries you mentioned: > > mysql> show variables like '%buffer%'; > +-++ > | Variable_name | Value | > +-++ > | bulk_insert_buffer_size | 8388608| > | innodb_buffer_pool_chunk_size | 134217728 | > | innodb_buffer_pool_dump_at_shutdown | ON | > | innodb_buffer_pool_dump_now | OFF| > | innodb_buffer_pool_dump_pct | 25 | > | innodb_buffer_pool_filename | ib_buffer_pool | > | innodb_buffer_pool_instances| 1 | > | innodb_buffer_pool_load_abort | OFF| > | innodb_buffer_pool_load_at_startup | ON | > | innodb_buffer_pool_load_now | OFF| > | innodb_buffer_pool_size | 134217728 | > | innodb_change_buffer_max_size | 25 | > | innodb_change_buffering | all| > | innodb_log_buffer_size | 16777216 | > | innodb_sort_buffer_size | 1048576| > | join_buffer_size| 262144 | > | key_buffer_size | 536870912 | > | myisam_sort_buffer_size | 8388608| > | net_buffer_length | 16384 | > | preload_buffer_size | 32768 | > | read_buffer_size| 131072 | > | read_rnd_buffer_size| 262144 | > | sort_buffer_size| 262144 | > | sql_buffer_result | OFF| > +-++ > > mysql> show variables like '%connec%'; > +---+-+ > | Variable_name | Value | > +---+-+ > | character_set_connection | utf8| > | collation_connection | utf8_general_ci | > | connect_timeout | 10 | > | disconnect_on_expired_password| ON | > | init_connect | | > | max_connect_errors| 100 | > | max_connections | 151 | > | max_user_connections | 0 | > | performance_schema_session_connect_attrs_size | 512 | > +---+-+ > > > > On Tuesday, August 2, 2016 at 11:49:07 AM UTC-4, gilberto dos santos alves > wrote: > >> hi. IMO vars for django may uses this values inside [MYSQLD], cause >> max_connections default is 100 >> >> innodb_buffer_pool_instances=8 >> max_connections=255 >> >> you could verify your environment using console command >> >> mysql -u your-user -p[your-password-whit-nospace] >> >> show variables like '%connec%'; >> >> show variables like '%buffer%'; >> >> >> for example my env show: >> mysql> show variables like '%buffer%'; >> +--+--+ >> | Variable_name| Value| >> +--+--+ >> | bulk_insert_buffer_size | 8388608 | >&g
Re: Need help with MySQL 5.7 crashing on Django's Jenkins
hi. please post your /etc/my.ini (or your equiv. mysql ini config file). 2016-08-01 21:05 GMT-03:00 Tim Graham <timogra...@gmail.com>: > Sometimes the MySQL 5.7.13 builds on Ubuntu 16.04 are failing with "Lost > connection to MySQL server during query" because the MySQL server restarts > during the tests. I wonder if anyone has an idea about how to solve this. > Looking through the MySQL error log, I think this is the root cause: > > 2016-08-01T23:02:56.636617Z 0 [ERROR] [FATAL] InnoDB: Semaphore wait has > lasted > 600 seconds. We intentionally crash the server because it appears > to be hung. > 2016-08-01 23:02:56 0x7f5fb75d8700 InnoDB: Assertion failure in thread > 140049074980608 in file ut0ut.cc line 920 > InnoDB: We intentionally generate a memory trap. > InnoDB: Submit a detailed bug report to http://bugs.mysql.com. > InnoDB: If you get repeated assertion failures or crashes, even > InnoDB: immediately after the mysqld startup, there may be > InnoDB: corruption in the InnoDB tablespace. Please refer to > InnoDB: > http://dev.mysql.com/doc/refman/5.7/en/forcing-innodb-recovery.html > InnoDB: about forcing recovery. > 23:02:56 UTC - mysqld got signal 6 ; > This could be because you hit a bug. It is also possible that this binary > or one of the libraries it was linked against is corrupt, improperly built, > or misconfigured. This error can also be caused by malfunctioning hardware. > Attempting to collect some information that could help diagnose the > problem. > As this is a crash and something is definitely wrong, the information > collection process might fail. > > key_buffer_size=536870912 > read_buffer_size=131072 > max_used_connections=4 > max_threads=151 > thread_count=4 > connection_count=4 > It is possible that mysqld could use up to > key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = > 584285 K bytes of memory > Hope that's ok; if not, decrease some variables in the equation. > > Thread pointer: 0x0 > Attempting backtrace. You can use the following information to find out > where mysqld died. If you see no messages after this, something went > terribly wrong... > stack_bottom = 0 thread_stack 0x20 > /usr/sbin/mysqld(my_print_stacktrace+0x3b)[0xe7bdab] > /usr/sbin/mysqld(handle_fatal_signal+0x489)[0x783759] > /lib/x86_64-linux-gnu/libpthread.so.0(+0x113d0)[0x7f60131dc3d0] > /lib/x86_64-linux-gnu/libc.so.6(gsignal+0x38)[0x7f6012596418] > /lib/x86_64-linux-gnu/libc.so.6(abort+0x16a)[0x7f601259801a] > /usr/sbin/mysqld[0x759764] > /usr/sbin/mysqld(_ZN2ib5fatalD1Ev+0x145)[0x110c905] > /usr/sbin/mysqld(srv_error_monitor_thread+0xe2d)[0x10aa34d] > /lib/x86_64-linux-gnu/libpthread.so.0(+0x76fa)[0x7f60131d26fa] > /lib/x86_64-linux-gnu/libc.so.6(clone+0x6d)[0x7f6012667b5d] > The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html > contains > information that should help you find out what is causing the crash. > > -- > You received this message because you are subscribed to the Google Groups > "Django developers (Contributions to Django itself)" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to django-developers+unsubscr...@googlegroups.com. > To post to this group, send email to django-developers@googlegroups.com. > Visit this group at https://groups.google.com/group/django-developers. > To view this discussion on the web visit > https://groups.google.com/d/msgid/django-developers/3f787f25-2e3f-49b1-b6a3-7a3411e70a9b%40googlegroups.com > <https://groups.google.com/d/msgid/django-developers/3f787f25-2e3f-49b1-b6a3-7a3411e70a9b%40googlegroups.com?utm_medium=email_source=footer> > . > For more options, visit https://groups.google.com/d/optout. > -- gilberto dos santos alves +55(11)9-8646-5049 sao paulo - sp - brasil -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-developers+unsubscr...@googlegroups.com. To post to this group, send email to django-developers@googlegroups.com. Visit this group at https://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/CAP9G-NKdUmCcWUn0syVRtMRCwdKYgO%3DyXf13%3DfXgZABaBsW9MQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: django-firebird for django 1.8.x alpha
hi. i will make some testes with firebird 2.0.5 and access to comercial software lojafacil that use firebird. thanks for message. 2016-04-06 8:13 GMT-03:00 mariuz <map...@gmail.com>: > The current master branch is being developed under django 1.8.x > > This is still in alpha status but I think the base code works pretty well. > > Any feedback wiil be appreciated. > > > https://github.com/maxirobaina/django-firebird/commits/master > > -- > You received this message because you are subscribed to the Google Groups > "Django developers (Contributions to Django itself)" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to django-developers+unsubscr...@googlegroups.com. > To post to this group, send email to django-developers@googlegroups.com. > Visit this group at https://groups.google.com/group/django-developers. > To view this discussion on the web visit > https://groups.google.com/d/msgid/django-developers/dcfb44eb-8dd0-49b0-817e-4576097e5d32%40googlegroups.com > <https://groups.google.com/d/msgid/django-developers/dcfb44eb-8dd0-49b0-817e-4576097e5d32%40googlegroups.com?utm_medium=email_source=footer> > . > For more options, visit https://groups.google.com/d/optout. > -- gilberto dos santos alves +55(11)9-8646-5049 sao paulo - sp - brasil -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-developers+unsubscr...@googlegroups.com. To post to this group, send email to django-developers@googlegroups.com. Visit this group at https://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/CAP9G-N%2BMr-t_4eeg54C1XK9eB5mJbo-dx%2Bjey24xtnS%2B0tV5KQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: Help!!
hi. this a list for django-development discussions. but anyway for python tutorial [1] see [1] https://docs.python.org/2/tutorial/ 2016-03-20 14:31 GMT-03:00 Chitra Sivakumar <chitra.si...@gmail.com>: > Hi , > > I am new to open source and python, I am interested in doing open source > contribution. It will be great !! if some mentor can help me getting > started. > > regards > chitra > > -- > You received this message because you are subscribed to the Google Groups > "Django developers (Contributions to Django itself)" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to django-developers+unsubscr...@googlegroups.com. > To post to this group, send email to django-developers@googlegroups.com. > Visit this group at https://groups.google.com/group/django-developers. > To view this discussion on the web visit > https://groups.google.com/d/msgid/django-developers/CAHwHwmVgJV3hj0PLn1_ntvjhWWGJRCYwNcprfQk-p%3DeZPMRU_A%40mail.gmail.com > <https://groups.google.com/d/msgid/django-developers/CAHwHwmVgJV3hj0PLn1_ntvjhWWGJRCYwNcprfQk-p%3DeZPMRU_A%40mail.gmail.com?utm_medium=email_source=footer> > . > For more options, visit https://groups.google.com/d/optout. > -- gilberto dos santos alves +55(11)9-8646-5049 sao paulo - sp - brasil -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-developers+unsubscr...@googlegroups.com. To post to this group, send email to django-developers@googlegroups.com. Visit this group at https://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/CAP9G-NK6151MFJP5e1EiF2gYCHdB%3DoZwkNLFxHvkOo1TosqQkg%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: confusion about contributions (login using github account)
2016-03-02 23:19 GMT-03:00 Russell Keith-Magee <russ...@keith-magee.com>: > Hi Becka, > > On Thu, Mar 3, 2016 at 8:55 AM, Becka <beckas...@gmail.com> wrote: > >> Hi, >> >> I've been spending some time looking over the docs, and I'm really >> interested in making them more approachable to relative n00bs like myself, >> particularly when it comes to contributing to Django and the docs. >> > > Fantastic! This sort of contribution is most appreciated! Thanks for > offering to help out. > > >> It seems like there's some conflicting information around where to look >> for issues. >> >> * There's one address <https://code.djangoproject.com/newticket> where >> you need to log in, but I can't see where to sign up >> >> * There's another url >> <https://code.djangoproject.com/query?status=!closed=1>where there >> are some "easy pickings" tickets >> >> Where can tickets be filed? Where should someone starting out look for >> tickets, and can they (we) open issues? I'd like to clarify what the docs >> ssay about this point. >> > > We’re using a system called Trac as an issue tracker; when you hit > code.djangoproject.com, that’s our Trac instance. > > Trac has a number of features, including an issue tracker, a wiki, and a > few other bits and bobs. The homepage of the Trac instance is a wiki page > that tells you where to go next (or, at least, tries to!) The first two > links under “getting started” on that page are links into the ticket > tracker; If you’re looking for somewhere to make your first contribution > “easy pickings” is a list of tickets that has been pre-filtered to only > contain issues that might be easy for a newcomer to tackle. Easy pickings > is a good place to start if you want to make your first contribution. > > The other link (“tickets”) is a link to a wiki page that contains a couple > of other pre-canned queries that can be helpful. All of those pre-canned > queries will ultimately end up at > https://code.djangoproject.com/query, which is the searchable index of > all tickets. From there, you can add and remove filters to find the exact > ticket you want. > > If you want to report a new issue, the first link you provide (/newticket) > is where you should go (unless it’s a security issue, in which case a whole > other procedure is required). The login is required as a spam measure - if > you don’t lock down Trac, random bots drop by and open tickets for !!Fr33 > STUFF!!. > if someone do not have a login for github.com please go to https://github.com/ and create one login using signup button. After that login is active, use your github login on djangoproject.com > > I hope that helps - if there’s anything else we can do to explain the > process we have, let us know! > > Yours > Russ Magee %-) > > -- > You received this message because you are subscribed to the Google Groups > "Django developers (Contributions to Django itself)" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to django-developers+unsubscr...@googlegroups.com. > To post to this group, send email to django-developers@googlegroups.com. > Visit this group at https://groups.google.com/group/django-developers. > To view this discussion on the web visit > https://groups.google.com/d/msgid/django-developers/CAJxq848NRqQO6WpqOX4ZAs%2Bm%2B_JZqRievPq8Cmiw82UdaF28jA%40mail.gmail.com > <https://groups.google.com/d/msgid/django-developers/CAJxq848NRqQO6WpqOX4ZAs%2Bm%2B_JZqRievPq8Cmiw82UdaF28jA%40mail.gmail.com?utm_medium=email_source=footer> > . > > For more options, visit https://groups.google.com/d/optout. > -- gilberto dos santos alves +55(11)9-8646-5049 sao paulo - sp - brasil -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-developers+unsubscr...@googlegroups.com. To post to this group, send email to django-developers@googlegroups.com. Visit this group at https://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/CAP9G-NJFuYb1VnWbX6Y_ugG7po-F-D%3D1Eo4Us64XtLzQfxr61w%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: Not able to install Django in Windows10
Hi. Please verify: 1 - what is your version especify name (home, professional, etc) 32 or 64bits, locale / language, python version 2 - look at your environment var system %PATH% (not user path) (to see open cmd and echo %PATH% 3 - if your %PATH% do not have python/scripts folder declared or firewall active block python pip executions. 2016-02-22 3:09 GMT-03:00 Nasif Noorudeen <nas...@gmail.com>: > I am not able to install Django 1.9.2(any version of Django ) in Windows > 10. I am using following command to install Django > > pip install Django==1.9.2 > > it is working fine in Windows 8 and Windows 7. It seems like this is is the > issue with pip tool > > If i simply type pip.exe also nothing is happening in console. > > If anyone facing same issue in Windows 10. Please help to solve this > > -- > You received this message because you are subscribed to the Google Groups > "Django developers (Contributions to Django itself)" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to django-developers+unsubscr...@googlegroups.com. > To post to this group, send email to django-developers@googlegroups.com. > Visit this group at https://groups.google.com/group/django-developers. > To view this discussion on the web visit > https://groups.google.com/d/msgid/django-developers/aa1bc911-cf2d-4e41-8872-4382c0133f21%40googlegroups.com > <https://groups.google.com/d/msgid/django-developers/aa1bc911-cf2d-4e41-8872-4382c0133f21%40googlegroups.com?utm_medium=email_source=footer> > . > For more options, visit https://groups.google.com/d/optout. > -- gilberto dos santos alves +55(11)9-8646-5049 sao paulo - sp - brasil -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-developers+unsubscr...@googlegroups.com. To post to this group, send email to django-developers@googlegroups.com. Visit this group at https://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/CAP9G-N%2B4wt%2BC%2BLvXz1Re4A9n2En32Nac-a_b5yQc0EjkDpeS1w%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: Setting up Django Over Apache Web-server
hi. if you have cpanel see [1] or another similiar shared host plan. [1] http://support.hostgator.com/articles/django-with-fastcgi 2015-08-03 20:36 GMT-03:00 Mudassar Hashmi <mudassarziahash...@hotmail.com>: > Please help to upload django on apache web server with without terminal > access to web server. > > Regards, > > Mudassar Hashmi > > -- > You received this message because you are subscribed to the Google Groups > "Django developers (Contributions to Django itself)" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to django-developers+unsubscr...@googlegroups.com. > To post to this group, send email to django-developers@googlegroups.com. > Visit this group at http://groups.google.com/group/django-developers. > To view this discussion on the web visit > https://groups.google.com/d/msgid/django-developers/COL126-W255BB734B46EC91F6C6D58C8770%40phx.gbl > <https://groups.google.com/d/msgid/django-developers/COL126-W255BB734B46EC91F6C6D58C8770%40phx.gbl?utm_medium=email_source=footer> > . > For more options, visit https://groups.google.com/d/optout. > -- gilberto dos santos alves +55(11)9-8646-5049 sao paulo - sp - brasil -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-developers+unsubscr...@googlegroups.com. To post to this group, send email to django-developers@googlegroups.com. Visit this group at http://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/CAP9G-NL%3DGxW4Jw_zxYaUCCDJ1f8rPeJis%2BiDq84nBDR4Qnm01Q%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: Quick question re typo-fixing etiquette
please see faq at [1] or [2] [1] https://docs.djangoproject.com/en/1.6/faq/ [2] irc://irc.freenode.net/django 2014/1/24 James Turley <jamesturley1...@googlemail.com> > Hi all, > > I'm a relatively novice Pythonist, but a hardened and incorrigible > spelling/grammar pedant, so I feel I could contribute in some small way by > fixing language errors in the docs as required. > > In the submitting patches guide, it says: "If you are fixing a really > trivial issue, for example changing a word in the documentation, the > preferred way to provide the patch is using GitHub pull requests without a > Trac ticket. Trac tickets are still acceptable." That's fine. My question > is: how 'trivial' should each pull request be? Should I make one for each > file I go through, or one for every last stray apostrophe, or something > else? I don't want to flood the committers with hundreds of meaningless > typo fixes and grammar corrections, at least if that's not the done thing. > > Thanks > James > > -- > You received this message because you are subscribed to the Google Groups > "Django developers" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to django-developers+unsubscr...@googlegroups.com. > To post to this group, send email to django-developers@googlegroups.com. > Visit this group at http://groups.google.com/group/django-developers. > To view this discussion on the web visit > https://groups.google.com/d/msgid/django-developers/b394cfd0-09ff-4409-972f-a688171580ef%40googlegroups.com > . > For more options, visit https://groups.google.com/groups/opt_out. > -- gilberto dos santos alves +55.11.98646-5049 sao paulo - sp - brasil -- You received this message because you are subscribed to the Google Groups "Django developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-developers+unsubscr...@googlegroups.com. To post to this group, send email to django-developers@googlegroups.com. Visit this group at http://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/CAP9G-NK6P9dDKNc3J_9et7LSRaBaudUDOU2S7dCX%2BByXQUPfjQ%40mail.gmail.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: Enforce the use of a unicode string in settings.LANGUAGES
yes i will try with django 1.6.
2014/1/22 Henrique Romano <chrom...@gmail.com>
> On Wed, Jan 22, 2014 at 11:38 AM, gilberto dos santos alves <
> gsa...@gmail.com> wrote:
>
>> please look details about on [1]. if you put
>>
>> # -*- coding: utf-8 -*- on sources and config files for django your string
>> "português" will be automatically handled.
>>
>>
> Can you just try what I reported? For example:
>
> $ cat ~/foofoo.py
> # -*- coding: utf-8 -*-
> from django.utils.translation import ugettext
>
> print ugettext("Português")
> $ python ~/foofoo.py
> Traceback (most recent call last):
> ...
> UnicodeDecodeError: 'ascii' codec can't decode byte 0xc3 in position 7:
> ordinal not in range(128)
>
> So, I'm not sure what you are talking about.
> --
> Henrique Romano
>
> --
> You received this message because you are subscribed to the Google Groups
> "Django developers" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to django-developers+unsubscr...@googlegroups.com.
> To post to this group, send email to django-developers@googlegroups.com.
> Visit this group at http://groups.google.com/group/django-developers.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/django-developers/CA%2BEHudKiJcgLQg-K2pwQrBFFcCTr%2BpV_t9VqmkSo%3D6n-6Kjqaw%40mail.gmail.com
> .
>
> For more options, visit https://groups.google.com/groups/opt_out.
>
--
gilberto dos santos alves
+55.11.98646-5049
sao paulo - sp - brasil
--
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to django-developers+unsubscr...@googlegroups.com.
To post to this group, send email to django-developers@googlegroups.com.
Visit this group at http://groups.google.com/group/django-developers.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-developers/CAP9G-NLgyqk%2ByUtSaZ6ueTbLiFfb2xLVCrT8n2Si7%3DgxKE626A%40mail.gmail.com.
For more options, visit https://groups.google.com/groups/opt_out.
Re: Enforce the use of a unicode string in settings.LANGUAGES
please look details about on [1]. if you put # -*- coding: utf-8 -*- on sources and config files for django your string "português" will be automatically handled. regards. [1] http://docs.python.org/2/howto/unicode.html 2014/1/22 Henrique Romano <chrom...@gmail.com> > Hi, > > On Wed, Jan 22, 2014 at 12:37 AM, gilberto dos santos alves < > gsa...@gmail.com> wrote: > >> please see that it is python directive not django. for all sources it is >> a good practive for all we that use pt-br utf-8 explicit this on second >> line of file python code >> >> # -*- coding: utf-8 -*- >> >> > Specyfing the encoding of the file don't make strings unicode > automatically, therefore doing it won't solve the problem. I think the > problem is still relevant. > > Thanks > > -- > You received this message because you are subscribed to the Google Groups > "Django developers" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to django-developers+unsubscr...@googlegroups.com. > To post to this group, send email to django-developers@googlegroups.com. > Visit this group at http://groups.google.com/group/django-developers. > To view this discussion on the web visit > https://groups.google.com/d/msgid/django-developers/CA%2BEHudJHqD4w%2B3ByRq8v4Mu6wbQ2DR0LqvNOJUyLfU_V8fZkGA%40mail.gmail.com > . > > For more options, visit https://groups.google.com/groups/opt_out. > -- gilberto dos santos alves +55.11.98646-5049 sao paulo - sp - brasil -- You received this message because you are subscribed to the Google Groups "Django developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-developers+unsubscr...@googlegroups.com. To post to this group, send email to django-developers@googlegroups.com. Visit this group at http://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/CAP9G-NLpjBRfs83NvQ3gCYtD2NuR6Ye8DgHbKd%2B0OynGM3RXAw%40mail.gmail.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: Enforce the use of a unicode string in settings.LANGUAGES
please see that it is python directive not django. for all sources it is a
good practive for all we that use pt-br utf-8 explicit this on second line
of file python code
# -*- coding: utf-8 -*-
regards!
2014/1/21 Henrique Romano <chrom...@gmail.com>
> Hi,
>
> As per the documentation[1], it is not clear that you _must_ use a unicode
> string for the language name. If you don't use an unicode string, the
> following can happen:
>
> >>> from django.utils.translation import ugettext
> >>> ugettext("Português")
> Traceback (most recent call last):
> ...
> UnicodeDecodeError: 'ascii' codec can't decode byte 0xc3 in position 7:
> ordinal not in range(128)
>
> As opposed to:
>
> >>> ugettext(u"Português")
> u'Portugu\xeas'
>
> I was just having an issue where the languages available was being
> rendered in the template, but since TEMPLATE_DEBUG was enabled, no errors
> was generated in the development environment. Switching TEMPLATE_DEBUG off
> in the production resulted in an exception with almost no clue on what
> happened.
>
> What do you guys think about making it clear that the user should always
> use an unicode string for the LANGUAGES setting?
>
> [1] https://docs.djangoproject.com/en/dev/ref/settings/#languages
> --
> Henrique Romano
>
> --
> You received this message because you are subscribed to the Google Groups
> "Django developers" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to django-developers+unsubscr...@googlegroups.com.
> To post to this group, send email to django-developers@googlegroups.com.
> Visit this group at http://groups.google.com/group/django-developers.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/django-developers/CA%2BEHudKfPXxry6T2tW_6ZNFzJgAJUHs3nO_mLkdp3Xk2wS09xg%40mail.gmail.com
> .
> For more options, visit https://groups.google.com/groups/opt_out.
>
--
gilberto dos santos alves
+55.11.98646-5049
sao paulo - sp - brasil
--
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to django-developers+unsubscr...@googlegroups.com.
To post to this group, send email to django-developers@googlegroups.com.
Visit this group at http://groups.google.com/group/django-developers.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-developers/CAP9G-NLKRTiyM_P-1aMR2dKZh%3DgNU_0s6GYGoXLO%2BjmzZYnsCw%40mail.gmail.com.
For more options, visit https://groups.google.com/groups/opt_out.
Re: Strange crash with ugettext_lazy when accent letter
please see your settings.py [1],
default_charset is utf-8?;
use_l10n is set true?
what is default content-type?
we have this issue when use pt-br chars like õ and ç but with correct setup
this has worked.
[1] https://docs.djangoproject.com/en/dev/ref/settings/
2013/12/16 Bastien Sevajol <sevajol.bast...@gmail.com>
> Hi,
>
> I want ask to this mailing list before open bug issue on code.django.
> When use ugettext_lazy with accent like "â" some strange behaviour
> happens. Exemple:
>
> # -*- coding: utf-8 -*-
>> from django.db import models
>>
> from django.utils.translation import ugettext_lazy as _
>>
> class MyModel(models.Model):
>>
>> name = models.CharField(_(u"name"), max_length=80)
>> type = models.CharField(max_length=1,
>> choices=(('a', '*â*'), ('b', 'b')),
>> default='b')
>>
>
> With this code the form will not be render. No error or warning, form is
> just not rendered. If 'â' is replaced by 'a', form is rendered correctly.
> ugettext_lazy Should not report error or somethig ?
>
> Thank's.
>
> --
> You received this message because you are subscribed to the Google Groups
> "Django developers" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to django-developers+unsubscr...@googlegroups.com.
> To post to this group, send email to django-developers@googlegroups.com.
> Visit this group at http://groups.google.com/group/django-developers.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/django-developers/1db21371-e1b6-4426-83f7-b6ba7d2cb025%40googlegroups.com
> .
> For more options, visit https://groups.google.com/groups/opt_out.
>
--
gilberto dos santos alves
+55.11.98646-5049
sao paulo - sp - brasil
--
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to django-developers+unsubscr...@googlegroups.com.
To post to this group, send email to django-developers@googlegroups.com.
Visit this group at http://groups.google.com/group/django-developers.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-developers/CAP9G-NJ_6U1vMnMKX7FMvZbv%2B%3DE_MOx1CrTgm3wRsBzP%2BY-p9g%40mail.gmail.com.
For more options, visit https://groups.google.com/groups/opt_out.
Re: make the source code of the django tutorial available ?
very great task! 2013/9/8 German Larrain <germanlarra...@gmail.com>: > I know there are different opinions on this topic but if anyone is > interested, I created a repo for the tutorial. The idea is to have branches > and tags that match those of the documentation. > > https://github.com/glarrain/django-tutorial-source-code > > A nice advantage of that is to be able to compare how the resulting code of > the official tutorial changes between releases. Others are: > > Be able to check that the tutorial is correct (it's kind of difficult to > spot mistakes from the documentation, either rendered or rst), i.e. the code > works (in fact, I think I discovered a bug in the current master, which I > will file in trac ASAP). > Let the user compare at the end of the tutorial the code he/she typed with > the one in the repo. > > Best regards, > Germán > > On Wednesday, January 16, 2013 11:28:42 PM UTC-6, Russell Keith-Magee wrote: >> >> >> >> On Thu, Jan 17, 2013 at 1:17 PM, Daniel Greenfeld <pyd...@gmail.com> >> wrote: >>> >>> >>> >>> On Wednesday, January 16, 2013 4:43:14 PM UTC-8, Russell Keith-Magee >>> wrote: >>>> >>>> Hi Daniele, >>>> >>>> On Thu, Jan 17, 2013 at 7:07 AM, Daniele Procida <evi...@googlemail.com> >>>> wrote: >>>>> >>>>> >>>> 2) This is what version control is for. I'd much rather see someone do >>>> the tutorial and use version control on their own repository, rather than >>>> just pull down the latest version of a repo that contains all the code they >>>> need. >>>> >>>> Following point 2, it might be worth suggesting that people use version >>>> control during the tutorial. I'm not suggesting we turn the Django tutorial >>>> into a parallel tutorial on git, but seeding the idea in people's heads has >>>> the benefit of reinforcing best practice (you do version control everything >>>> you do, right?), and makes it easier to work around the rollback problems >>>> you describe; if they don't know what version control is, they might be >>>> encouraged to go investigate, and as a result, another code-fairy gets >>>> their >>>> wings :-) >>> >>> >>> There are already third-party versions of the Django tutorial that also >>> instruct on source control and TDD. These are great, and wonderful, but I >>> feel they overwhelm beginner Django developers with too much. >> >> >> To be clear -- I'm not suggesting we try and make the Django tutorial a >> parallel tutorial on source control. I'm just suggesting that we drop a >> gentle hint at the start of the tutorial, to the effect of: >> >> "If you know how to use a source control system (like Git), you might want >> to set up your tutorial directory as a repository. >> >> If you don't know how to use a source control system, don't worry. You >> don't need to know anything about source control to complete this tutorial. >> However, source control systems are incredibly useful tools that are used >> widely in software development, and you'd be well advised to learn how to >> use them." >> >> and then, after completing relevant blocks of work: >> >> "If you're using source control on this project, now would be a good time >> to commit what you've done." >> >> The aim is to encourage best practice, or at least make users *aware* of >> best practice, but leave the details up to them. >> >> Yours, >> Russ Magee %-) >> > -- > You received this message because you are subscribed to the Google Groups > "Django developers" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to django-developers+unsubscr...@googlegroups.com. > To post to this group, send email to django-developers@googlegroups.com. > Visit this group at http://groups.google.com/group/django-developers. > For more options, visit https://groups.google.com/groups/opt_out. -- gilberto dos santos alves +55.11.98646-5049 sao paulo - sp - brasil -- You received this message because you are subscribed to the Google Groups "Django developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-developers+unsubscr...@googlegroups.com. To post to this group, send email to django-developers@googlegroups.com. Visit this group at http://groups.google.com/group/django-developers. For more options, visit https://groups.google.com/groups/opt_out.
Re: Deprecate FCGI support in Django 1.7
remember that on "shared hosts" we do not have option to use, explicity http ports, like examples from [1]. we do not have root access, nor http.conf access for apache2/root configs. when we hare dedicated server it is easy run app with django. on shared host, all config for running django fcgi is made using with user ssh terminal, and with sftp/ftp (example filezilla), .htaccess files and cpanel. for install uwsgi we need c compiler, that we do not have on shared hosts. It is more easy and less expensive for "first-time companies using web apps" use shared hosts and only solution that i find is using fcgi. if necessary additional work todo (installs, .htaccess, etc) it is not the problem [1] http://flask.pocoo.org/docs/deploying/fastcgi/?highlight=fcgi 2013/7/15 Some Developer <someukdevelo...@gmail.com> > On 15/07/13 16:10, Florian Apolloner wrote: > >> On Monday, July 15, 2013 4:14:43 PM UTC+2, Jannis Leidel wrote: >> >> If you're suggesting to move the FastCGI code into a separate app: +1 >> >> >> I'd have just dropped it, but yes we can move it out; although someone >> else will have to step up to continue maintaining it (if there is a need >> to maintain it). >> >> Florian >> > > What about SCGI and AJP support? Is that going? > > Seems silly to drop FastCGI which is probably the most popular of three > and leave the other two intact. If you're going to drop something drop all > three. > > At least then it is clear to users that WSGI is the only supported option > in Django. > > Third parties can then maintain FastCGI, SCGI and AJP support (which I > believe all come from flup anayway). > > > -- > You received this message because you are subscribed to the Google Groups > "Django developers" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to > django-developers+unsubscribe@**googlegroups.com<django-developers%2bunsubscr...@googlegroups.com> > . > To post to this group, send email to > django-developers@**googlegroups.com<django-developers@googlegroups.com> > . > Visit this group at > http://groups.google.com/**group/django-developers<http://groups.google.com/group/django-developers> > . > For more options, visit > https://groups.google.com/**groups/opt_out<https://groups.google.com/groups/opt_out> > . > > > -- gilberto dos santos alves +55.11.98646-5049 sao paulo - sp - brasil -- You received this message because you are subscribed to the Google Groups "Django developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-developers+unsubscr...@googlegroups.com. To post to this group, send email to django-developers@googlegroups.com. Visit this group at http://groups.google.com/group/django-developers. For more options, visit https://groups.google.com/groups/opt_out.
Re: Deprecate FCGI support in Django 1.7
i start 2 months ago using fcgi inside an shared host (hostgator.com) and after lots of tries with wsgi only using fcgi was worked with apache2. but i will read and learn about uwsgi and try this. my app use version 1.6a of django is 1.6b worked using python 2.6. because parts of my app is with status development i will test this with python 2.7 too. but i agree that docs is not clear, because they mixed concepts of apache2 and django (directories static, admin etc). i am reviewing these docs soon for clarify concepts about wsgi, fcgi and if necessary uwsgi. If someone have advices or additional ref. is welcome! ;>) 2013/7/14 Florian Apolloner <f.apollo...@gmail.com>: > Hi, > > I'd like to get rid of everything FCGI-specific in Django sooner or later > (rather sooner). Flup isn't maintained since a long time and there is no > ticket tracker to report stuff. Graham pointed out that if someone wants to > use FCGI they can use > http://uwsgi-docs.readthedocs.org/en/latest/Options.html#fastcgi-socket > which doesn't even require flup, which sounds like a good compromise to me. > I'd need some help for the docs from some uWSGI users, since I have no idea > about it ;) > > Thoughts, objections? > > Cheers, > Florian > > -- > You received this message because you are subscribed to the Google Groups > "Django developers" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to django-developers+unsubscr...@googlegroups.com. > To post to this group, send email to django-developers@googlegroups.com. > Visit this group at http://groups.google.com/group/django-developers. > For more options, visit https://groups.google.com/groups/opt_out. > > -- gilberto dos santos alves +55.11.98646-5049 sao paulo - sp - brasil -- You received this message because you are subscribed to the Google Groups "Django developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-developers+unsubscr...@googlegroups.com. To post to this group, send email to django-developers@googlegroups.com. Visit this group at http://groups.google.com/group/django-developers. For more options, visit https://groups.google.com/groups/opt_out.
Re: Missing timezone support in built-in time template filter
well done. 2013/7/3 Warren Smith <wsmith...@gmail.com>: > On Mon, Jul 1, 2013 at 6:18 PM, Russell Keith-Magee > <russ...@keith-magee.com> wrote: >>> >>> >>> Agreed. >>> >>> Also, just to clarify, I think we should stick with Django's policy of >>> only supporting naive time objects, for the reasons you cited earlier in >>> this thread. >>> >>> So, any timezone support we would add to the time filter should only >>> support aware datetime objects, not aware time objects. >>> >>> Correct? >> >> >> Yes - that sounds like the right approach to me. >> > > Done. https://code.djangoproject.com/ticket/20693 is ready for somebody to > review it. It would be great if this could get into 1.6. > > -- > Warren Smith > > -- > You received this message because you are subscribed to the Google Groups > "Django developers" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to django-developers+unsubscr...@googlegroups.com. > To post to this group, send email to django-developers@googlegroups.com. > Visit this group at http://groups.google.com/group/django-developers. > For more options, visit https://groups.google.com/groups/opt_out. > > -- gilberto dos santos alves +55.11.98646-5049 sao paulo - sp - brasil -- You received this message because you are subscribed to the Google Groups "Django developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-developers+unsubscr...@googlegroups.com. To post to this group, send email to django-developers@googlegroups.com. Visit this group at http://groups.google.com/group/django-developers. For more options, visit https://groups.google.com/groups/opt_out.
Re: Django runfcgi umask: what is it meant to do and why?
yes. i agree. my tests in hostgator.com shared host show this. tests in my ubuntu 12.04 amd64 shows same problem. using django 1.5 and 1.6a, 16b. 2013/6/30 Juan Luis Boya <ntr...@gmail.com>: > They talk about there was a os.umask(0) and they created that option in > order to change it. > > But I would like to know then, why was that `os.umask(0)` there in the first > place? What was it purpose? > > On the other hand there is the confusion this option brings. Many people > think the option is intended to set the socket umask. Just in that bug > report there is a user saying "umask=0111 creates a socket with umask...". > Even Django documentation recommends you to use separate users for increased > security and tells you to set umask argument in order for them to > communicate. > > These are wrong! Setting that umask does not only not work if runfcgi is not > daemonized, but also gives write permissions to all files created by Django > to any user in its group (often the web server), potentially breaking > isolation with other applications (i.e. PHP scripts being run as the server > user). > > - Juan Luis > > -- > You received this message because you are subscribed to the Google Groups > "Django developers" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to django-developers+unsubscr...@googlegroups.com. > To post to this group, send email to django-developers@googlegroups.com. > Visit this group at http://groups.google.com/group/django-developers. > For more options, visit https://groups.google.com/groups/opt_out. > > -- gilberto dos santos alves +55.11.98646-5049 sao paulo - sp - brasil -- You received this message because you are subscribed to the Google Groups "Django developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-developers+unsubscr...@googlegroups.com. To post to this group, send email to django-developers@googlegroups.com. Visit this group at http://groups.google.com/group/django-developers. For more options, visit https://groups.google.com/groups/opt_out.
Re: Django Admin Revamp - Any updates?
yah... this is very good news for all of us. mainly when we are not root user, and are jailed without bash, zsh. thanks. i will read carefully. regards. 2013/6/19, Victor Hooi <victorh...@gmail.com>: > Hi, > > Hmm, Daniel Greenfeld (pydanny) seems to have written another one, > DjangoAdmin 2.0 as well: > > https://news.ycombinator.com/item?id=5900083 > > https://github.com/twoscoops/django-admin2 > > Cheers, > Victor > > On Monday, 11 March 2013 12:08:54 UTC+11, Pantelis Petridis wrote: >> >> I'd like to add yawd-admin <https://github.com/yawd/yawd-admin> to the >> list. It's bootstrap, up-to date with the latest core admin changes, >> stable, the github master fully supports django1.5 and has many goodies >> like modal inlines, fancybox popups for add_related , custom widgets, db >> settings, google analytics support etc. >> >> On Friday, December 14, 2012 11:36:19 AM UTC+2, is_null wrote: >>> >>> There are *many* apps providing bootstrap templates for >>> django.contrib.admin, here a few: >>> >>> - https://github.com/michaelhelmick/django-bootstrap-admin >>> - https://github.com/gkuhn1/django-admin-templates-twitter-bootstrap >>> - https://github.com/riccardo-forina/django-admin-bootstrapped >>> - https://github.com/aobo711/bootstrap-django-admin >>> - I myself did such templates. >>> >>> >>> > > -- > You received this message because you are subscribed to the Google Groups > "Django developers" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to django-developers+unsubscr...@googlegroups.com. > To post to this group, send email to django-developers@googlegroups.com. > Visit this group at http://groups.google.com/group/django-developers. > For more options, visit https://groups.google.com/groups/opt_out. > > > -- gilberto dos santos alves +55.11.98646-5049 sao paulo - sp - brasil -- You received this message because you are subscribed to the Google Groups "Django developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-developers+unsubscr...@googlegroups.com. To post to this group, send email to django-developers@googlegroups.com. Visit this group at http://groups.google.com/group/django-developers. For more options, visit https://groups.google.com/groups/opt_out.
Re: tutorial url broken
thanks. already done new link for mezzanine. 2013/4/29 Karen Tracey <kmtra...@gmail.com> > On Mon, Apr 29, 2013 at 1:52 PM, gilberto dos santos alves < > gsa...@gmail.com> wrote: > >> >> Hi. on this url:: [1] we have this link url:: [2] broken. >> >> url:: [1] https://code.djangoproject.com/wiki/Tutorials >> >> > That's in the wiki, which is (generally, except for some pages which are > locked down due to abuse in the past) editable by the community. If you > scroll to the bottom of the page, you'll see an "Edit this page" button, if > you press that you'll be able to edit the content and remove the no-longer > functioning link. > > Karen > > -- > You received this message because you are subscribed to the Google Groups > "Django developers" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to django-developers+unsubscr...@googlegroups.com. > To post to this group, send email to django-developers@googlegroups.com. > Visit this group at http://groups.google.com/group/django-developers?hl=en > . > For more options, visit https://groups.google.com/groups/opt_out. > > > -- gilberto dos santos alves +55.11.98646-5049 sao paulo - sp - brasil -- You received this message because you are subscribed to the Google Groups "Django developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-developers+unsubscr...@googlegroups.com. To post to this group, send email to django-developers@googlegroups.com. Visit this group at http://groups.google.com/group/django-developers?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
tutorial url broken
Hi. on this url:: [1] we have this link url:: [2] broken. url:: [1] https://code.djangoproject.com/wiki/Tutorials url:: [2] http://codingnstuff.com/2010/01/a-complete-blog-engine-using-django-in-60-minutes/ -- gilberto dos santos alves +55.11.98646-5049 sao paulo - sp - brasil -- You received this message because you are subscribed to the Google Groups "Django developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-developers+unsubscr...@googlegroups.com. To post to this group, send email to django-developers@googlegroups.com. Visit this group at http://groups.google.com/group/django-developers?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
Re: .rst files for tutorials of djangorocks.com
sorry. i miss this detail. 2013/4/29 Russell Keith-Magee <russ...@keith-magee.com> > Hi Gilberto, > > The site you've referenced is not officially related to the Django > project. I wasn't previously aware of the site -- we'll be having words > with them for reproducing Django content without permission. > > If you've got questions or comments about the tutorial, you'll have to > take that up with the owners of that site. > > Yours, > Russ Magee %-) > > On Mon, Apr 29, 2013 at 12:00 PM, gilberto dos santos alves < > gsa...@gmail.com> wrote: > >> Hi for all. >> >> Following this url [1], i found some clarify needs for this tutorial >> works nice. >> >> Please where i find these .rst files? I already search django.github.comand >> not found them. >> >> Thanks! >> >> url:: [1] >> http://www.djangorocks.com/tutorials/how-to-create-a-basic-blog-in-django/ >> >> -- >> gilberto dos santos alves >> +55.11.98646-5049 >> sao paulo - sp - brasil >> >> >> >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Django developers" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to django-developers+unsubscr...@googlegroups.com. >> To post to this group, send email to django-developers@googlegroups.com. >> Visit this group at >> http://groups.google.com/group/django-developers?hl=en. >> For more options, visit https://groups.google.com/groups/opt_out. >> >> >> > > -- > You received this message because you are subscribed to the Google Groups > "Django developers" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to django-developers+unsubscr...@googlegroups.com. > To post to this group, send email to django-developers@googlegroups.com. > Visit this group at http://groups.google.com/group/django-developers?hl=en > . > For more options, visit https://groups.google.com/groups/opt_out. > > > -- gilberto dos santos alves +55.11.98646-5049 sao paulo - sp - brasil -- You received this message because you are subscribed to the Google Groups "Django developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-developers+unsubscr...@googlegroups.com. To post to this group, send email to django-developers@googlegroups.com. Visit this group at http://groups.google.com/group/django-developers?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
.rst files for tutorials of djangorocks.com
Hi for all. Following this url [1], i found some clarify needs for this tutorial works nice. Please where i find these .rst files? I already search django.github.comand not found them. Thanks! url:: [1] http://www.djangorocks.com/tutorials/how-to-create-a-basic-blog-in-django/ -- gilberto dos santos alves +55.11.98646-5049 sao paulo - sp - brasil -- You received this message because you are subscribed to the Google Groups "Django developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-developers+unsubscr...@googlegroups.com. To post to this group, send email to django-developers@googlegroups.com. Visit this group at http://groups.google.com/group/django-developers?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
