MultiKeyDictError

[Abhineet Baranwal]

Can anyone explain me with example What is MultiKeyDictError in django and 
when it comes ?

-- 
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/3b5d2734-515b-429d-a30a-d522eff53fd9%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: MultiKeyDictError

[Adam Johnson]

This mailing list is for the development of Django itself, not for support
using Django. Please use the django-users mailing list for that, or IRC
#django on freenode, or a site like Stack Overflow.

...that said your answer is on
https://docs.djangoproject.com/en/dev/ref/request-response/ , presuming you
meant MultiValueDictKeyError .

Returns the value for the given key. If the key has more than one value, it
> returns the last value. Raises
> django.utils.datastructures.MultiValueDictKeyError if the key does not
> exist. (This is a subclass of Python’s standard KeyError, so you can stick
> to catching KeyError.)


On Thu, 4 Apr 2019 at 08:47, Abhineet Baranwal 
wrote:

> Can anyone explain me with example What is MultiKeyDictError in django and
> when it comes ?
>
> --
> 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/3b5d2734-515b-429d-a30a-d522eff53fd9%40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>


-- 
Adam

-- 
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/CAMyDDM1M_7fYEQ2QAhC6bFzOwv0J9SapJm6LB%3DdA8dA38vS-zg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Should we backport adding support for psycopg2 2.8 to the 1.11.x and 2.1.x?

[Mariusz Felisiak]

Patch for adding support for psycopg2 *2.8* is ready (see ticket #30331 
 and PR11171 
). Fix is quite 
straightforward and works with all supported version of psycopg2, i.e. 
*2.5.4+*. The question is, should we backport this fix to the *1.11.x* and 
*2.1.x*? Theoretically it doesn't qualify due to our backport policy, 
because both are in the "extended support" time.

-- 
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/46e34105-d7b3-4026-b275-738c8b6c7d01%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Should we backport adding support for psycopg2 2.8 to the 1.11.x and 2.1.x?

[Adam Johnson]

I'd say backport it. The 1.11 docs say to install 2.5.4 or higher (
https://github.com/django/django/blob/stable/1.11.x/docs/ref/databases.txt#L95
).
So either you backport the fix or edit the old docs to say <2.8, which is
just as much work?

On Thu, 4 Apr 2019 at 13:52, Mariusz Felisiak 
wrote:

> Patch for adding support for psycopg2 *2.8* is ready (see ticket #30331
>  and PR11171
> ). Fix is quite
> straightforward and works with all supported version of psycopg2, i.e.
> *2.5.4+*. The question is, should we backport this fix to the *1.11.x*
> and *2.1.x*? Theoretically it doesn't qualify due to our backport policy,
> because both are in the "extended support" time.
>
> --
> 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/46e34105-d7b3-4026-b275-738c8b6c7d01%40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>


-- 
Adam

-- 
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/CAMyDDM2npP7bQ5ikpAuTVTESj2Nt%2B07ERYKo9f%3DijdFU5Sg-AQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

a bug about ipv6?

[林杰]

OS:windows 10 1803
Python: 3.6.6 
Django version: 2.2

any django project, when run use "python manage.py runserver [::]:8000"  
the web server are listen ipv6 address ,but when you use other localhost 
ipv6 address (not ::1) ,the server well throw a UnicodeDecodeError , and 
this bug can't reappear in linux, windows7 or windows10 1709

should i repost this to microsoft ,or just here?

-- 
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/f0511b6e-cef8-40b0-8a4b-8e3322e872ea%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: GSoC Proposal (FormSet Improvement)

[PARTH PATIL]

On Thursday, April 4, 2019 at 10:02:01 AM UTC+5:30, Asif Saif Uddin wrote:
>
> I checked your contribution Parth, really good one!
>

Thank you :)
 

> once you improve your proposal, try to focus more on 
> form/formfield/formset/widget/admin/ related issues so that you have a 
> better insight into what your proposal going to improve in those areas. And 
> popular and useful extensions could be benefited from x features to be 
> implemented in that way etc. triaging the related area based tickets and 
> fixing some more related issues not only improve your chance to get 
> selected but help you understand the related areas much better. good luck 
> for GSoC this year.
>

Thanks again for the advice, I'm trying to compile a list for tickets that 
can be directly or indirectly fixed by my project. Also trying to find 12 
weeks worth of work in the formsets.
My main focus right now is:-

   - Making the request variable available throughout the formset
   - Handling relation fields in ModelFormSet  (* new)
   - declarative syntax for formset (#10403 
   )
   - adding pagination option / pretty print 

*Feel free if you would like to add something to this.*
 

> On Wednesday, April 3, 2019 at 10:06:26 PM UTC+6, PARTH PATIL wrote:
>>
>> Yes sure I will try to update my proposal by tomorrow (4th April) night 
>> (IST +5:30), So  please have a look at it once again, and suggest changes.
>>
>>
>> Best Regards,
>> PARTH PATIL
>>
>> On Wed, 3 Apr 2019, 9:23 pm Carlton Gibson,  wrote:
>>
>>> Yes, just pseudo code — so when reviewing your proposal next week it's 
>>> easy to see that it'll be the right approach. 🙂
>>>
>>> On Wednesday, 3 April 2019 17:51:18 UTC+2, PARTH PATIL wrote:



 On Wednesday, April 3, 2019 at 8:58:26 PM UTC+5:30, Carlton Gibson 
 wrote:
>
> Hey Parth. 
>
> Right. So, thanks for making the effort so far. Good. 
>
> Can you add more detail about yourself. You've not contributed to 
> Django right? So the concern at this point would be whether you're able 
> to 
> fulfil the project. 
>

 I have contributed to Django (see #30189 
 ), I have mentioned it at 
 the end of my proposal, I would try to highlight that. 

  

> What's your experience with Django? (and if you want to implement a 
> declarative formset syntax, Python more generally?)
> (Perhaps you said this, but it needs to be in the proposal.) 
>

 Sure I will add some of my projects in the proposal. 

>
> You don't necessarily need to have ideas for the final code, but what 
> does e.g. the usage look like with your idea (i.e. adding the request 
> parameter)? 
> (So the formset gets the request and this is available where...? and 
> so on: can you SHOW in your proposal that this WILL address the issues?)
>

 I'm a little bit confused here, What you mean by "SHOW that this 
 works"? 

- Do you just write some pseudo code, and say this will work?
- Or I have to prove in some way that this will work??


> HTH.
>
> Kind Regards,
>
> Carlton
>
>
> On Monday, 1 April 2019 21:29:33 UTC+2, PARTH PATIL wrote:
>>
>> Here is a link to my GSoC proposal
>> Its a first draft so you are open to comment and suggest changes
>>
>>
>> https://docs.google.com/document/d/1JuoVOU5xMwXY7JrHJshezIyuIpFfoEM49rO3e0rfNhE/edit?usp=sharing
>>
>>
>> Best Regards,
>>
>> PARTH PATIL
>>
>> SOFTWARE DEVELOPER, AUV-IITB
>>
>> CONVENOR, ELECTRONICS & ROBOTICS CLUB IIT BOMBAY.
>>
>> [image: Image result for FACEBOOK ROUND ICON] 
>>  [image: Image result for 
>> instagram ROUND ICON]  
>> [image: 
>> Image result for linkedin ROUND ICON] 
>> 
>>
>> -- 
>>> 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-d...@googlegroups.com.
>>> To post to this group, send email to django-d...@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/deae8484-5a5c-4158-b5ef-f262f30eb6eb%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  (Cont

Re: a bug about ipv6?

[Adam Johnson]

Please post the stack trace on a bug report at
https://code.djangoproject.com/ , especially after looking for similar
tickets :)

The mailing list is generally for broader discussion.

On Thu, 4 Apr 2019 at 14:15, 林杰  wrote:

> OS:windows 10 1803
> Python: 3.6.6
> Django version: 2.2
>
> any django project, when run use "python manage.py runserver [::]:8000"
> the web server are listen ipv6 address ,but when you use other localhost
> ipv6 address (not ::1) ,the server well throw a UnicodeDecodeError , and
> this bug can't reappear in linux, windows7 or windows10 1709
>
> should i repost this to microsoft ,or just here?
>
> --
> 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/f0511b6e-cef8-40b0-8a4b-8e3322e872ea%40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>


-- 
Adam

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

Re: Should we backport adding support for psycopg2 2.8 to the 1.11.x and 2.1.x?

[Mariusz Felisiak]

The only difference is that backporting the fix has some risk of regression.

-- 
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/5193cfe5-8adb-4753-bcc0-8f34739449ce%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

More standard template filters

[Collin Anderson]

Hi All,

I use django templates a lot and I always wished there was a 
myvar|startswith:"teststring", myvar|endswith:"teststring" and a 
myvar|contains:"teststring" filter.

I instead do stuff like myvar|slice:":10" == "teststring" which is a total 
hack.

Is this something that could be simple and common enough to add to django 
as batteries-included built-in?

Thanks,
Collin

-- 
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/4d465a4c-6d8c-498e-8310-d03dce5338ce%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

GSOC Proposal : CrossDB JSON Field

[Rohit Jha]

Hi 

I am Rohit Jha, I am a sophomore at IIT Roorkee. I am planning to 
participate in GSOC. My draft Proposal can be found here :

https://docs.google.com/document/d/1jSEir_wuYlBqvQTmWJUF3mpquuIH4ElZG1hFBeMl1HI/edit?usp=sharing

Feedback is much appreciated 

Thanks

-- 
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/fcaed3da-3b9f-44a0-85a5-7d5007775360%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: More standard template filters

[Curtis Maloney]

On 4/5/19 3:06 AM, Collin Anderson wrote:

Hi All,

I use django templates a lot and I always wished there was a 
myvar|startswith:"teststring", myvar|endswith:"teststring" and a 
myvar|contains:"teststring" filter.


It's almost like we need a syntax for calling methods with an argument, 
just like we can with filters.


For example (bring on the sheds for bikes!)

{{ myvar.startswith<"teststring" }}

I instead do stuff like myvar|slice:":10" == "teststring" which is a 
total hack.


Is this something that could be simple and common enough to add to 
django as batteries-included built-in?


Alternatively, I recall some time in the past I may have written a 
"strings" template filter library simply to provide string methods as 
filters...


--
Curtis

--
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/a2b323bc-9f60-f4c9-6074-4d103bd6f930%40tinbrain.net.
For more options, visit https://groups.google.com/d/optout.