Re: What happens if a Fellow has a holiday?

[Daniel Chimeno]

Enjoy your week off!


El jueves, 4 de junio de 2020, 12:47:57 (UTC+2), Carlton Gibson escribió:
>
> Hi all. 
>
> Short answer is we don't really know, since we never take holidays. 🙂
>
> I though am having a much needed week off from tomorrow, to be back on the 
> 16th. 
>
> Mariusz will need assistance as available *Approving changes*, from 
> Claude (our third merger) and the Technical Board, who can also Approve 
> PRs. 
> Mostly that's not needed for contributor PRs, but Mariusz makes a lot of 
> his *own PRs* as he's working, and those do need approval.
> Both these points by DEP 10.
>
> To facilitate this I have added the Django Technical Board GitHub team to 
> the django/django repo, with the non-write "Triage" role. 
> In this context, mostly this allows Mariusz to ask the TB by team handle 
> for a review. 
> (I trust this is OK.) 
>
> 3.1b1 is due on the 15th. We can delay that but... 
>
> Please can I ask the 6 of you to be aware that you might be needed. 
> Thanks. 
>
>
> Kind Regards,
>
> Carlton
>
>
>
>
>
>
>
>
>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/django-developers/e8d54466-08de-4908-9917-cf18ef89bb59o%40googlegroups.com.

Re: Idea: Allow queryset.get() and queryset.filter() to accept a positional argument for implicit primary key filtering

[Daniel Chimeno]

This is something I've also experimented while working with a shell, I 
often mislead the .get(pk), with .get(pk=pk), 
but only at the shell, not in the views or other places (not sure why).
For that, I'm -1 to to include it in the core, and possible the best place 
is a third package app like django-extensions or similar.



-- 
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/d4db960d-1e9a-4321-9e0a-610e78532295%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Django template 'if ... is' feature design

[Daniel Chimeno]

The *is* comparator is quite error prone for misunderstanding it (as we 
could observed some times)
maybe it worths to link python docs about it:
https://docs.python.org/3.5/reference/expressions.html#is

Well, that Python docs doesn't say to much (lack of examples)

>>> a = 'pub'
>>> b = ''.join(['p','u','b'])
>>> a == b
True
>>> a is b
False

a == b it's the same as 
id(a) == id(b)

I think we should give an emphasis on  this because are going to cause 
problems to some people.

Hope it helps. 


El jueves, 7 de abril de 2016, 23:43:21 (UTC+2), Stephen escribió:
>
> Hello, 
>
> I reviewed 
>
>  https://github.com/django/django/commit/c00ae7f5 
>
> while updating the features of Grantlee, and I have the following notes: 
>
>  * The unit tests added both have the same name ("template"). They should 
> have different names of the form 'if-tag-isNN' 
>  * The feature does not work the same way as django 'is' works. For 
> example: 
>
> In: t = e.from_string( 
>  "{% if \"True\" is \"True\" %}yes{% else %}no{% endif %}") 
> In: t.render(c) 
>
> Out: 'no' 
>
> The feature 'if ... is' feature looks like it needs more design 
> consideration before it is released. 
>
> Thanks, 
>
> Steve. 
>
>
>

-- 
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/d94f9eac-469f-48cf-bb73-09fe17572f9e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Django Integration

[Daniel Chimeno]

Hello,

There are more information about the project in the doc page:
https://channels.readthedocs.org/en/latest/

El sábado, 5 de marzo de 2016, 1:16:31 (UTC+1), Chad Paulson escribió:
>
> I was happy to read that part of the Mozilla Open Source Support program 
> funding that was recently awarded to the Django Software Foundation will go 
> toward integrating key components of Django REST Framework into Django.
>
> Since I haven't found any update since the initial announcement in 
> December, I was curious what the status of this integration is and, if 
> possible, how soon it might be available.
>
> https://www.djangoproject.com/weblog/2015/dec/11/django-awarded-moss-grant/
>

-- 
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/f8106391-7ee4-4c21-9f4c-12fc342dbc21%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Discussion] Legacy documentation / Boken docs Django v1.2

[Daniel Chimeno]

IMHO We should keep the older version of docs somewhere, ReadTheDocs it's 
fine.
But we can't only remove them. We may notice the users instead of returning 
a simple 404.
There are a lot of people still using those versions.
To keep happy search engines, we should give a 301 to somewhere, not sure 
if we should do it or not.



El jueves, 7 de agosto de 2014, 13:32:25 (UTC+2), Areski Belaid escribió:
>
> Hi Folks,
>
> I wanted to open a discussion regarding the following ticket 
> https://code.djangoproject.com/ticket/23042
>
> To summarize briefly, you may notice that we can search doc for Django 
> version 1.2 (for example 
> https://docs.djangoproject.com/search/?q=forms&release=4) but the links 
> in the result won't work.
>
>
> As Baptiste (IRC bmispelon) explained on IRC, we may have 2 approach to 
> solve this problem:
>
> 1) Fix the docs builder for versions < 1.2 (at the moment the doc-building 
> process is broken on old branches due to different version of Sphinx)
>
> 2) Discontinue older Django docs version and decide a policy regarding doc 
> hosting
>
>
> What do you think?
>
>
> -- 
> //Areski
>
>

-- 
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/ba425446-63fb-4039-b238-443adac456ed%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: add prefered/default protocol in the sites framework #26079

[Daniel Chimeno]

Hi,

I think the same in the case of:

>
>1. It would make data less portable between development (where SSL is 
>often not in use) and production.
>
> So maybe  a settings option could work.


El miércoles, 13 de enero de 2016, 14:21:14 (UTC+1), Eric Rouleau escribió:
>
> Hi
>
> I've created a ticket to propose adding a preferred/default protocol in 
> the "sites" framework at https://code.djangoproject.com/ticket/26079
>
> tim suggested I bring this to the mailing list and said the following:
>
> I'm not immediately convinced that a database field is the way to go for a 
>> couple reasons:
>>
>>1. It would make data less portable between development (where SSL is 
>>often not in use) and production.
>>2. I'm not sure it's a common case that only some sites would use SSL 
>>but not others.
>>
>> A third-party library called django-hosts, which djangoproject.com uses, 
>> adds a setting called ​HOSTS_SCHEME 
>> 
>>  to 
>> solve this. I think there's been some discussion about merging at least 
>> parts of this library into core since it solves common problems.
>>
>> See also #10944  (we might 
>> close this ticket as a duplicate of that one) and #23829 
>>  (about customizing 
>> ping_google to allow https). I think the best course of action would be 
>> to consider this feedback and write to the DevelopersMailingList 
>>  with your 
>> proposal. Either solution of a new setting or a new database field need 
>> feedback from a wider audience. Thanks!
>>
>
>- actually I would say it is even more portable as you 
>would probably use different databases between dev and prod , meaning you 
>can have http in dev but https in prod
>- its not just for SSL but also maybe a it could be used with other 
>protocols/schemes such as dav, webcal, feed
>- third party libraries could now have a definitive way of generating 
>a full URL 
>
> what do you guys think?
>
>

-- 
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/7063ff52-e065-4193-b615-f70c5cf45f1e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: FYI: pip install django is failing

[Daniel Chimeno]

There was a issue with pypi from some locations, although the status page 
doesn't say anything about it.
https://status.python.org/  

El viernes, 25 de diciembre de 2015, 13:03:05 (UTC+1), john...@gmail.com 
escribió:
>
> >pip install django --upgrade
> Collecting django
> Could not find a version that satisfies the requirement django (from 
> versions: )
> No matching distribution found for django
>
> This seems to only be an issue with django as all other packages in 
> requirements file are installing fine this morning
>
> Looking at:  https://pypi.python.org/simple/django/
>
> I see no packages... 
>

-- 
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/06435b13-400b-4b88-8260-ec6dd0c76b0b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: MOSS Award to Django

[Daniel Chimeno]

Hi,
Just saying congrats to people involved and the community. Great step for 
Django!

El viernes, 11 de diciembre de 2015, 19:19:00 (UTC+1), Andrew Godwin 
escribió:
>
> Hi everyone,
>
> For those who haven't seen, Mozilla has awarded $150,000 to Django for 
> work on Channels and request/response improvements lifted from REST 
> Framework. More in the blog post here: 
> https://www.djangoproject.com/weblog/2015/dec/11/django-awarded-moss-grant/
>
> I'll be coordinating this effort for the most part, but we're still 
> working out who to fund and the roadmap for the project, as well as work 
> out how we can pay people for their work on a different scale to the Django 
> Fellowship, so it might take a bit of time!
>
> I'll be back on here with some questions for people to discuss/answer 
> about the channels design at some point soon, but a lot of the basic design 
> is already up at http://channels.readthedocs.org, so take a read over 
> that if you're interested.
>
> What I can say is that my intention is to both bake Channels into the next 
> major release of Django, as well as hopefully release a pluggable app 
> version that will run on 1.8 and 1.9 - I have some plans around how to do 
> that effectively, but they involve hitherto unforged paths around Django 
> and how we package dependencies, so I can't say we'll get there 100%.
>
> Andrew
>

-- 
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/c25c0c0e-b3be-4190-8798-01ad9238bf25%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Documentation tool

[Daniel Chimeno]

Hello,
I'm looking for a documentation tool for my django project.
Something like JavaDoc or PHPDoc, to be able to generate a HTML|PDF with the
models, views, urls..
I've used sphinx to non-related Django projects, but I've never tried with 
Django

Any suggest?
Thanks.

Chimeno

-- 
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/5aee768c-b6c1-41de-b0d2-47c6d65bed57%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.