Re: photobook designing

[Sebastian Bassi]

yes, you can.

On Thu, Jan 24, 2019 at 2:50 PM Esra Başkurt 
wrote:

> Hello
> I want to do a website about photobook designer like :
> https://www.adoramapix.com/books/
> 
>
> How can I do it with django?
>
> --
> 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/35c9cd0b-4a16-42c3-bee0-78be2015adf7%40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>


-- 


Non standard disclaimer: READ CAREFULLY. By reading this email,
you agree, on behalf of your employer, to release me from all
obligations and waivers arising from any and all NON-NEGOTIATED
agreements, licenses, terms-of-service, shrinkwrap, clickwrap,
browsewrap, confidentiality, non-disclosure, non-compete and
acceptable use policies ("BOGUS AGREEMENTS") that I have
entered into with your employer, its partners, licensors, agents and
assigns, in perpetuity, without prejudice to my ongoing rights and
privileges. You further represent that you have the authority to release
me from any BOGUS AGREEMENTS on behalf of your employer.
Google ads remover words: suicide, murder

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

Re: photobook designing

[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.

P.S. did you see https://www.djangoproject.com/start/ ?

On Thu, 24 Jan 2019 at 21:49, Esra Başkurt  wrote:

> Hello
> I want to do a website about photobook designer like :
> https://www.adoramapix.com/books/
> 
>
> How can I do it with django?
>
> --
> 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/35c9cd0b-4a16-42c3-bee0-78be2015adf7%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/CAMyDDM1xuOqW7Krvo1H1h9UViuNnxThYVTbJfEXzQ%3D2UMRosKQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

photobook designing

[Esra Başkurt]

Hello
I want to do a website about photobook designer like : 
https://www.adoramapix.com/books/ 


How can I do it with django?

-- 
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/35c9cd0b-4a16-42c3-bee0-78be2015adf7%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: revisiting the Python version support policy

[Carlton Gibson]

To be honest, I'm surprised there's even one person who comes within a 1000 
miles of this list who's using Python 3.5. :)

My reason for thinking we should follow Python's supported versions is 
users, and particularly beginning users, who have got they-don't-know 
version and find a tutorial just what... no sorry need... `pip3 install 
Django` to work, and give them the version of Django that corresponds to 
what they see when they visit docs.djangoproject.com. 

I don't agree this is theoretical at all. 

It's not just Debian. (Which doesn't fit my mental model here really...)

It's all those few-years-old computers out there. 

It's for example Raspbian, which as of this month is still shipping Python 
3.5. 

So my boy, who's 10, says, 

- What would you use? 
- Well I'd use Django (obviously) 
- Can I use that?
- Yeah... 

If we do drop Python 3.5 I have to say, "Well, no. But you can use this old 
one." That's not as cool.
But there will be people who are more seriously affected. 

> Who is saying, "I want to use the latest version of Django, but I want to 
use a really old version of Python."

No one is saying this. The notion of versions doesn't come into it. We're 
well beyond the barrier-to-entry before we get there. 
I (just my opinion on this) think we mistake our audience if we forget 
this.  
(For this reason I don't think the deployment issue is the relevant one. 
It's about people learning to programme, not professionals.) 

We can't support everything forever, and I'm as keen as anyone to push 
forward, but following Python is (for me) the thing we should do. 
I think Django's position in the Python eco-system requires it. 

Of course if we don't, things are easier for us, yes. 

Again, just my opinion. 
C. 

-- 
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/19e099cf-6087-4efd-9138-d338f12bbf2c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: revisiting the Python version support policy

[Ryan Hiebert]

On Thu, Jan 24, 2019 at 11:29 AM Tim Graham  wrote:

> Let's hear from people who find the current Python support policy
> insufficient for their needs.
>

Agreed. I'm not one of them, dropping 3.5 support disadvantages me in no
way. I don't use it in production or in development, and would have no
problem with 3.5 support being dropped.

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

Re: revisiting the Python version support policy

[Tim Graham]

It's interesting to me that no one (besides Claude -- and that's based on 
his ability to contribute to Django) has indicated that they care about 
Python 3.5 support in their deployments of Django 3.0... so I wonder if 
there is really a strong need for it. Who is saying, "I want to use the 
latest version of Django, but I want to use a really old version of 
Python." ... then 8 months later when Django 3.1 is released ... oh, now I 
still want to use the latest version of Django but I can't because my 
Python is too old.

It's an analogous situation to Django 2.0 and Python 3.4. From the Django 
2.0 release notes, "Django 2.0 will be the last release series to support 
Python 3.4. If you plan a deployment of Python 3.4 beyond the end-of-life 
for Django 2.0 (April 2019), stick with Django 1.11 LTS (supported until 
April 2020) instead. Note, however, that the end-of-life for Python 3.4 is 
March 2019." Is anyone in this situation? As I argued before, I think it's 
better to drop support for versions of Python after an LTS so that Django 
users aren't "stranded" on some unsupported Django because their Python is 
too old.

If we amend the policy as suggested, then I think Django 2.1 (end of 
mainstream support in April) would have gotten Python 3.4 support (end of 
support in March) -- did anyone miss that?

It's impossible to quantify how much work would be required to support the 
oldest version of Python an extra 8 or 16 months in Django's branch. It's 
not only keeping around workarounds for that older Python, but also 
developing new features with workarounds... and not being able to use new 
features in Python (or having to vendor them in Django, which then 
generally requires a deprecation of that vendored code). I think the 
justification to adopt a new policy should be clear. Currently I see "it 
would be nice" theoretical arguments. Let's hear from people who find the 
current Python support policy insufficient for their needs.

On Thursday, January 24, 2019 at 12:04:35 PM UTC-5, Ryan Hiebert wrote:
>
>
> On Thu, Jan 24, 2019 at 10:55 AM Adam Johnson > 
> wrote:
>
>> So, phrasing... maybe... as a draft: "Typically, we will support a Python 
>>> version unless it will be end of life before the corresponding version of 
>>> Django is outside of mainstream support. For example, Python 3.5 security 
>>> support ends September 2019, whilst Django 3.1 ends mainstream support in 
>>> April 2021. Therefore Django 3.0, which is end of life August 2019 is the 
>>> last version to support Python 3.5." 
>>
>>
>> +1. A subtle change on the existing policy but it makes a difference.
>>
>
> That seems better to me as well. It only ties us to the support policy of 
> Python, not various special-cased distributions. My concern, though, is 
> that it weakens semantic versioning a bit, so we should do it carefully. We 
> don't follow it precisely, but if we drop support for a version of Python, 
> that seems to me like it would qualify as a breaking change, and should be 
> preferred to be done when changing major versions after an LTS release. If 
> that is deemed to not be a significant concern, then I think this proposed 
> policy is a reasonable one.
>

-- 
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/afff11b1-5924-45a0-b204-99a2a04f5f39%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: revisiting the Python version support policy

[Adam Johnson]

>
> So, phrasing... maybe... as a draft: "Typically, we will support a Python
> version unless it will be end of life before the corresponding version of
> Django is outside of mainstream support. For example, Python 3.5 security
> support ends September 2019, whilst Django 3.1 ends mainstream support in
> April 2021. Therefore Django 3.0, which is end of life August 2019 is the
> last version to support Python 3.5."


+1. A subtle change on the existing policy but it makes a difference.

On Thu, 24 Jan 2019 at 08:16, Carlton Gibson 
wrote:

> Sorry I mistyped. " Python 3.5 security support ends September 2020" (but
> you get the point.)
>
> --
> 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/ac50c67c-51a8-4c94-9505-c19fc6fd7cfc%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/CAMyDDM1-jtxRXNXjcvr8ALPXTAh8ss-LN%3DniAODm1hNQ9nwEWA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: revisiting the Python version support policy

[Ryan Hiebert]

On Thu, Jan 24, 2019 at 10:55 AM Adam Johnson  wrote:

> So, phrasing... maybe... as a draft: "Typically, we will support a Python
>> version unless it will be end of life before the corresponding version of
>> Django is outside of mainstream support. For example, Python 3.5 security
>> support ends September 2019, whilst Django 3.1 ends mainstream support in
>> April 2021. Therefore Django 3.0, which is end of life August 2019 is the
>> last version to support Python 3.5."
>
>
> +1. A subtle change on the existing policy but it makes a difference.
>

That seems better to me as well. It only ties us to the support policy of
Python, not various special-cased distributions. My concern, though, is
that it weakens semantic versioning a bit, so we should do it carefully. We
don't follow it precisely, but if we drop support for a version of Python,
that seems to me like it would qualify as a breaking change, and should be
preferred to be done when changing major versions after an LTS release. If
that is deemed to not be a significant concern, then I think this proposed
policy is a reasonable one.

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

Re: Begninner

[Dan Davis]

George,

If you are an experienced programmer in some other language, I recommend
Fluent Python.   It is not a good book for someone new to programming.

On Thu, Jan 24, 2019 at 7:19 AM george ngugi  wrote:

> hey,
>
> Am new in python programming, can kindly can someone help me on which is
> the best site to learn the python
>
> BR George
>
> --
> 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/ee66af07-4ffb-4e0b-b8fc-648e1aca35ee%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 https://groups.google.com/group/django-developers.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-developers/CAFzonYbocP8zmuQroc992tOaL4Q6740x92ZhvwBBfwZNf%2B_%2BTg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Need to create a blog-style site

[Petr Klus]

Try https://github.com/nephila/djangocms-blog or
https://github.com/divio/aldryn-newsblog
ᐧ

On Thu, 24 Jan 2019 at 16:31, Martin F.  wrote:

> Hello all,
> I published in the Users group, but here makes more sense. Apologies for
> the double post.
>
> I need to create a website similar to www.django-cms.org with news, tags
> and articles. I could not however figure out how to do it with djangocms.
>
> Any ideas would be much appreciated.
>
> Thank you!
>
> --
> Message URL:
> https://groups.google.com/d/msg/django-cms-developers/topic-id/message-id
> Unsubscribe: send a message to
> django-cms-developers+unsubscr...@googlegroups.com
> ---
> You received this message because you are subscribed to the Google Groups
> "django CMS developers" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to django-cms-developers+unsubscr...@googlegroups.com.
> To view this discussion on the web, visit
> https://groups.google.com/d/msgid/django-cms-developers/02505e40-d94a-48fa-96fa-196a98fdbab7%40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>


-- 
*Petr Klus*

p...@bonsaitiger.com
+44 (0)203 935 6842 <00442039356842>
+44 (0)203 935 6799 <004402039356799>
www.bonsaitiger.com

*Bonsai Tiger (UK)*
24/25 The Shard
32 London Bridge Street
London
SE1 9SG
United Kingdom
P: +44 207 112 8803
E: lon...@bonsaitiger.com

*Bonsai Tiger (Croatia)*
Gotovceva 4
21 000 Split
Croatia
P: +385 95 818 45 73
E: sp...@bonsaitiger.com

"Bonsai Tiger" is a trading name of CNK Digital Solutions Ltd. A Limited
Company registered in England and Wales | Company Number 7686919
Registered Address: Dalton House 60 Windsor Avenue London SW19 2RR

-- 
Message URL: 
https://groups.google.com/d/msg/django-cms-developers/topic-id/message-id
Unsubscribe: send a message to 
django-cms-developers+unsubscr...@googlegroups.com
--- 
You received this message because you are subscribed to the Google Groups 
"django CMS developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-cms-developers+unsubscr...@googlegroups.com.
To view this discussion on the web, visit 
https://groups.google.com/d/msgid/django-cms-developers/CA%2BVn_4B2T3%3D%3DE6bmQC_-zkutVn42XQpkr7%2BtkdUb1-rqBLHyzw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Google Summer of Code 2018

[Sidhant Bendre]

Hey Cartlton, you're a life saver! Thank you so much and have nice day!

On Thursday, January 24, 2019 at 3:36:33 PM UTC+1, Carlton Gibson wrote:
>
> Hi Sidhant. 
>
> See Tim's thread from the other day: 
> https://groups.google.com/d/topic/django-developers/PcXfiDNwPxg/discussion
>
> Looking at the Wiki page from 2018 he linked, two points jump out: 
>
> * Don't feel limited to the ideas [on the page] -- if you've got a cool 
> project you want to work on, we'll probably be able to find you a mentor. 
> * Post to 
> https://groups.google.com/forum/#!forum/django-core-mentorship if you 
> need to discuss, I'm sure we can help. 
> * Any proposals for GSOC should be submitted [to this list] — plus get 
> them in soon I guess. 
>
> On Thursday, 24 January 2019 15:21:34 UTC+1, Sidhant Bendre wrote:
>>
>> Dear Django developers, I want to ask why there were no django projects 
>> for GSoC 2018? Furthermore, are there any potential mentors for this year's 
>> Google Summer of Code that I can have a conversation with as I want to get 
>> more clarity on the application process for Django and talk to them about 
>> the guidelines specific to Django regarding Google Summer of Code
>>
>

-- 
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/65a74c59-af57-4076-9ee2-01d585229baa%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Google Summer of Code 2019

[Adam Johnson]

I'd be happy to help mentor a cross-DB JSONField, it's something I'd like
to see done so I can deprecate the one I maintain in Django-MySQL.

On Thu, 24 Jan 2019 at 14:43, Carlton Gibson 
wrote:

> Perhaps it's partly the GSoC doesn't cross the radar until just a few
> weeks before the deadline... 
>
> I'm happy to help mentor but also Django Core Mentorship is there...
> https://groups.google.com/forum/#!forum/django-core-mentorship
>
>
> One idea for a good project might be adding a cross DB JSONField as per
> this thread
>
>
> https://groups.google.com/d/topic/django-developers/zfred27yVPg/discussion
>
> * All the supported DBs have native JSON support.
> * SQLite is the only one where we don't have a Django model field already
> to work on.
>* That would be first step as PoC I'd guess.
> * Then, how can we unify?
> * And, a migration path (from contrib.postgres)
>
> I don't know if that's perfect but it strikes me as eminently do-able.
>
> --
> 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/32637936-6241-43f6-bbbf-469f57d3d371%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/CAMyDDM345HrY0m71On3AgGOvvhEDPeXPPtLQk3rJyS4pWn79hw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Google Summer of Code 2019

[Carlton Gibson]

Perhaps it's partly the GSoC doesn't cross the radar until just a few weeks 
before the deadline... 

I'm happy to help mentor but also Django Core Mentorship is there...
https://groups.google.com/forum/#!forum/django-core-mentorship


One idea for a good project might be adding a cross DB JSONField as per 
this thread

  
 https://groups.google.com/d/topic/django-developers/zfred27yVPg/discussion

* All the supported DBs have native JSON support. 
* SQLite is the only one where we don't have a Django model field already 
to work on. 
   * That would be first step as PoC I'd guess. 
* Then, how can we unify? 
* And, a migration path (from contrib.postgres) 

I don't know if that's perfect but it strikes me as eminently do-able. 

-- 
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/32637936-6241-43f6-bbbf-469f57d3d371%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Google Summer of Code 2018

[Carlton Gibson]

Hi Sidhant. 

See Tim's thread from the other 
day: https://groups.google.com/d/topic/django-developers/PcXfiDNwPxg/discussion

Looking at the Wiki page from 2018 he linked, two points jump out: 

* Don't feel limited to the ideas [on the page] -- if you've got a cool 
project you want to work on, we'll probably be able to find you a mentor. 
* Post to 
https://groups.google.com/forum/#!forum/django-core-mentorship if you need 
to discuss, I'm sure we can help. 
* Any proposals for GSOC should be submitted [to this list] — plus get them 
in soon I guess. 

On Thursday, 24 January 2019 15:21:34 UTC+1, Sidhant Bendre wrote:
>
> Dear Django developers, I want to ask why there were no django projects 
> for GSoC 2018? Furthermore, are there any potential mentors for this year's 
> Google Summer of Code that I can have a conversation with as I want to get 
> more clarity on the application process for Django and talk to them about 
> the guidelines specific to Django regarding Google Summer of Code
>

-- 
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/bc84953a-a0c0-4db1-8435-34638b76e9c0%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Google Summer of Code 2018

[Sidhant Bendre]

Dear Django developers, I want to ask why there were no django projects for 
GSoC 2018? Furthermore, are there any potential mentors for this year's 
Google Summer of Code that I can have a conversation with as I want to get 
more clarity on the application process for Django and talk to them about 
the guidelines specific to Django regarding Google Summer of Code

-- 
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/bb6a50df-ffdd-41b6-a95a-16f9ac8e341e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Begninner

[Adam Johnson]

First: 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.

However: The Django tutorial is a typical place to start for web
development https://www.djangoproject.com/start/ . However if you have
never programmed before, it's probably too high level, so try something
like https://www.learnpython.org/

On Thu, 24 Jan 2019 at 07:20, george ngugi  wrote:

> hey,
>
> Am new in python programming, can kindly can someone help me on which is
> the best site to learn the python
>
> BR George
>
> --
> 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/ee66af07-4ffb-4e0b-b8fc-648e1aca35ee%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/CAMyDDM1cqzkwUhc1MHEG88XzxjOHTjDTfSbHzyDsHUgaYZoy2A%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Begninner

[george ngugi]

hey,

Am new in python programming, can kindly can someone help me on which is 
the best site to learn the python

BR George

-- 
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/ee66af07-4ffb-4e0b-b8fc-648e1aca35ee%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: revisiting the Python version support policy

[Carlton Gibson]

Sorry I mistyped. " Python 3.5 security support ends September 2020" (but 
you get the point.)

-- 
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/ac50c67c-51a8-4c94-9505-c19fc6fd7cfc%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: revisiting the Python version support policy

[Carlton Gibson]

> My idea was to set the policy as : when a new major Django version is 
released, it supports all current supported versions of Python.

I agree with this — more or less...

Python 3.5 is officially supported for the entire life of Django 3.0. (It 
goes EOL a month after Django 3.0) 
(c.p [0] vs [1])

[0]: https://devguide.python.org/#status-of-python-branches
[1]: https://www.djangoproject.com/download/#supported-versions

So I think we SHOULD support Python 3.5 for Django 3.0.
(Yes, push forward, but pushing people off of supported versions seems a 
bit over-zealous, and I think we'll be shooting ourselves in the foot, due 
to the need to repeatedly handle, probably valid, pushback.)

However Django v3.1 will be released JUST A MONTH before Python v3.5 goes 
EOL. As such I don't want to support it there. 

So, phrasing... maybe... as a draft: "Typically, we will support a Python 
version unless it will be end of life before the corresponding version of 
Django is outside of mainstream support. For example, Python 3.5 security 
support ends September 2019, whilst Django 3.1 ends mainstream support in 
April 2021. Therefore Django 3.0, which is end of life August 2019 is the 
last version to support Python 3.5." 

i.e. What Claude said except "...unless it's just about to be dropped". 

I know we backported support for Python 3.7 to Django 1.11 but I think this 
should apply to the LTS as well. 

> ...they've already made the choice to prioritize stability rather than 
access to new versions, and this is the consequence of the choice...


Just as an additional point, Django third-party apps as a rule try to 
follow Django's support versions policy. (i.e. Currently supporting 1.11+) 
This works well for people. I think the situation is equivalent with 
regards to Django and Python. 

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 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/dbab5867-b4aa-4dbe-a952-b8fbd9657e3b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.