Re: How to deal with potential Django bugs you come accross

[Erik Stein]

Hey Curtis --

thanks for your answer! I'll do this from now on (and of course I'll try 
me best to write a complete bug report including a proposed fix if the 
time allows).


https://code.djangoproject.com/ticket/30475#ticket

Have a nice day

-- erik


On 13.05.19 18:19, Curtis Maloney wrote:

Hi Erik,


On 5/13/19 8:22 PM, Erik Stein wrote:


Hello everyone --

 From time to time I come accross a potential bug in Django core, but 
because of a tight schedule don't have the time to dive into it and 
write a proper ticket. How would you suggest to deal with it?



my personal position would be to open a ticket with what information 
you _do_ have, so the discovery is not lost.


The "worst case" is one of the ever efficient Django Fellows comes by, 
tests it out, and closes it as "works as expected".


If you _don't_ log the issue, it _will_ be forgotten about, because 
we're all human. :)



Today e.g.

– Using i18n_patterns with prefix_default_language=True,
– trying to get the frontpage URL without a language given in the URL

works in debug mode, but gives an internal server error without any 
backtrace in production mode.


This was caused by a buggy 404.html template, but probably buggy 404 
templates should give a backtrace, too, and i18n_patterns shouldn't 
be concerned by this anyway.


Certainly a solution worthy of discussion!

Are those notes something which should get into Trac to be 
investigated later?


Absolutely yes!


Thanks for you opinion and guidance,


--
Curtis



--
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/2c2b42de-e97c-aca6-0acf-21ed84c20c33%40classlibrary.net.
For more options, visit https://groups.google.com/d/optout.

How to deal with potential Django bugs you come accross

[Erik Stein]

Hello everyone --

From time to time I come accross a potential bug in Django core, but 
because of a tight schedule don't have the time to dive into it and 
write a proper ticket. How would you suggest to deal with it?


Today e.g.

– Using i18n_patterns with prefix_default_language=True,
– trying to get the frontpage URL without a language given in the URL

works in debug mode, but gives an internal server error without any 
backtrace in production mode.


This was caused by a buggy 404.html template, but probably buggy 404 
templates should give a backtrace, too, and i18n_patterns shouldn't be 
concerned by this anyway.


Are those notes something which should get into Trac to be investigated 
later?


Thanks for you opinion and guidance,

-- erik


--
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/6e03157c-770a-cfe6-1569-e0f0c2aee122%40classlibrary.net.
For more options, visit https://groups.google.com/d/optout.

Re: Re-design "proposal" for djangoproject.com

[Erik Stein]

Am 21.05.2012 um 04:06 schrieb Adam Cezar Jenkins:

> I'm sad to hear that about the pony. The pony itself isn't the issue, the 
> issue to me is that there is a lack of branding of a real logo/mascot. 
> 
> I agree with 90% of the comparisons made in the blog post 
> http://grokcode.com/746/dear-python-why-are-you-so-ugly/

Please let me add in all politeness that I don't agree. djangoproject.com is 
not for the masses and therefore doesn't need to be over-simplified. On the 
contrary, it's for professionals who know what they are looking for.

What is missing in django marketing is IMHO a cleverly selected showcase of 
large and also small mature django sites, including in-house. A list of mature 
plugin-projects/apps would make sense, too.

Best
-- erik



Erik Stein
Programmierung, Grafik
Oranienstr. 32   10999 Berlin, Germany
fon +49 30 69201880   fax +49 30 692018809
email e...@classlibrary.net



-- 
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 a serious framework, really

[Erik Stein]

The other day I went back to one of my first django projects. It's running on 
production since 2007/2008 flawlessly serving a rather complex scientific 
database for about 10 visits/month, still using django 1.1. The reason was 
that the current maintainer needed some help with the project and django.

I was extremely happy to see how easy it was to get back to an understanding of 
the code and to show the current maintainer what he missed. He is not a 
programmer, but only got some variables wrong and missed to write a view 
function.

The problem and another problem, too, were solved within an hour.

Django has it's limits, but it is one of the most serious frameworks out there. 
Thanks to everyone who contributes to it and especially to those who took the 
best of python and designed an API and project structure which prove to be 
well-arranged til today.

-- erik




Am 11.04.2012 um 14:54 schrieb Russell Keith-Magee:

> On Wednesday, 11 April 2012 at 8:10 PM, Jason Ma wrote:  

[snip]


Erik Stein
Programmierung, Grafik
Oranienstr. 32   10999 Berlin, Germany
fon +49 30 69201880   fax +49 30 692018809
email e...@classlibrary.net



-- 
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: Import problem starting with r12977

[Erik Stein]

thanks for pointing this out.

I attached a symptomatic patch to ticket #13366.

best
-- erik


Am 17.04.2010 um 14:33 schrieb Ramiro Morales:

> On Sat, Apr 17, 2010 at 4:38 AM, Erik Stein <c...@classlibrary.net> wrote:
>> I'd would definetly consider this a bug in django, but I've no idea how to 
>> design a regression test for this, sorry. I'll try to understand what these 
>> app loading changes do.
> 
> I think this has already been reported in ticket 13366, Comment is a
> model that inherits from an abstract base class that has fields
> (BaseCommentAbstractModel).

-- 
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: Import problem starting with r12977

[Erik Stein]

I'm was digging around more, too, and finally i've set up a small test 
environment with django (r12955), just an project with a single app:

django-admin.py startproject mytest
cd mytest
django-admin.py startapp blog


INSTALLED_APPS = (
'django.contrib.auth',
'django.contrib.comments', # <-- Added comments app
'django.contrib.contenttypes',
'django.contrib.sessions',
'django.contrib.sites',
'django.contrib.messages',
'blog',
)

blog/models.py:

from django.db import models
from django.contrib.comments.models import Comment


c-y:mytest erik$ ./manage.py validate
Error: cannot import name Comment

I'd would definetly consider this a bug in django, but I've no idea how to 
design a regression test for this, sorry. I'll try to understand what these app 
loading changes do.

greetings
-- erik

Am 17.04.2010 um 02:09 schrieb Derek Hoy:

> On Sat, Apr 17, 2010 at 12:36 AM, Derek Hoy  wrote:
>> 
>> I'll dig around a bit more.
> 
> The problems seemed to come from the same models.py that was shared
> across the projects. I moved a couple of imports and it seems fine
> with trunk (r12996).
> 
> So it looks like it's the change in the error handling that is showing
> up problems in the code.
> 
> And that means we should be in django-users :)
> 
> Derek

-- 
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.

Import problem starting with r12977

[Erik Stein]

Hello --

I hope that's the correct place to ask, else point me to django-users.

Starting with changeset

http://code.djangoproject.com/changeset/12977 (Fixed #13328 -- Added a 
getstate/setstate pair to fields so that callable default values aren't 
pickled. Thanks to bkonkle for the report, and Vitaly Babiy for the patch.)

I get import errors which are very difficult to debug (at least for me). I'm 
hangling from file to file. It seems to boil down to

self.model = cls

in fields/__init__.py.

It may be related to some non-obvious circular import on my side, but what 
exactly am I supposed to do concerning r12977? File a new bug or just try to 
fix my code?

best
-- erik



Erik Stein
Programmierung, Grafik
   Oranienstr. 32   10999 Berlin, Germany
   fon +49 30 69201880   fax +49 30 692018809
   email e...@classlibrary.net





Erik Stein
Programmierung, Grafik
Oranienstr. 32   10999 Berlin, Germany
fon +49 30 69201880   fax +49 30 692018809
email e...@classlibrary.net



-- 
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.