Re: Replacing the contrib.sites Site model with a setting?
I don't think its feasible to move away from db model entirely. Widely used
packages like django CMS rely on there being a site model.
On Friday, January 29, 2016 at 2:45:02 PM UTC-6, Tim Graham wrote:
>
> In another thread about adding a "scheme" field to the Site model [1], I
> floated the idea of moving the data stored by the Site model into a setting:
>
> I've sometimes thought that the Site model violates the principle that you
> shouldn't put configuration in your database. I guess there's some
> usefulness to having a ForeignKey to the site, but... would it be feasible
> to offer a SITES setting that could be used instead? e.g.
>
> SITES = {
> 1: {'scheme': 'http', 'domain': example.com, 'name': 'My Site'},
> ...
> }
>
> Carl said:+1 to this, I've long felt that the Site model was an
> anti-pattern. I don't know if it's worth deprecating and switching to a
> different system, though; it'd be a relatively painful deprecation for
> those using it, I would guess.
>
> James said: "In using Marten Kenbeek's URL dispatch rewrite branch, I've
> found that using the pattern of defining some site configuration in your
> settings is the way to go: it more easily allows you to have URL patterns
> on multiple domain/scheme combinations. I use a dict similar to what Tim
> has shown, and then use it to initialize my scheme/domain URL constraints
> in my root urls.py."
>
> I'd like to get more feedback and ideas about this. Do you think we'll be
> better off in the long run with a setting as opposed to storing the data in
> the database? Maybe writing a new sites app that uses a setting instead of
> trying to modify the existing models-based one would be a better plan.
>
> I think the hard problem to solve is what to do about the Redirect and
> FlatPage models which have ForeignKey and ManyToManyField relations to the
> Site model.
>
> Perhaps some outcome of this discussion plus considering what features of
> related third-party tools like django-hosts [2] might be useful to
> incorporate in Django itself would be worthy of a project like Google
> Summer of Code.
>
> [1]
> https://groups.google.com/d/topic/django-developers/CzxaPDe8fpI/discussion
> [2] https://github.com/jazzband/django-hosts
>
--
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/af8e6f75-8b0b-4169-9b2c-313908a59f8b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Problem UnicodeDecodeError when run createsuperuser
Hello everyone, I have a problem when run createsuperuser.py command in python 3.4. How can I solve it definitely? Look the code: https://gist.github.com/lucassimon/7837dce442e3a4a090ce4d155b4a2035 -- 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/fee89dec-a2cf-4fd1-96c3-189647202926%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Fellow Report - February 4, 2017
Triaged --- https://code.djangoproject.com/ticket/27797 - dumpdata generate a backup not usable with loaddata using MySQL (wontfix) https://code.djangoproject.com/ticket/27792 - Extended category support for Atom and RSS feeds (accepted) https://code.djangoproject.com/ticket/2 - File object does not consistently open itself in context manager use (accepted) https://code.djangoproject.com/ticket/27804 - Use unittest.subTest() in Django's test suite (created) https://code.djangoproject.com/ticket/27791 - update_or_create() doesn't work properly when model has auto_now=True (invalid) https://code.djangoproject.com/ticket/27807 - Overriding username validators doesn't work as documented (accepted) Authored -- https://github.com/django/djangoproject.com/pull/734 - Sorted corporate membership list page by membership tier. https://github.com/django/django/pull/8019 - Fixed #27805 -- Fixed ClearableFileInput's "Clear" checkbox on model fields with a default. Reviewed/committed -- https://github.com/django/django/pull/7987 - Fixed #27793 -- Used stdlib's ipaddress module to validate IP addresses. https://github.com/django/django/pull/7985 - Fixed #25192 -- Fixed squashmigrations crash with RunPython.noop on Python 2. https://github.com/django/django/pull/7924 - Fixed #27758 -- Reallowed AdvancedModelIterator pattern after template widget rendering. https://github.com/django/django/pull/7907 - Refs #27421 -- Documented GDALRaster creation in detail. https://github.com/django/django/pull/8003 - Fixed #27800 -- Fixed QuerySet.annotate(Length(...)).distinct() crash. https://github.com/django/django/pull/7781 - Fixed #27661 -- Moved FileSystemFinder's ImproperlyConfigured exceptions to system checks. https://github.com/django/django/pull/8020 - Fixed #27741 -- Isolated staticfiles testcase. https://github.com/django/django/pull/7932 - Fixed #27767 -- Added distinct argument to ArrayAgg. -- 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/cc31a0ea-d9f5-448a-a819-1654e0ebf695%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Google Summer of Code 2017
Thanks a lot for the guidance. I joined irccloud.com. Will keep posting for further queries, there! On Friday, February 3, 2017 at 6:03:33 PM UTC+5:30, Tim Graham wrote: > > There are web clients for IRC such as irccloud.com that you can use to > avoid port restrictions. This mailing list isn't the best place for basic > contributing questions. > > The #django-dev IRC channel or the mentorship mailing list could be > suitable for new contributor questions. > https://groups.google.com/group/django-core-mentorship > > If the question involves design decisions, commenting on the ticket you > intend to work on might also be appropriate. > > On Friday, February 3, 2017 at 7:16:48 AM UTC-5, HITESH V. BHAGCHANDANI > wrote: >> >> My college blocks ports for IRC and am unable to communicate freely with >> the django community. By the way, I have joined only a few days ago and >> would like to know where I can post my queries regarding details( which >> function to use, what file to edit and so on) about any patch that I'd be >> writing for a ticket. Is this mailing list the right place? >> >> On Saturday, January 21, 2017 at 2:27:33 AM UTC+5:30, Tim Graham wrote: >>> >>> I've submitted our organization application for this year. >>> >>> Anyone interested in mentoring, please indicate your interest >>> https://code.djangoproject.com/wiki/SummerOfCode2017. Any experienced >>> contributors are welcome to mentor. We also need project ideas on that >>> page. I've copied the ideas from past years, but they may not be the best. >>> If you have an idea in mind, feel free to start a new thread on this >>> mailing list to see if others think it's suitable. >>> >>> Any students interested in participating, the time to starting >>> contributing is now! The chances of developing a successful proposal >>> without any past contributions to Django is very low. >>> >>> If you have a question, let me know. >>> >> -- 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/7f6db283-e8ed-4b76-81df-c678c3412aeb%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
