Re: Potentially inconsistent behavior between test client and normal WSGI requests

[Florian Apolloner]

On Saturday, April 25, 2015 at 8:46:58 AM UTC+2, Matt Hooks wrote:
>
> I'm not really familiar with the design ideals of the Django devs or the 
> WSGI spec.  From what I can tell, the spec doesn't specify whether the url 
> should be unquoted before passing it to the application.
>

I think the WSGI spec somewhat follows the CGI spec which says:
Unlike a URI path, the PATH_INFO is not URL-encoded, and cannot contain 
path-segment parameters.

So to my understanding this seems to be a bug in whatever you use, no?

Cheers,
Florian

-- 
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/3f6c9b88-1c72-4daa-9a77-1ebdf0ed393b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: virtual fields and the migration framework

[Federico Capoano]

Yes I am on 1.7 because 1.8 is not supported yet but I'm working on it.

I'll come back when I'll have more info.

Federico


On Thursday, April 23, 2015 at 8:09:42 PM UTC+2, Florian Apolloner wrote:
>
>
>
> On Thursday, April 23, 2015 at 6:59:58 PM UTC+2, Federico Capoano wrote:
>>
>> cls._meta.add_field(self, virtual=True)
>>
>> gives:
>>
>>   File "/var/www/django-hstore/django_hstore/virtual.py", line 29, in 
>> contribute_to_class
>> cls._meta.add_field(self, virtual=True)
>> TypeError: Error when calling the metaclass bases
>> add_field() got an unexpected keyword argument 'virtual'
>>
>>
> This should definitely work on master/1.8: 
> https://github.com/django/django/blob/master/django/db/models/options.py#L294 
> -- seems like you are on 1.7 or something.
>
> cheers,
> florian
>

-- 
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/0c06e657-5963-4731-a414-807265b1c9c1%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Idea/request for help: Django Developers Community Survey

[Tim Graham]

Aymeric and I put together a draft:

https://docs.google.com/forms/d/1Owv-Y_beohyCm9o2xPamdBnvjreNYoWai3rDloKZxWw/viewform

All questions are optional so you can just click through it to view the 
questions. We'll probably clear any responses before its finalized anyway.

Let us know if you think we should make any additions or changes.

On Wednesday, April 22, 2015 at 4:03:44 AM UTC-4, Federico Capoano wrote:
>
> Great idea.
> The questions look good enough to me.
>
> I love django-apps or libraries shipped in python packages. One of the 
> reason I love Django is the fact that it didn't frenetically add stuff to 
> the framework just because it's cool.
> The good thing of python packages is that you can get some data from pypi 
> (downloads) and github (clones). But we can't do that with contrib apps 
> unfortunately.
>
> Federico
>
>
> On Saturday, April 18, 2015 at 1:00:13 AM UTC+2, Tim Graham wrote:
>>
>> I had an idea to conduct a survey to get a sense of how developers are 
>> using Django. I first had the idea when the question of maintenance of the 
>> Oracle GIS backend came up. We really have no idea whether or not anyone is 
>> actually using that backend, and it would be helpful to know so we are not 
>> wasting resources on unused features. Also there's the question of how 
>> often to release Django. I think it would be nice to make that decision 
>> based on some data from the community.
>>
>> Is anyone is interested in coordinating such a survey (collating 
>> questions, preparing the online survey, etc.).
>>
>> Some question ideas to get started:
>>
>> Which database backend(s) do you use?
>> [ ] Checkbox for each one
>>
>> Which contrib apps do you use?
>> [ ] Checkbox for each one
>>
>> How often would you like to see new major version of Django released?
>> [ ] List some options, probably between 6 and 9 months.
>>
>> Describe which version of Django you use (check all the apply):
>> [ ] I only use long-term support releases.
>> [ ] I upgrade to the latest stable version as quickly as possible.
>> [ ] I run off of master.
>> [ ] I upgrade Django when the version I am using is nearing the end of 
>> its support (or after).
>> [ ] I don't bother upgrading Django, even if it becomes unsupported.
>>
>

-- 
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/f14071d1-c570-483a-abd2-833e1b47ab4d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Idea/request for help: Django Developers Community Survey

[Marc Tamlyn]

I would suggest IRC and/or Github should be options on the "I follow Django
development" question.

I'd also suggest we ask a couple of open ended questions along the line of
"What's your favourite thing about Django" and "What's your least favourite
thing about Django". I've found interesting responses from people before
along those lines.

Marc

On 25 April 2015 at 13:29, Tim Graham  wrote:

> Aymeric and I put together a draft:
>
>
> https://docs.google.com/forms/d/1Owv-Y_beohyCm9o2xPamdBnvjreNYoWai3rDloKZxWw/viewform
>
> All questions are optional so you can just click through it to view the
> questions. We'll probably clear any responses before its finalized anyway.
>
> Let us know if you think we should make any additions or changes.
>
>
> On Wednesday, April 22, 2015 at 4:03:44 AM UTC-4, Federico Capoano wrote:
>>
>> Great idea.
>> The questions look good enough to me.
>>
>> I love django-apps or libraries shipped in python packages. One of the
>> reason I love Django is the fact that it didn't frenetically add stuff to
>> the framework just because it's cool.
>> The good thing of python packages is that you can get some data from pypi
>> (downloads) and github (clones). But we can't do that with contrib apps
>> unfortunately.
>>
>> Federico
>>
>>
>> On Saturday, April 18, 2015 at 1:00:13 AM UTC+2, Tim Graham wrote:
>>>
>>> I had an idea to conduct a survey to get a sense of how developers are
>>> using Django. I first had the idea when the question of maintenance of the
>>> Oracle GIS backend came up. We really have no idea whether or not anyone is
>>> actually using that backend, and it would be helpful to know so we are not
>>> wasting resources on unused features. Also there's the question of how
>>> often to release Django. I think it would be nice to make that decision
>>> based on some data from the community.
>>>
>>> Is anyone is interested in coordinating such a survey (collating
>>> questions, preparing the online survey, etc.).
>>>
>>> Some question ideas to get started:
>>>
>>> Which database backend(s) do you use?
>>> [ ] Checkbox for each one
>>>
>>> Which contrib apps do you use?
>>> [ ] Checkbox for each one
>>>
>>> How often would you like to see new major version of Django released?
>>> [ ] List some options, probably between 6 and 9 months.
>>>
>>> Describe which version of Django you use (check all the apply):
>>> [ ] I only use long-term support releases.
>>> [ ] I upgrade to the latest stable version as quickly as possible.
>>> [ ] I run off of master.
>>> [ ] I upgrade Django when the version I am using is nearing the end of
>>> its support (or after).
>>> [ ] I don't bother upgrading Django, even if it becomes unsupported.
>>>
>>  --
> 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/f14071d1-c570-483a-abd2-833e1b47ab4d%40googlegroups.com
> 
> .
>
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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/CAMwjO1EiqZOaUm2g%2BCuwMDvDG_%2ByWVUayymAhZ-7jK5syLNarg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Idea/request for help: Django Developers Community Survey

[Carl Meyer]

On 04/25/2015 06:29 AM, Tim Graham wrote:
> Aymeric and I put together a draft:
> 
> https://docs.google.com/forms/d/1Owv-Y_beohyCm9o2xPamdBnvjreNYoWai3rDloKZxWw/viewform
> 
> All questions are optional so you can just click through it to view the
> questions. We'll probably clear any responses before its finalized anyway.
> 
> Let us know if you think we should make any additions or changes.

Looks good to me! Thanks for putting that together. Looking forward to
seeing the results.

Carl

-- 
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/553C1F22.7080100%40oddbird.net.
For more options, visit https://groups.google.com/d/optout.


signature.asc
Description: OpenPGP digital signature

Re: System check is using the default database connection for all the models

[Tim Graham]

It seems like a bug to me. If I had to guess, I'd say it's a multi-database 
setup that no one thought to test when the system check framework was 
developed.

On Friday, April 24, 2015 at 3:49:03 PM UTC-4, Ion Scerbatiuc wrote:
>
> Hello,
>
> Wasn't sure if this is a bug or not, and I couldn't find any related 
> tickets on https://code.djangoproject.com
>
> We have the following database set-up:
>
>- the default database is MySQL
>- two additional databases are PostGIS
>
> The system check framework (either `manage.py check` or `manage.py 
> runserver`) is using the default database (mysql) to validate 
> `django.contrib.gis.db.models.Model`-based models, and the commands are 
> blowing up with the following error: 
> AttributeError: 'DatabaseOperations' object has no attribute 
> 'geo_db_type'. 
>
> You can find the detailed stack trace here: 
> https://gist.github.com/delinhabit/587d6f26afb4bbc559cb
>
> We set-up database routers for the PostGIS models to use the proper 
> connection, but the check framework seems to ignore them. 
> Are we doing something wrong? 
> Is this a known pitfall of the system check framework around multiple 
> databases that we are unaware of? 
> Or is this a bug?
>
> Thanks,
> Ion
>

-- 
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/701a49c0-84e5-46cf-a002-d7eaa990f5c8%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Fellow Report - April 24, 2015

[Tim Graham]

I am thinking that if all goes well, we will probably release a 1.8.1 bug 
fix release by next Friday. Currently we have about 20 fixes for that 
release.

Report for week ending April 24, 2015:

Triaged

---

https://code.djangoproject.com/ticket/24668 - Update docs example code for 
ModelAdmin.save_formset() (fixed)

https://code.djangoproject.com/ticket/24676 - Regression on ManytoMany 
representation in the admin interface (accepted)

https://code.djangoproject.com/ticket/24675 - Skip "SET SQL_AUTO_IS_NULL = 
0" on versions of MySQL that don't need it (accepted)

https://code.djangoproject.com/ticket/24630 - Misleading/incorrect docs 
about RunPython and transactions (accepted)

https://code.djangoproject.com/ticket/24686 - Support for Moving a model 
between two Django apps (accepted)

https://code.djangoproject.com/ticket/24690 - ArrayField data bleeds 
between instances when using field.append(item) (accepted)

https://code.djangoproject.com/ticket/24689 - DetailView & ListView 
get_template_name and get_context_object_name fail with deferred QuerySet 
(accepted)

https://code.djangoproject.com/ticket/24691 - Document model._state.adding 
(since UUIDField sets value before save) (accepted)

https://code.djangoproject.com/ticket/24698 - Relation clear fails silently 
when using OneToOneField+UUIDField (accepted)

https://code.djangoproject.com/ticket/24704 - Development server does not 
restart on SynaxError (fixed)

Authored



https://github.com/django/djangoproject.com/pull/458 - Fixed #445 -- Fixed 
NotADirectory exception in docs app.

https://github.com/django/django/pull/4389 - Fixed #24526 -- Combined 
django.request/security loggers with the root logger.

https://github.com/django/django/pull/4548 - Fixed #24649 -- Allowed using 
Avg aggregate on non-numeric field types.

Reviewed/committed

--

https://github.com/django/django/pull/4534 - Refactored 
PasswordResetTokenGenerator to be a bit more extensible.

https://github.com/django/django/pull/4458 - Refs #24397 -- Sped up model 
reloading in ProjectState.

https://github.com/django/django/pull/4393 - Fixed #22394 -- Refactored 
built-in datetime lookups to transforms.

https://github.com/django/django/pull/4533 - Refs #24591 -- Optimized 
cloning of ModelState objects.

https://github.com/django/django/pull/4460 - Fixed #24591 -- Optimized 
cloning of ModelState objects.

https://github.com/django/django/pull/4539 - Fixed #24613 -- Added example 
to QuerySet.defer() documentation

https://github.com/django/django/pull/4512 - Fixed #24643 -- Added 
get_context_data() method to FormMixin

https://github.com/django/django/pull/4546 - Fixed #24689 -- Fixed 
DetailView methods with deferred QuerySet

Reviews of core dev work



https://github.com/django/django/pull/4447 - Fixed #24573 -- Considered new 
related models for reloading

https://github.com/django/django/pull/4529 - Fixed #24654 -- Based ordering 
circular references detection on columns.

https://github.com/django/django/pull/4416 - Fixed #22598 -- Allowed 
make_aware to work with ambiguous datetime

https://github.com/django/django/pull/4558 - Fixed #24701 -- Converted 
model manager names to unicode in migrations
https://github.com/django/django/pull/4555 - Added lazyness to contrib.gis 
imports

-- 
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/2bd80898-3aee-4b8a-8e5a-d11222f3022f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Idea/request for help: Django Developers Community Survey

[Shai Berger]

Hi,

On Saturday 25 April 2015 15:29:30 Tim Graham wrote:
> Aymeric and I put together a draft:
> 
> https://docs.google.com/forms/d/1Owv-Y_beohyCm9o2xPamdBnvjreNYoWai3rDloKZxW
> w/viewform
> 
> All questions are optional so you can just click through it to view the
> questions. We'll probably clear any responses before its finalized anyway.
> 
> Let us know if you think we should make any additions or changes.
> 

This looks great, thanks for putting it together. There are only a few things 
I'd like to add.

First of all, a question I find interesting about the general use pattern: "Do 
you use Django mainly for one big project, or many small ones?" I'm not sure 
what's the best way to phrase it, but I think it may be important for 
interpreting other answers (e.g. larger projects will probably tend to move 
slower w.r.t releases, will tend to use more contrib and 3rd-party apps, etc).

In "components": Request processing (URLs, middleware, view decorators).
Also, while not a "component" per se, Django's documentation is often cited as 
a valuable resource, and a lot of effort goes into it; I'm not sure adding it 
as a component adds value, but perhaps we should ask about topic guides vs. 
reference or something of the sort.

In the question about "contrib" apps, should we include the removed apps 
(comments, markup, formtools, localflavor)?

In the list of 3rd-party backends: I'm not sure what are the criteria for 
being in this list; two other 3rd-patyr backends I'm aware of are django-
pyodbc-azure (which I've used) and the proprietary mxODBC-django.

Again, thanks for the initiative,

Shai.