Re: Changeset [5231] -- do_clean_*() is awkward naming

[Etienne Robillard]

I dont understand that changes. For me thats just odd, and
a royal pain to update lots of sites just for renaming clean_data to 
cleaned_data.

I really think thats odd and a better rationale would take in consideration
that already working and defined functions should try to keep at least some kind
of backward compatible hooks at least for being nice to users of clean_data!   

Why not incorporating the semantics or desired logic of cleaned_data into 
clean_data, so
that at least that part of the newforms api would stay as in the documentation ?
 
Etienne

On Tue, 15 May 2007 02:30:14 +1000
Malcolm Tredinnick <[EMAIL PROTECTED]> wrote:

> 
> On Mon, 2007-05-14 at 10:52 -0500, Adrian Holovaty wrote:
> > On 5/14/07, John Shaffer <[EMAIL PROTECTED]> wrote:
> > > For me, an AttributeError from clean_data is a much more friendly
> > > change than silently ignoring code like:
> > >
> > > def clean_email(self):
> > > """Prevent account hijacking by disallowing duplicate emails."""
> > 
> > John makes an excellent point. I'm +1 on changing clean_data to
> > cleaned_data and keeping the "clean_XXX" method hooks as-is.
> 
> Everything switched around again in [5237].
> 
> Malcolm
> 
> 
> > 

--~--~-~--~~~---~--~~
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 [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-developers?hl=en
-~--~~~~--~~--~--~---

Re: Bug with contenttypes when models are removed - what approach to take?

[Etienne Robillard]

On 12/24/2011 12:55 PM, Diederik van der Boor wrote:

Hi,

I've encountered a bug with the contenttypes framework when a model is
removed. You'll end up with a AttributeError in _add_to_cache():

'NoneType' object has no attribute '_meta'

That's because the ContentType still exists, byt ContentType.

I would like to solve it, yet I'm not sure about the recommended approach:
1. returning None for ContentType.objects.get_for_id() when the model does not
exist.
2. Raise an exception that the referenced model does not exist.

What is your idea on this?

This bug currently hits me because django-polymorphic (which I use) uses the
contenttype framework to upcast the models. As the models are removed, but the
contenttype still exists, making queries causes an AttributeError. When Django
returns a normal response, I'll see how to address this issue in django-
polymorphic too.

Best regards,

Diederik



Hi,

I'm not sure this is not entirely related to django-polymorphic, yet
a traceback would have been helpful in understanding your code. :)

cheers,
E

--
Etienne Robillard
Lead Developer and Consultant
Green Tea Hackers Club
Email:  animelo...@gmail.com
Website:http://gthcfoundation.org

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

SOPA bill question

[Etienne Robillard]

Hi,

I'm curious and at the same time a little worried by the upcoming "SOPA" 
bill, which would imposes in US new laws for blocking down websites and 
user-generated content on the basis of copyright violation.


What thus you Django developers all think of this proposed law and how 
could this may affect open source communities such as Django and Python

to develop novel apps specifically for creating user-generated content?

https://duckduckgo.com/?q=SOPA+end+of+internet

--
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: SOPA bill question

[Etienne Robillard]

On 12/26/2011 07:46 PM, Jeremy Dunck wrote:

On Mon, Dec 26, 2011 at 4:33 PM, Etienne Robillard  wrote:

What thus you Django developers all think of this proposed law and how could
this may affect open source communities such as Django and Python
to develop novel apps specifically for creating user-generated content?


This feels off-topic to me; the breadth of SOPA is far beyond UGC, far
beyond Django, and Django is useful for many kinds of sites that do
not involve UGC.

I, for one, am against it, but would prefer to discuss it in a proper forum.



Hm, I suppose you're right. This maybe slightly off-topic but still I 
would be interested to understand how this could affect open source 
development and in particular dynamic web site development which 
involves UGC..


Finally blacklisting web sites on the basis of copyright violation sure 
sounds like a big trojan horse to manipulate the internet DNS system IMHO.


http://www.guardian.co.uk/technology/2011/nov/16/sopa-condemned-internet-blacklist-bill

--
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: SOPA bill question

[Etienne Robillard]

On 12/26/2011 11:12 PM, Justin Holmes wrote:

Yep, there's no doubt that having these kinds of discussions on the
dev list (which already struggles at times to keep a good signal /
noise ratio) is not the way.

However, it was clear at djangocon (and is also clear in the various
django IRC channels) that:

1) Many django developers are politically conscious and active, and

2) Many django developers view their participation in the django
project *as a political act*.

Where, then, can we gather to discuss the social and political issues
facing our community, and the social and political implications of the
various decisions that we make?

To my knowledge, there isn't currently a "proper forum" for this
discussion.  I'd like to create and cultivate one if I can get the
proper guidance from the core team.




I agree. The whole point about freedom of expression is that its not
relevant to a "proper forum" but whether we can freely express ourselves
independently from censorship on the internet. :)

Cheers,

Etienne


--
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: SOPA bill question

[Etienne Robillard]

James,

This SOPA bill thing probably concerns more open source communities than 
you could think of, including Django development, and discussing about 
it should be a good thing, not a bad one, as far I understand the 
problems it creates.


Further I disagree this is a bad list for discussing the implications 
SOPA, and encourages everyone to sharpen their minds on this issue, so 
please don't be "sorry" to talk about it.



Best regards,

Etienne



On Dec 27, 2011 11:16 PM, "James Richards" mailto:hei...@mac.com>> wrote:

I do agree that the fundamental point of Django is free distribution
of content.  Are developers now obligated to design software that is
not under their control?  How does that affect contracted
development obligations?  This is probably not the ideal list but it
is surely a worthy topic for one.

Please pardon the intrusion,

James

 > With the utmost respect, I must rebuke Paul's claim that this
discussion is misplaced on the dev list.  We all have a stake in
this legislation.  All free software projects have a stake in this
legislation.  I urge those unfamiliar with H.R. 3261 to google for
the Cole's Notes.  This legislation effects the removal of judicial
oversight from the process of "incarceration" of an electronic
entity.  This isn't about politics at all.  User contributed content
is about to become a liability...
 >
 > Ryan
 >
 > - Original Message -
 > From: "Justin Holmes" mailto:jus...@justinholmes.com>>
 > To: django-developers@googlegroups.com

 > Sent: Monday, December 26, 2011 10:12:10 PM GMT -06:00 US/Canada
Central
 > Subject: Re: SOPA bill question
 >
 > Yep, there's no doubt that having these kinds of discussions on the
 > dev list (which already struggles at times to keep a good signal /
 > noise ratio) is not the way.
 >
 > However, it was clear at djangocon (and is also clear in the various
 > django IRC channels) that:
 >
 > 1) Many django developers are politically conscious and active, and
 >
 > 2) Many django developers view their participation in the django
 > project *as a political act*.
 >
 > Where, then, can we gather to discuss the social and political issues
 > facing our community, and the social and political implications
of the
 > various decisions that we make?
 >
 > To my knowledge, there isn't currently a "proper forum" for this
 > discussion.  I'd like to create and cultivate one if I can get the
 > proper guidance from the core team.
 >
 >
 >
 > On Mon, Dec 26, 2011 at 10:18 PM, Paul McMillan mailto:p...@mcmillan.ws>> wrote:
 >> While this bill certainly merits discussion, and may indeed be
related
 >> to sites created with and using Django, this forum is not the place
 >> for it. Please do not continue this thread here.
 >>
 >> -Paul
 >>
 >> --
 >> 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.
 >>
 >
 >
 >
 > --
 > Justin Holmes
 >
 > Head Instructor, SlashRoot Collective
 > SlashRoot: Coffee House and Tech Dojo
 > 60 Main Street
 > New Paltz, NY 12561
 > 845.633.8330 
 >
 > --
 > 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.
 >

--
You received this message because you are subscribed to the Google
Groups "Django developers" group.
To post to thi

Re: RFC: Query Methods

[Etienne Robillard]

On 01/12/2012 07:24 AM, Zachary Voase wrote:

I strongly feel that switching around managers like that would be an
example of overengineering.

The user story which drove this RFC was based on an issue which has
been encountered by lots of developers, but typically solved in a
single way. Django's conservative style of development is very
accommodating to this 'lowest common denominator' approach to adding
features. However, by adding this manager-switching feature, we're
second-guessing our users' intentions, and introducing unjustified
complexity to the API.

Agreed +1 it seems as well the whole model inheritance has the potential 
to complexify code, not making it any more simpler than

it should by manually making SQL queries with the .extra method.

Cheers,
Etienne

--
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: End-user defined fields, how would you approach it?

[Etienne Robillard]

Hi,


2. The second approach would be to have a database table for each of
the users (probably no more than a 1000). I've read django has
something in the lines of inspectdb, which actually checks which
fields are there and produces the model for you. This could be useful
but I think maybe I should store the fields this particular user has
created and somehow dinamically tell django, hey, we also have this
fields in this model. Is this possible? I know it's generally bad to
have different tables for each user, but considering this scenario,
how would you guys rate this method, would it be ok to have one table
for each user?


Its not really the functional aspect that burdens me but rather to 
understand why on Earth a web site would need to store individual data 
on a per-user basis, unless for fascists tracking/monitoring reasons of 
your visitors.. As for this reason alone I'd decline this for political 
reasons. (-1)



The model that requires custom fields is for example Person. They
might want a custom field to store address, blood type, or any other
thing.


Whatever. ;-)


MANY THANKS in advance! Have a nice sunday!
Bernardo Pires



cheers,
Etienne

--
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: End-user defined fields, how would you approach it?

[Etienne Robillard]

For other options checkout this guide:http://stackoverflow.com/a/7934577/497056

Best regards,
Ivan Kharlamov


Probably a really mediocre reference assuming its on stackoverflow.com 
already... :-)


Cheers
E


--
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: End-user defined fields, how would you approach it?

[Etienne Robillard]

On 01/29/2012 12:31 PM, Ivan Kharlamov wrote:

On 01/29/2012 09:16 PM, Etienne Robillard wrote:




For other options checkout this
guide:http://stackoverflow.com/a/7934577/497056

Best regards,
Ivan Kharlamov


Probably a really mediocre reference assuming its on stackoverflow.com
already... :-)


Well, I'm not going to pretend that I'm a superstar programmer. I wrote
this reference because some time ago I've had a need to implement
dynamic Django models and didn't find any up to date cheat sheet or side
by side comparison of different dynamic model implementations.

Maybe you know better. Why don't you share your knowledge?


Please reread my initial reply to this thread for explanation as i'm 
feeling bored of repeating sometimes... :-)


cheers,

E

--
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: End-user defined fields, how would you approach it?

[Etienne Robillard]

On 01/29/2012 01:40 PM, Aymeric Augustin wrote:

Hello Etienne,

The three messages you posted in this thread aren't appropriate on this mailing 
list, both in terms of contents and tone.

Please stay on topic, respect other members of the community, and if you don't 
have anything constructive to say, refrain from posting — even with a smiley.

Thanks,



They were just fine. Please stop trolling and respect the little freedom 
of expression we still have.


E

--
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: End-user defined fields, how would you approach it?

[Etienne Robillard]

On 01/29/2012 02:46 PM, John Hensley wrote:

On Jan 29, 2012, at 1:52 PM, Etienne Robillard wrote:


On 01/29/2012 01:40 PM, Aymeric Augustin wrote:

Hello Etienne,

The three messages you posted in this thread aren't appropriate on this mailing 
list, both in terms of contents and tone.

Please stay on topic, respect other members of the community, and if you don't 
have anything constructive to say, refrain from posting — even with a smiley.

Thanks,



They were just fine. Please stop trolling and respect the little freedom of 
expression we still have.


Etienne,

I sympathize with you regarding the ever-decreasing civil liberties, I really do, but the 
django-developers list is not the place for this. If a core developer tells you that your 
messages aren't appropriate, the only correct response is, "Sorry, won't happen 
again." You've been asked repeatedly now to take the politics somewhere else. Please 
have the maturity and civility to do so.

John


You're missing the point totally.

The point is that as most as everyone on this list, we have the right to 
discuss things which feels on topic with this list without being 
discriminated for no reasons.


Now that has nothing to do with mediocre questions. Don't expect 
anything from me but harsh responses when you're expecting only mediocre 
answers, as this is really not more on-topic than

was SOPA.

E



--
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: End-user defined fields, how would you approach it?

[Etienne Robillard]

On 01/29/2012 12:55 PM, Ivan Kharlamov wrote:

On 01/29/2012 09:39 PM, Etienne Robillard wrote:

On 01/29/2012 12:31 PM, Ivan Kharlamov wrote:

On 01/29/2012 09:16 PM, Etienne Robillard wrote:




For other options checkout this
guide:http://stackoverflow.com/a/7934577/497056

Best regards,
Ivan Kharlamov


Probably a really mediocre reference assuming its on stackoverflow.com
already... :-)


Well, I'm not going to pretend that I'm a superstar programmer. I wrote
this reference because some time ago I've had a need to implement
dynamic Django models and didn't find any up to date cheat sheet or side
by side comparison of different dynamic model implementations.

Maybe you know better. Why don't you share your knowledge?


Please reread my initial reply to this thread for explanation as i'm
feeling bored of repeating sometimes... :-)

Its not really the functional aspect that burdens me but rather to understand 
why on Earth a web site would need to store individual data on a per-user 
basis, unless for fascists tracking/monitoring reasons of your visitors.. As 
for this reason alone I'd decline this for political reasons. (-1)


Oh, I've got your point! Yes, it is true that dynamic models are only
for communist hippie weirdos such as medical workers etc. ^-^


LOL- Not all medical workers should be communist hippie weirdos... :-)

cheers,
E

--
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: End-user defined fields, how would you approach it?

[Etienne Robillard]

On 01/29/2012 12:55 PM, Ivan Kharlamov wrote:

On 01/29/2012 09:39 PM, Etienne Robillard wrote:

On 01/29/2012 12:31 PM, Ivan Kharlamov wrote:

On 01/29/2012 09:16 PM, Etienne Robillard wrote:




For other options checkout this
guide:http://stackoverflow.com/a/7934577/497056

Best regards,
Ivan Kharlamov


Probably a really mediocre reference assuming its on stackoverflow.com
already... :-)


Well, I'm not going to pretend that I'm a superstar programmer. I wrote
this reference because some time ago I've had a need to implement
dynamic Django models and didn't find any up to date cheat sheet or side
by side comparison of different dynamic model implementations.

Maybe you know better. Why don't you share your knowledge?


Please reread my initial reply to this thread for explanation as i'm
feeling bored of repeating sometimes... :-)

Its not really the functional aspect that burdens me but rather to understand 
why on Earth a web site would need to store individual data on a per-user 
basis, unless for fascists tracking/monitoring reasons of your visitors.. As 
for this reason alone I'd decline this for political reasons. (-1)


Oh, I've got your point! Yes, it is true that dynamic models are only
for communist hippie weirdos such as medical workers etc. ^-^


cheers,

E





sorry for the interruptions, what are we saying now? :-)

Please continue discussing this, if you feel its appropriate to let have 
for each users a SQL table..


cheers,
E


--
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: End-user defined fields, how would you approach it?

[Etienne Robillard]

On 01/29/2012 04:27 PM, Łukasz Rekucki wrote:

First of all, this whole topic doesn't belong on django-developers in
the first place as it's strictly a user question (I didn't see any
proposal to change anything in the core, etc.). In the future, please
post to django-users with question about using Django.

On 29 January 2012 21:44, Etienne Robillard  wrote:

On 01/29/2012 02:46 PM, John Hensley wrote:


On Jan 29, 2012, at 1:52 PM, Etienne Robillard wrote:


On 01/29/2012 01:40 PM, Aymeric Augustin wrote:


Hello Etienne,

The three messages you posted in this thread aren't appropriate on this
mailing list, both in terms of contents and tone.

Please stay on topic, respect other members of the community, and if you
don't have anything constructive to say, refrain from posting — even with a
smiley.

Thanks,



They were just fine. Please stop trolling and respect the little freedom
of expression we still have.



Etienne,

I sympathize with you regarding the ever-decreasing civil liberties, I
really do, but the django-developers list is not the place for this. If a
core developer tells you that your messages aren't appropriate, the only
correct response is, "Sorry, won't happen again." You've been asked
repeatedly now to take the politics somewhere else. Please have the maturity
and civility to do so.

John


You're missing the point totally.

The point is that as most as everyone on this list, we have the right to
discuss things which feels on topic with this list without being
discriminated for no reasons.



You're not discriminated - everyone is treated the same way here and
judged only by their actions. By disobeying the rules of this list,
you're disrespecting it's members. If you disagree with the rules of
this community, you don't have to be part of it. Insulting it's core
members surely doesn't help you convince us, that it's a good choice
to accept your definition of "things which feels on topic with this
list".



OK good. I see your points but please observe I'm still searching where 
I'm "disobeying" the rules ?


Anyways, thanks trying not to disturb the thread. But i disagree it 
should be on django-users as now that I'm thinking more of this 
possiblity to have one table per user.



--
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: End-user defined fields, how would you approach it?

[Etienne Robillard]

On 01/29/2012 07:51 PM, Russell Keith-Magee wrote:


On 30/01/2012, at 6:05 AM, Etienne Robillard wrote:


On 01/29/2012 04:27 PM, Łukasz Rekucki wrote:


You're not discriminated - everyone is treated the same way here and
judged only by their actions. By disobeying the rules of this list,
you're disrespecting it's members. If you disagree with the rules of
this community, you don't have to be part of it. Insulting it's core
members surely doesn't help you convince us, that it's a good choice
to accept your definition of "things which feels on topic with this
list".



OK good. I see your points but please observe I'm still searching where I'm 
"disobeying" the rules ?



Let me help.

Firstly:

"...unless for fascists tracking/monitoring reasons of your visitors.."

You just called the OP a fascist, based purely on an architectural decision.

Secondly:

"Probably a really mediocre reference assuming its on stackoverflow.com already... 
:-)"

You just called the entire population of Stack Overflow mediocre, and implied 
that Ivan specifically was mediocre because he recommended it.

Thirdly:

"Don't expect anything from me but harsh responses when you're expecting only 
mediocre answers"

We don't expect harsh responses *at all*. If you can't say something 
constructive, say nothing at all.

None of these three comments were necessary, or were consistent with the tone 
that we expect of participants in Django-developers. If you don't like what 
someone is doing with technology, refrain from commenting. If you don't like 
Stack Overflow, don't recommend it; if someone recommends something from Stack 
Overflow that you disagree with, point out the specific flaws in the specific 
suggestion that has been made. If you think someone is asking bad questions, 
ignore them; or if you're feeling particularly helpful, assist them by 
providing constructive guidance on asking better questions.

Regarding your reference to discussions about SOPA -- you'll notice that when 
SOPA came up recently, it was very rapidly pointed out that such discussions 
were off-topic for Django-developers, unless there was a specific call to 
action for the Django codebase.

This isn't censorship, or the jackboot of the thought police. It's the Django 
core team ensuring that we maintain a civil community.

Yours,
Russ Magee %-)



i still think stackoverflow.com is retarded. Ie it attracts stupid 
peoples with stupid questions towards stupid solutions. :-)


As for your opinions, I respect them as always and that should be all 
the same for me, ie without stupid moderation/trolling.


Otherwise this is only fascist moderation and I'm making only very 
polite comments when talking about SOPA. So please be cool and observe 
that the net is still a free place to discuss without stupid trolls to

dictate content.

Cheers,
E

--
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: End-user defined fields, how would you approach it?

[Etienne Robillard]

On 01/29/2012 09:28 PM, Russell Keith-Magee wrote:


On 30/01/2012, at 9:51 AM, Etienne Robillard wrote:


i still think stackoverflow.com is retarded. Ie it attracts stupid peoples with 
stupid questions towards stupid solutions. :-)

As for your opinions, I respect them as always and that should be all the same 
for me, ie without stupid moderation/trolling.

Otherwise this is only fascist moderation and I'm making only very polite 
comments when talking about SOPA. So please be cool and observe that the net is 
still a free place to discuss without stupid trolls to
dictate content.



http://www.youtube.com/watch?v=G2y8Sx4B2Sk

Let me be perfectly clear.

There is a world of difference between "I don't think that XYZ, as suggested by StackOverflow, is a very 
good idea", and "StackOverflow is for stupid people with stupid questions". Unprovoked 
accusations of fascism, or suggesting that an individual is mediocre is not a "very polite comment".

You are free to hold any opinion you want. You are free to provide any 
constructive advice that you care to share.

You're not free to use the Django community as a platform to call people 
stupid, mediocre, or fascists.

I am not saying you can't express your opinions. I'm telling you that when you 
express your opinions in an official Django forum, you'll keep a civil tongue 
in your mouth. That isn't censorship -- it's called being polite.

If you can't maintain a civil tone, then I would kindly ask you to refrain from 
posting. If you continue to maintain an uncivil tone, then for the good of the 
Django community, I'll ban you from posting.

Yours,
Russ Magee %-)



So why are you now insisting on putting it on the personal side unless 
for this particular reasons of banning me ? You're perfectely fitting 
into a idiot for me and no matter what I could be attempting to 
say/reply it would still be an idiot response.


So please go ahead and ban me from this group and enjoy 
mediocre/prefabricated content as i'm getting tired of discrimination

and retarded peoples like you in particular.

Cheers,
E

--
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: End-user defined fields, how would you approach it?

[Etienne Robillard]

On 01/29/2012 02:46 PM, John Hensley wrote:

On Jan 29, 2012, at 1:52 PM, Etienne Robillard wrote:


On 01/29/2012 01:40 PM, Aymeric Augustin wrote:

Hello Etienne,

The three messages you posted in this thread aren't appropriate on this mailing 
list, both in terms of contents and tone.

Please stay on topic, respect other members of the community, and if you don't 
have anything constructive to say, refrain from posting — even with a smiley.

Thanks,



They were just fine. Please stop trolling and respect the little freedom of 
expression we still have.


Etienne,

I sympathize with you regarding the ever-decreasing civil liberties, I really do, but the 
django-developers list is not the place for this. If a core developer tells you that your 
messages aren't appropriate, the only correct response is, "Sorry, won't happen 
again." You've been asked repeatedly now to take the politics somewhere else. Please 
have the maturity and civility to do so.

John



John, even with your reply your putting politics on the topic. It just 
deplorable we let people destroy threads on the basis on content 
filtering just because they have the 'moderation' flag set and they can 
impose whatever (mediocre) rules they wish.. :-)


--
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: End-user defined fields, how would you approach it?

[Etienne Robillard]

On 01/30/2012 08:20 AM, Bernardo Pires wrote:

Someone has PMS.


you mean like Post-menstrual syndrome ? Are you kidding.. 8-)

i'm just concerned by whatever I could touch would be immediately
backfired as OT..

E

--
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: Getting a traceback out of connection.queries

[Etienne Robillard]

On 02/01/2012 10:30 AM, Daniel Moisset wrote:

On Tue, Jan 31, 2012 at 8:34 PM, josharian  wrote:

Hi all,

We're using connection.queries to log all sql executed during
development. I find myself wishing that in addition to 'sql' and
'time', there was a 'traceback' entry, so that troublesome/mysterious
queries could quickly be tracked back to their origins.

Adding it is a pretty small patch -- an `import traceback` and a
couple of `'traceback': traceback.extract_stack(),`s. My question is:
Is there a better way to get at this data currently? Is there any
interest in such a patch?

Thanks,
Josh


Using django-debug-toolbar provides that functionality, without having
to modify the django core

D.


i use __exception__ value inside pdb... OK now thats way OT... :-)

Cheers,
E

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

Extending Django models with Schevo

[Etienne Robillard]

Hi,

I'm planning to extend django-hotsauce to support a generic "model" API. 
I would like to reuse the Django models API to support Schevo databases. 
Ideally, I would like to introspect into my reusable Django apps to 
discover configured features. Importing and exporting data from/to 
Schevo databases using JSON fixtures would also be a great addition.


Any ideas if Django 1.10 can be used for this?

Kind regards,

Etienne

--
Etienne Robillard
tkad...@yandex.com
http://www.isotopesoftware.ca/

--
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/de1730ab-2c5e-310e-d7a8-38d0ca5f4e43%40yandex.com.
For more options, visit https://groups.google.com/d/optout.

Re: Extending Django models with Schevo

[Etienne Robillard]

Hi Tim,

I'm looking for technical comments about developing Django models 
classes using the Schevo DBMS.


http://www.isotopesoftware.ca/documentation/libschevo/

I would like to use this like so:

$ manage.py schevo test myapp

$ manage.py schevo db-update myapp

$ manage.py schevo shell

The "schevo" string is a command to access the Schevo API from the 
Django management script.


The Django model classes I need would provide a bridge to the Schevo 
databases.


Kind regards,

E


Le 2017-02-17 à 19:20, Tim Graham a écrit :
Hi Etienne, I'm not sure exactly what type of response you're looking 
for or if this is on-topic for the Django developers mailing list, 
which pertains to the development of Django itself. django-users seems 
more appropriate unless you're proposing some feature for Django.


On Friday, February 17, 2017 at 3:57:42 PM UTC-5, Etienne Robillard 
wrote:


Hi,

I'm planning to extend django-hotsauce to support a generic
"model" API.
I would like to reuse the Django models API to support Schevo
databases.
Ideally, I would like to introspect into my reusable Django apps to
discover configured features. Importing and exporting data from/to
Schevo databases using JSON fixtures would also be a great addition.

Any ideas if Django 1.10 can be used for this?

Kind regards,

Etienne

-- 
Etienne Robillard

tka...@yandex.com 
http://www.isotopesoftware.ca/

--
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 
<mailto:django-developers+unsubscr...@googlegroups.com>.
To post to this group, send email to 
django-developers@googlegroups.com 
<mailto: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/f907064e-f4c4-4c73-aa31-0204b7ee1c12%40googlegroups.com 
<https://groups.google.com/d/msgid/django-developers/f907064e-f4c4-4c73-aa31-0204b7ee1c12%40googlegroups.com?utm_medium=email&utm_source=footer>.

For more options, visit https://groups.google.com/d/optout.


--
Etienne Robillard
tkad...@yandex.com
http://www.isotopesoftware.ca/

--
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/3b1a19b2-5d06-8e45-e479-60ed5fb3bd72%40yandex.com.
For more options, visit https://groups.google.com/d/optout.

Re: Will asgi become a PEP like wsgi is ?

[Etienne Robillard]

WSGI is for building web applications in Python.

ASGI is for building platform-oriented web applications in Django.

I'm -1 on this.

I prefer the ease and flexibility of WSGI draft over asynchronous 
platform choices.


E


Le 2017-03-13 à 07:08, James Pic a écrit :
I do not see myself using Django without Channels anymore, it's become 
a basic Django feature for me and I just love it. Despite my perhaps 
lack of knowledge about the protocol internals, such features seem 
like it would certainly benefit the Python community and anyway I'd 
say it's worth a try just to see what the python-ideas list has to say.

--
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 
<mailto:django-developers+unsubscr...@googlegroups.com>.
To post to this group, send email to 
django-developers@googlegroups.com 
<mailto: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/CAC6Op1-p6O4pzUHcgZEE%2Bap8ZAdkQqeaC_bSi0%3DvF8GH%2BZBc4A%40mail.gmail.com 
<https://groups.google.com/d/msgid/django-developers/CAC6Op1-p6O4pzUHcgZEE%2Bap8ZAdkQqeaC_bSi0%3DvF8GH%2BZBc4A%40mail.gmail.com?utm_medium=email&utm_source=footer>.

For more options, visit https://groups.google.com/d/optout.


--
Etienne Robillard
tkad...@yandex.com
http://www.isotopesoftware.ca/

--
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/827eb016-b963-b036-d054-3ed340f848c3%40yandex.com.
For more options, visit https://groups.google.com/d/optout.

Re: Will asgi become a PEP like wsgi is ?

[Etienne Robillard]

As far I know Django channels is a Django framework enforcing a specific 
messaging protocol in mind.


I don't see how implementing ASGI could help to build more scalable apps 
without breaking compatibility with WSGI.


E


Le 2017-03-13 à 07:50, James Pic a écrit :

On Mon, Mar 13, 2017 at 12:26 PM, Etienne Robillard  wrote:

ASGI is for building platform-oriented web applications in Django.

Could you elaborate on this ? The only mention of Django I found in
the spec linked by the OT is "Django Channels ships with a no-op
consumer attached by default; we recommend other implementations do
the same", so it doesn't look really coupled with Django overall:
http://channels.readthedocs.io/en/stable/asgi.html



--
Etienne Robillard
tkad...@yandex.com
http://www.isotopesoftware.ca/

--
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/8362a1d7-a0fa-b48a-4d48-15bdbb651c9f%40yandex.com.
For more options, visit https://groups.google.com/d/optout.

python.py deserialization and handling foreign key fields ?

[Etienne Robillard]

Hi all,

How should exceptions caught by FieldDoesNotExist be handled 
when trying to deserialize a object mapping to native python data types? 

For example, I have a csv row which I would like to deserialize into a model 
instance, but it breaks when trying to convert any foreign key field, giving
the following error message:

FieldDoesNotExist: Foo has no field named 'foo_id'

Any pointers how to work-around this issue ?

Thanks in advance,

Etienne

--~--~-~--~~~---~--~~
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 [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-developers?hl=en
-~--~~~~--~~--~--~---

Re: python.py deserialization and handling foreign key fields ?

[Etienne Robillard]

Hi Russell, 

Thanks for responding to this thread. You were right
for the data not matching the model. The assumption that 
some_model_instance.__dict__.keys() would return the fields names
is simply wrong. :)

Yes im trying to get a csv deserializer using the python.py and
csv.py modules as a base. It is currently working to some extent,
but I havent tested with anything else than postgresql_psycopg2. 

The issue is that it returns some ProgrammingErrors like:

Traceback (most recent call last):
  File "test_deserialize.py", line 145, in test_get_initial_data_as_dict
obj.save()
  File "/home/erob/django/django/core/serializers/base.py", line 166, in save
models.Model.save(self.object, raw=True)
  File "/home/erob/django/django/db/models/base.py", line 250, in save
','.join(placeholders)), db_values)
  File "/usr/local/erob/django/django/db/backends/util.py", line 19, in execute
return self.cursor.execute(sql, params)
ProgrammingError: invalid input syntax for integer: "0.1"


I dont know if this thread should be in django-users, but my apologies
if this isnt the appropriate list for posting :)

Thanks,
Etienne


On Fri, 13 Jul 2007 11:11:13 +0800
"Russell Keith-Magee" <[EMAIL PROTECTED]> wrote:

> 
> On 7/13/07, Etienne Robillard <[EMAIL PROTECTED]> wrote:
> >
> > How should exceptions caught by FieldDoesNotExist be handled
> > when trying to deserialize a object mapping to native python data types?
> ...
> > Any pointers how to work-around this issue ?
> 
> I'm unclear what the issue is.
> 
> Are you building your own CSV deserializer, or using one of Django's
> serializers?
> 
> Why are you getting FieldDoesNotExist errors at all? If you are
> getting these, it suggests to me that your data doesn't match your
> model.
> 
> Yours,
> Russ Magee %-)
> 
> > 

--~--~-~--~~~---~--~~
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 [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-developers?hl=en
-~--~~~~--~~--~--~---

how to desreialize foreign keys in postgresql to python ?

[Etienne Robillard]

Hi, 

Im trying to deserialize an csv row into a django object instance 
but it fails to process foreign keys correctly. As far as I understand this 
issue,
there's no such "field.attname" in the table which is necessary for making
the FK relationship: 

Jul 16 09:44:44 fluke postgres[51608]: [2-1] ERROR:  insert or update on table 
"sf_rates" violates foreign key constraint 
"fk_calling_plan_id_refs_calling_plan_id_6ccd374b"
Jul 16 09:44:44 fluke postgres[51608]: [2-2] DETAIL:  Key 
(fk_calling_plan_id)=(1) is not present in table "sp_calling_plans".
Jul 16 09:44:44 fluke postgres[51608]: [2-3] STATEMENT:  END

I think the code which should make the data[field.attname] key/attribute is in 
serializers/python.py: 


# Handle FK fields
elif field.rel and isinstance(field.rel, models.ManyToOneRel):
 if field_value:
data[field.attname] = field.rel.to._meta.get_field(field.rel.field_name)
 else:
data[field.attname] = None


As a work-around, I've found that setting null=True should allow the save() 
method
to write the record in the db, however I'm uncertain how to cope with this 
issue, 
especially for the postgresql case...

Any ideas/suggestions how to get foreign keys fields do the good thing for 
postgresql ?

Etienne

--~--~-~--~~~---~--~~
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 [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-developers?hl=en
-~--~~~~--~~--~--~---

Re: how to deserialize foreign keys in postgresql to python ?

[Etienne Robillard]

Russell,

Thanks for your help. 

Next time, could you please just have the decency to reply
to the sender himself, instead of writing things like that
to the list ? 

I think that would have more punch (think netiquette) than 
making unconstructive remarks which just doesnt belong
to this list...  
 
Regards,
Etienne  


On Tue, 17 Jul 2007 09:28:06 +0800
"Russell Keith-Magee" <[EMAIL PROTECTED]> wrote:

> 
> On 7/17/07, Russell Keith-Magee <[EMAIL PROTECTED]> wrote:
> > On 7/16/07, Etienne Robillard <[EMAIL PROTECTED]> wrote:
> > >
> > > Jul 16 09:44:44 fluke postgres[51608]: [2-1] ERROR:  insert or update on 
> > > table "sf_rates" violates foreign key constraint 
> > > "fk_calling_plan_id_refs_calling_plan_id_6ccd374b"
> >
> > > Any ideas/suggestions how to get foreign keys fields do the good thing 
> > > for postgresql ?
> 
> And again, this should be on django-users, not django-developers.
> 
> Yours,
> Russ Magee %-)
> 
> > 


-- 
Etienne Robillard | [EMAIL PROTECTED] | 514.962.7703
Owner, Green Tea Hackers Club
510 Mirelle, Laval
P.Q. Canada
H7A-2H5

--~--~-~--~~~---~--~~
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 [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-developers?hl=en
-~--~~~~--~~--~--~---

Re: Accessing request.FILES in chunks

[Etienne Robillard]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1



Hi there,

Not sure what you're trying to achieve with FileWrapper,
however here's how I'd do it with Django prior to revision 5818:

...
if request.method == 'POST':
   # Fetch some new data..
   new_data = request.POST.copy()
   new_data.update(request.FILES) # as explained in the docs..
   # Then, if the form is clean..
   if form.is_valid():
  # Decode the field names if they are utf-8 coated...
  utf8_fname = lambda u: smart_unicode(u, strings_only=False)
  filedata =  form.cleaned_data['filedata'].get(utf8_fname('content'))
  filename = form.cleaned_data['filedata'].get(ut8_fname('filename'))
  ...

HTH !

Etienne


On Tue, 14 Aug 2007 15:15:15 -
"[EMAIL PROTECTED]" <[EMAIL PROTECTED]> wrote:

> 
> Hi there!
> 
> I'm using Amazon S3 for file storage, so I have to access the FILES-
> object directly in my view. So #2070 won't have any effect, as far as
> I can see.
> 
> I've been thinking about the FileWrapper-object.
> If I access it like this: the_file =
> FileWrapper(file(StringIO(request.FILES['file']['content'])))
> would that load the whole thing into memory? Is there a way around
> this?
> 
> If there isn't, what are my options?
> 
> Thanks!
> 
> 
> > 
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.5 (FreeBSD)

iEYEARECAAYFAkbBykYACgkQdXKAffkXj4NB0gCgyNwctNkuLoq1WVBOIU6edxHs
vJYAn0DuGYJiXLQub5OUoDaMJ9N2hUj+
=OmJV
-END PGP SIGNATURE-

--~--~-~--~~~---~--~~
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 [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-developers?hl=en
-~--~~~~--~~--~--~---

Re: A question about manage.py validation

[Etienne Robillard]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1


Not sure what to expect unless you give some more data, input, 
or whatever which should make senses regarding your issue with FileField.

However, in my case i've managed to make FileField working
reasonably well using the newforms-admin branch. I suggest you
take a look at http://code.djangoproject.com/ticket/3297 if you
not already done.  

> Is there a particular reason this validation is being performed there
> instead of in the __init__ of each Field subclass? I haven't looked
> over the entirety of it, but it seems like that's going to be
> something of a barrier to custom subclasses, if those subclasses
> redefine any of those assumptions.

Again, we should probably "see" better your problem with some raw examples. :) 
Why should you need any management-specific methods for doing validation on
a file field ?

from django.newforms import fields 
class GenericFile(fields.FileField):
 def clean(self, data):
   return super(fields.FieldField, self).clean(data)

Regards,
Etienne

-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.5 (FreeBSD)

iEYEARECAAYFAkbKF1UACgkQdXKAffkXj4MqCQCglayArm/WtFwtdlMQUx/coDkC
fcYAnjkbatcZmthYGqSlOJj5sb4/z+ci
=rbN6
-END PGP SIGNATURE-

--~--~-~--~~~---~--~~
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 [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-developers?hl=en
-~--~~~~--~~--~--~---

Re: GSoC 2007: Reusable Django applications

[Etienne Robillard]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1



Hi Jannis,

Thanks for your time writing this post. :)

I like this idea of having reusable apps for Django 
all in the same place. Here's some suggestions.

> My initial GSoC application [1] was divided in:
> 
> 1) Create code infrastructure to simplify the process of building
> reusable Django applications, e.g. with egg files.
> 2) Build a public repository website for reusable Django applications.

Egg files are great. We could easy_install them, assuming the user
or developer is already using setuptools. 
 
> Even if these two topics are connected in a way, I stumbled over the
> rather different approaches to package management on a programming
> language, operating system and community level. I evaluated the
> package formats I knew to learn more about common package management
> idioms (apt, rpm, gems, distutils, setuptools) and realized that
> reinventing the wheel should be avoided - especially for a specific
> product like Django; reusable Django apps should happen with something
> stable and widely known, preferable without having to tie users to a
> "simple", wrapped version of a sophisticated system.

Agreed. In order to distribute reusable django apps, there should be
at least a common package namespace where all theses packages would get  
installed. I've thought the namespace "apps" would be a good 
starting point for this. 

> So, giving the user the option to have an easy start with package
> management was my first actual goal. I looked at the standard
> distutils and the defacto standard setuptools and found the features I
> needed: package management, dependency tracking, uploading and an easy-
> to-distribute format - eggs. Hacking the setuptools code and cloning
> the cheeseshop (PyPI) wasn't an option of course, so instead I
> introduced a "release" metaphor (thanks for the idea Neil Blakey-
> Milner) which holds the basic metadata for a reusable Django
> application. It's basically a simple Python file which lives in the
> application directory, gets loaded by setup.py and can be hand-edited
> or even abandoned if not needed.

Again, I really like the idea to use setuptools and eggs for distribution
of django apps/packages. However, Im less sure about adding anything
special inside a app for specifying metadata. Why not just use a regular
setup.py script for distributing a standalone app ?

> So now I'm on building the rest of the repository website, using
> several of the django-* Google Code projects. If you have any ideas
> for it, feel free to contact me. What about djangoapps.org?

+1 for djangoapps.org and for using a common package namespace
for reusable django apps. [apps]

Also, the freebsd ports collection is a great example of a well-managed
collection of reusable apps. We should use this more for inspiration.. :)

Finally, please check out notmm. Its a Django toolkit containing various
packages, and a set of django apps (distributed as a standalone component, but 
included
in the standard distribution). [1]

1. svn co http://tools.assembla.com/svn/notmm/trunk/ notmm
   
Cheers,

- - Etienne
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.5 (FreeBSD)

iEYEARECAAYFAkbS2/wACgkQdXKAffkXj4OeTgCfSoiattnF4JoHChUvLqYoP4c7
QrgAoLDZcClKCDj83MEXz+Ngo0gL/PhS
=kk87
-END PGP SIGNATURE-

--~--~-~--~~~---~--~~
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 [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-developers?hl=en
-~--~~~~--~~--~--~---

Re: Django 1.0 features -- the definitive list

[Etienne Robillard]

On Nov 30, 2007 2:27 AM, Max Battcher <[EMAIL PROTECTED]> wrote:

>
> On Nov 30, 2007 2:18 AM, jj <[EMAIL PROTECTED]> wrote:
> > move 0.96 to 1.0 status. This might sound somewhat artificial, but
> > would clearly indicate that 0.96 is a version one can already trust.
> > Isn't the Web site already advocating 0.96 that way?
>
> That might be a good idea...  backport any remaining useful fixes to
> 0.96, maybe go ahead and do the newforms -> forms rename, and not much
> more really needs to be done and call that 1.0 and everything else
> becomes 2.0...


I think it would be great if Django-1.0 (and subsequent releases) be
backward-compatible with Django-0.96...

Regards and happy sprinting!
- Etienne

--~--~-~--~~~---~--~~
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 [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-developers?hl=en
-~--~~~~--~~--~--~---