Re: Django 1.4 roadmap
What happend to "SVN is least common denominator"? -- You received this message because you are subscribed to the Google Groups "Django developers" group. To view this discussion on the web visit https://groups.google.com/d/msg/django-developers/-/5DgmsJ17_8oJ. 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: Deprecate change pk + save behavior for 1.4
Settings pk as None is recommended method of model cloning, as per: https://docs.djangoproject.com/en/dev/topics/db/queries/#copying-model-instances -- You received this message because you are subscribed to the Google Groups "Django developers" group. To view this discussion on the web visit https://groups.google.com/d/msg/django-developers/-/8lwTO_Ec8I4J. 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: Python 3 port - all tests now pass on 2.7.2 and 3.2.2 with the same codebase
Most important: where to send all those beer pints? -- You received this message because you are subscribed to the Google Groups "Django developers" group. To view this discussion on the web visit https://groups.google.com/d/msg/django-developers/-/4NW-QeNEBvAJ. 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 1.4 alpha on December 22nd
This is good news. Thanks. -- You received this message because you are subscribed to the Google Groups "Django developers" group. To view this discussion on the web visit https://groups.google.com/d/msg/django-developers/-/tZW8wIV9fv0J. 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.
Sprint in Kraków (Poland)
Hello! I have a pleasure of announcing a Django sprint in Kraków, Poland. The sprint will take place on February 4th and 5th in a spacious office provided by HiddenData at Rynek Główny 17 (that's the main square). You can find map on sprint home page: http://sprint.pykonik.org/ If you're planning to attend, please register at: http://sprint.pykonik.org/registration/ As Django 1.4 is almost ready, most probably we will be focusing on fixing any bugs preventing the release. Sprint is organized by Kraków Python User Group Pykonik -- Tomek Paczkowski http://hauru.eu -- 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: Making management forms for formsets optional
I remember that Ruby on Rails solved problem with checkboxes with a hidden field that was added before each checkbox [1] [1]: http://apidock.com/rails/ActionView/Helpers/FormHelper/check_box On Friday, June 5, 2015 at 11:29:21 AM UTC+1, Patryk Zawadzki wrote: > > Hi folks, > > I've talked to Marc about fixing the case where a formset will raise > an uncaught ValidationError when instantiated with a missing or broken > management form. This has caused us great pain when dealing with > vulnerability scanners that tend to POST random crap to each endpoint > they find as it means formsets—unlike forms—are not safe to > instantiate with untrusted data. > > Now wrapping each and every formset instance in a try/except block and > having to manually handle the fallback case is not fun. But as Marc > pointed out, forgetting a management form is one of the most common > pitfalls people run into when dealing with formsets. > > Therefore I propose making the management form optional. The only case > that requires an explicit TOTAL_FORMS variable are forms that consist > of nothing but checkboxes (as unchecked checkboxes are not included in > POST data). In other cases (including all ModelFormSets as they always > contain a hidden PK field) we can deduct the number of submitted forms > from the data itself. > > Ideally I would get rid of the management form entirely and document > that a form that is nothing but checkboxes is an unsupported case and > that a workaround would be to include an extra hidden field. Honza may > or may not kill me for suggesting that. > > For now, I would like to make the formset optional and document the > cases where you need to include it. If included, it would take > precedence to keep the existing deployments working. > > Thoughts? > > -- > Patryk Zawadzki > I solve problems. > -- 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 http://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/daea9c86-ddd5-4d3e-b033-cc42f6538070%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: AutoField issue in SQLite3
I think Russ wanted to say that if you have this problem and want it fixed, the best way is go to ticket page on trac and contribute to it. It can be in couple of ways: provide useful steps to reproduce, reviewing patches etc. I see there is Pull Request attached, so try checking it out and see if it helps with your problem and then leave comment on ticket that it did or not. Broader guide to getting things done/fixed in Django is available here: https://docs.djangoproject.com/en/dev/internals/contributing/ On Wednesday, August 28, 2013 12:57:27 AM UTC+2, Russell Keith-Magee wrote: > > Hi Leonardo, > > There's no magic hidden source of information about tickets - if there's > information, it's the discussion on the ticket. > > Yours, > Russ Magee %-) > > > > On Tue, Aug 27, 2013 at 10:14 AM, Leonardo Borges Avelino < > lbo...@gmail.com > wrote: > >> >> Hi folks! >> >> Any news about this ticket: https://code.djangoproject.com/ticket/10164 ? >> >> I am having this issue using SQLite3 in django 1.5. The primary key is >> not monotonic increasing. >> >> >> Leonardo >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Django developers" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to django-develop...@googlegroups.com . >> To post to this group, send email to >> django-d...@googlegroups.com >> . >> Visit this group at http://groups.google.com/group/django-developers. >> For more options, visit https://groups.google.com/groups/opt_out. >> > > -- You received this message because you are subscribed to the Google Groups "Django developers" 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 http://groups.google.com/group/django-developers. For more options, visit https://groups.google.com/groups/opt_out.
Django Sprint in Kraków, PL: 15-16 Feb 2014
[Cross posting with django-users] Hello, Pykonik, Kraków Python User Group, would like to invite you to 3rd Django Sprint in Kraków. We would like this event to become a winter tradition, so come and join us! This year we meet on weekend of 15th and 16th February in brand new offices of Base, located at Wyczółkowskiego 7 in Kraków. If you have never contributed to Django, don't worry, this is perfect occasion to start! You don't need to know Django itself and you can learn everything on the spot. For those of you who earn money with Django, how about giving back to the community? What you learn might help you with your work. Besides, it's so fulfilling to finally squash that long lasting, annoying bug that bothered you for long time. While sprint itself is free, we kindly ask you to register at https://django-sprint-krk-2014.eventbrite.com — it will help us prepare right amount of food and drinks. By the way: bring your own laptop. More details available at: http://sprint.pykonik.org Best regards Tomek -- You received this message because you are subscribed to the Google Groups "Django developers" 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 http://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/39444e65-fadc-4a92-8d9a-756d3a7245de%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: inspectdb and non "public" schema in postgresql
If I understand correctly, your legacy database is not in "public" schema.
Django offers no support for Postgres schemas, it's left to the
developer/ops people to have correct search_path set.
There are two possible fixes for you:
- set Postgres user default search path to contain your schema
- hook into connection_created signal and set search pach manually[1]
[1]: https://docs.djangoproject.com/en/dev/ref/signals/#connection-created
On Monday, May 19, 2014 11:38:20 PM UTC+2, Fabio Caritas Barrionuevo da Luz
wrote:
>
> Hello Django core developers.
> Sorry if this is not the correct place to handle this.
>
> I have a legacy database in PostgreSQL, which is still in production.
> I want to migrate it to Django.
> I tried to do the reverse engineering of the database to generate models
> classes
>
> I set my settings like this:
>
> DATABASES = {
> # this read/write into "public" postgresql schema
> 'default': {
> 'ENGINE': 'django.db.backends.postgresql_psycopg2',
> 'NAME': 'neweposse',
> 'USER': 'neweposse_user',
> 'PASSWORD': 'neweposse_user',
> 'HOST': '127.0.0.1',
> 'PORT': '5432',
> },
> # legacy database
> 'eposse': {
> 'ENGINE': 'django.db.backends.postgresql_psycopg2',
> 'NAME': 'eposse',
> 'USER': 'eposse_user',
> 'PASSWORD': 'eposse_user',
> 'HOST': '127.0.0.1',
> 'PORT': '5432',
> }
> }
>
>
> in terminal:
>
> (django1.7a5)sutransdev@sutransdev:~/webdocpy$ python manage.py inspectdb
> ...
> from __future__ import unicode_literals
>
> from django.db import models
>
> (django1.7a5)sutransdev@sutransdev:~/webdocpy$ python manage.py inspectdb
> --database=eposse
> ...
> from __future__ import unicode_literals
>
> from django.db import models
>
>
>
> inspectdb not identify the tables in the database and does not generate
> the model classes
>
>
> The question is?
>
> 1) Am I doing something wrong. Currently there any way he could get Django
> to recognize a schema different from the "public" database schema?
>
> 2) This is really a bug, and I need to create a ticket for this?
>
> 3) or Django does not currently support different database schema, but
> this feature will be added when Marc Tamlyn add enhanced features to
> postgresql, as described here:
>
> https://www.kickstarter.com/projects/mjtamlyn/improved-postgresql-support-in-django?
>
>
>
> Thanks for the hard work to maintain this great framework
>
>
>
> --
> Fábio C. Barrionuevo da Luz
> Acadêmico de Sistemas de Informação na Faculdade Católica do Tocantins -
> FACTO
> Palmas - Tocantins - Brasil - América do Sul
>
--
You received this message because you are subscribed to the Google Groups
"Django developers" 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 http://groups.google.com/group/django-developers.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-developers/31a94b4b-d1a7-43bf-9468-bd8f65835f01%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
