Re: Announcment - django-databrowse

[Russell Keith-Magee]

On Fri, Jan 11, 2013 at 3:00 AM, Alireza Savand wrote:

> Yes, Correct.
> I agree with `django.contrib.auth` specially since 1.5 when it went
> pluggable.
> It's a mistake to say django should be clean as possible.
> Just imagine ORM, forms or some other core features get split, Django will
> no longer be Django.
> But look at some of the apps in `django.contrib.*`, Such as:
>
> * sitemaps
> * coments
> * syndication
> * webdesign
> * ...
>
> I'm not saying they are useless, No. They are just fine. But they can be
> handled outside
>  of Django mainstream.
>
>
… and that's exactly the intention behind use splitting out databrowse et
al from contrib. databrowse hasn't received attention for a long time (and
was probably added to core in haste in the first place). webdesign is an
app that contains 1 template tag. markup is a library that provides support
for 3 markup languages, ignoring lots of others, and adding a dependency on
downstream libraries (some of which haven't got a great track record on
fixing security problems).

So - given that we now live in a world where packaging "Just Works™",
splitting up parts of Django's core into side projects is now a viable
option.

Also - keep in mind that there is a middle ground -- we can split these
projects out of the "django" repository, but still continue to maintain
them as official Django projects. This is what we've done with localflavor.
This allows us to put localflavor code into the hands of developers with
domain expertise, while maintaining the official nature of localflavor
additions.

Don't fear -- we're not going to chop out and abandon big ticket features
of Django like auth or admin. The most we would do is move them into a
separate repository for management purposes.

Yours,
Russ Magee %-)

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To post to this group, send email to django-users@googlegroups.com.
To unsubscribe from this group, send email to 
django-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-users?hl=en.

Re: Announcment - django-databrowse

[Alireza Savand]

Yes, Correct.
I agree with `django.contrib.auth` specially since 1.5 when it went
pluggable.
It's a mistake to say django should be clean as possible.
Just imagine ORM, forms or some other core features get split, Django will
no longer be Django.
But look at some of the apps in `django.contrib.*`, Such as:

* sitemaps
* coments
* syndication
* webdesign
* ...

I'm not saying they are useless, No. They are just fine. But they can be
handled outside
 of Django mainstream.



On Thu, Jan 10, 2013 at 6:20 PM, Derek  wrote:

> I for one hope that django.contrib.auth is never "wiped off" and handed
> off to some random third party.  I think that the framework would be much
> poorer for its loss and I'm happy to trade off for a "slower and dirtier"
> Django to be able to keep its presence.
>
>
>
> On Wednesday, 9 January 2013 01:17:17 UTC+2, Alir3z4 wrote:
>>
>> Hi,
>>
>> Since Django 1.4 released, `django.contrib.databrowse` get deprecated.
>> And it's removed from 1.5.
>> Actually I hope django.contrib.* completely **get wiped off django, I
>> guess django development
>> will be faster and cleaner without those app.
>>
>> I've extracted and adopted it.
>> Now it's available as stand-alone package pypi.
>>
>> pypi:
>> http://pypi.python.org/pypi/**django-databrowse
>>
>> source/git repo:
>> https://github.com/Alir3z4/**django-databrowse
>>
>>
>> Regards,
>> Alireza Savand
>>
>  --
> You received this message because you are subscribed to the Google Groups
> "Django users" group.
> To view this discussion on the web visit
> https://groups.google.com/d/msg/django-users/-/FaIWDRTgCtgJ.
>
> To post to this group, send email to django-users@googlegroups.com.
> To unsubscribe from this group, send email to
> django-users+unsubscr...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/django-users?hl=en.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To post to this group, send email to django-users@googlegroups.com.
To unsubscribe from this group, send email to 
django-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-users?hl=en.

Re: Announcment - django-databrowse

[Derek]

I for one hope that django.contrib.auth is never "wiped off" and handed off 
to some random third party.  I think that the framework would be much 
poorer for its loss and I'm happy to trade off for a "slower and dirtier" 
Django to be able to keep its presence.


On Wednesday, 9 January 2013 01:17:17 UTC+2, Alir3z4 wrote:
>
> Hi,
>
> Since Django 1.4 released, `django.contrib.databrowse` get deprecated.
> And it's removed from 1.5.
> Actually I hope django.contrib.* completely get wiped off django, I guess 
> django development
> will be faster and cleaner without those app.
>
> I've extracted and adopted it.
> Now it's available as stand-alone package pypi.
>
> pypi:
> http://pypi.python.org/pypi/django-databrowse
>
> source/git repo:
> https://github.com/Alir3z4/django-databrowse
>
>
> Regards,
> Alireza Savand
>

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/django-users/-/FaIWDRTgCtgJ.
To post to this group, send email to django-users@googlegroups.com.
To unsubscribe from this group, send email to 
django-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-users?hl=en.

Announcment - django-databrowse

[Alir3z4]

Hi,

Since Django 1.4 released, `django.contrib.databrowse` get deprecated.
And it's removed from 1.5.
Actually I hope django.contrib.* completely get wiped off django, I guess 
django development
will be faster and cleaner without those app.

I've extracted and adopted it.
Now it's available as stand-alone package pypi.

pypi:
http://pypi.python.org/pypi/django-databrowse

source/git repo:
https://github.com/Alir3z4/django-databrowse


Regards,
Alireza Savand

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/django-users/-/zpKP-nBTULQJ.
To post to this group, send email to django-users@googlegroups.com.
To unsubscribe from this group, send email to 
django-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-users?hl=en.