Helooo any body is here?
22 Mart 2015 Pazar 16:14:03 UTC+2 tarihinde Mesut Gülecen yazdı:
>
> Hi, my name is Mesut Gülecen, currently in second year of engineering
> at Canakkale Onsekiz Mart University in Turkey.
> I want to contribute to the development of Django. I have working upon
> Djang
Firstly, this is really a question for django-users ... this mailing list
is for discussion of the development _of_ Django, not _with_ Django.
On 24 March 2015 at 13:16, Ma Yuping wrote:
> django V1.6.8
>
> Let URL be:
>
> url(r'^blog/(?P\d+)/$', views.index, name='index'),
>
> url(r'^blog/(?P\d
django V1.6.8
Let URL be:
url(r'^blog/(?P\d+)/$', views.index, name='index'),
url(r'^blog/(?P\d+)/article/(?P\d+)/view/$',
views.article, name='article'),
Input following urls to the the browser:
blog/1/
blog/1/1/
blog/1/article/1/
blog/1/1/1/1/article/1/1/1/1/
blog/bb/1/1/1/
...
They
On Mon, 2015-03-23 at 19:16 -0600, Carl Meyer wrote:
> And it still seems to me that it's bad for Django's default config to
> set `level: ERROR` and `propagate: False` on the django.request and
> django.security loggers, as that prevents those logs from propagating to
> higher-level handlers someo
I played around with this a bit, and it seems that if you
`disable_existing_loggers` but mention a specific pre-existing logger in
your new config, that logger (and its children) are not disabled. So in
your example here, because you're including the 'django' logger in your
new config, it and its c
Hm, now I wonder if that blog post in my initial post is entirely correct.
This config seems to send all Django logging to stdout (regardless of the
value of disable_existing_loggers). The difference from the initially
proposed doc patch is that this config redefines the 'django' logger
instead
On Monday, March 23, 2015 at 9:45:12 PM UTC+1, Wim Feijen wrote:
>
> This may sound stupid, but I actually use Logbook for logging because I
> find it easy to use.
>
Why would this sound stupid? Logbook is a nice library and actually worth
thinking about if we start using dependencies in Django.
This may sound stupid, but I actually use Logbook for logging because I
find it easy to use.
On Monday, 23 March 2015 18:48:26 UTC+1, Tim Graham wrote:
>
> The alternative to a new setting would be to revert the "merging" behavior
> of the django.utils.log.DEFAULT_LOGGING and settings.LOGGING en
This is what we're using to send to loggly. I'm not honestly 100% sure it
works as intended but it gets the job done. It would be great if we could
conditionally log to console when running in a local dev environment.
LOGGING = {
'version': 1,
'disable_existing_loggers': True,
'form
On 03/23/2015 12:18 PM, Carl Meyer wrote:
> On 03/23/2015 11:48 AM, Tim Graham wrote:
>> The alternative to a new setting would be to revert the "merging"
>> behavior of the django.utils.log.DEFAULT_LOGGING and settings.LOGGING
>> entirely. This original design was proposed by Claude in
>> https://
On 03/23/2015 11:48 AM, Tim Graham wrote:
> The alternative to a new setting would be to revert the "merging"
> behavior of the django.utils.log.DEFAULT_LOGGING and settings.LOGGING
> entirely. This original design was proposed by Claude in
> https://code.djangoproject.com/ticket/18993#comment:7, b
The alternative to a new setting would be to revert the "merging" behavior
of the django.utils.log.DEFAULT_LOGGING and settings.LOGGING entirely. This
original design was proposed by Claude in
https://code.djangoproject.com/ticket/18993#comment:7, but now we realize
disable_existing_loggers=Tru
On 03/22/2015 08:23 PM, Carl Meyer wrote:
> The first, more complex and more important question is: how do we fix
> Django's logging config process to be less broken, so that the best
> advice for getting it to do what you what isn't "disable Django's
> interference entirely and do it yourself."? I
Hi I am nterested in participating in the Google Summer of Code and I look
web side. I want to work "Test Framework Cleanup" or SQLAlchemy / NoSQL
integration parts. I think if you can help me I can accomplish.
22 Mart 2015 Pazar 16:14:03 UTC+2 tarihinde Mesut Gülecen yazdı:
>
> Hi, my name is
On Sunday, March 22, 2015 at 8:22:10 PM UTC+1, Tim Graham wrote:
>
> I'm not sure about the background of that idea, but it might be somewhat
> obsolete. In Django 1.8, we integrated django-secure and its security
> checks. These run as part of the system check framework:
> https://docs.django
15 matches
Mail list logo
