Re: Can we remove FILE_CHARSET?

Thanks for the follow-up Jon. I'll let Vasili follow-up on his use-case if possible/relevant. TBH I'm not at all sure about the SQL data files bit, which is in part why I asked here. (Encoding issues!) > Maybe that sentence should be rephrased to "template files, static files, and translati

Re: Adding a database-agnostic JSONField into Django

This has come up again, with an example implementation for Oracle: https://code.djangoproject.com/ticket/29821 Anyone know of an SQLite implementation? -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. T

Re: Adding a database-agnostic JSONField into Django

xtensions exists: > https://www.sqlite.org/json1.html > > According to the release history (https://sqlite.org/changes.html) this > was added in version 3.9.0 (2015-10-14). > > But I have no direct experience working with it. > > On Thu, Oct 4, 2018 at 12:19 AM Carlton Gibson >

Fellow Reports -- October 2018

ate email about this tomorrow. 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

Widening participation (Thoughts from DjangoCon)

ve input very welcome. Hopefully there’s nothing actually controversial in all of this. 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 a

Re: Fellow Reports -- October 2018

angoproject.com/ticket/28184 -- FileField storage param should allow a callable 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

Re: Python string formatting

We had a bit of a discussion of this on Python 2 docs have got this re format(): > This method of string formatting is the new standard in Python 3, and should be preferred to the % formatting described in String Formatting Operations in new code. ​https://docs.python.org/2/library/stdtypes

Re: Python string formatting

Sorry, I typed that up and forgot to paste the link 🙄 On Wednesday, 31 October 2018 20:14:14 UTC+1, Carlton Gibson wrote: > > We had a bit of a discussion of this on > https://code.djangoproject.com/ticket/29623 -- You received this message because you are subscribed to the Goog

Re: race condition on making directories when multiple files are uploaded to the same folder

Yep. Coming up shortly... On Thursday, 1 November 2018 13:45:20 UTC+1, Tim Graham wrote: > > It's in a regression in Django 2.0 that will be fixed in today's 2.1.3 > release. > https://code.djangoproject.com/ticket/29890 > -- You received this message because you are subscribed to the Google Gr

Django bugfix release: 2.1.3

Details are available on the Django project weblog: https://www.djangoproject.com/weblog/2018/nov/01/bugfix-release/ -- 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

Re: Make input field remove newlines from value

wrong with a custom widget, as you've used. (I don't see it as a monkey patch: custom widgets are not an anti-pattern — there's no way we can account for every use-case in the core framework.) Thus, I agree with the wontfix here. Kind Regards, Carlton On Friday, 2 Novem

Re: easy pcikings

u're seeing etc) — the more detail you can provide the easier it is to help you. I hope that gets you started, and welcome aboard! Kind Regards, Carlton On Sunday, 4 November 2018 14:53:07 UTC+1, aby...@gmail.com wrote: > > Hi i am Abhith,iam new to django and i have read the newco

Fellow Reports -- November 2018

ModelAdmin.actions. 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-developer

Re: Proposal to remove ModelAdmin's collection of actions from superclasses

one?) If not, then the "usual Python behaviour" argument is favourite. (i.e. +1) — 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 rec

Re: Proposal to extend support for object permission

Both of these have small footprints and no breaking changes. So I think +1 yes. My only concern thus far is bringing out the change well enough in the release notes and docs. (Split between the two PRs I'm not sure it quite does that.) Kind Regards, Carlton -- You received thi

Re: Postgres PGCrypto in Django?

? 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...@googlegrou

Re: Proposal to extend support for object permission

2018 11:55:54 UTC+1, Tobias Bengfort wrote: > > On 08/11/2018 11:43, Carlton Gibson wrote: > > My only concern thus far is bringing out the change well enough in the > > release notes and docs. > > (Split between the two PRs I'm not sure it quite does that.) > &

Re: Extending django.contrib.auth.models Group name to be 191 character max_length

now what's going on with first_name but I think 150 chars is the go-to value here. (Hey, nice 🚲 🙂) Regards, Carlton -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from

Re: Fellow Reports -- November 2018

ased views https://code.djangoproject.com/ticket/29939 -- Increase Group.name max_length from 80 to 150 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

Re: Removing Oracle from Django core in 3.0

Hi Joe! 👋 > On 26 Nov 2018, at 09:05, Johannes Hoppe > wrote: > > I don't mind putting in extra work for an open source database. For a private > corp that makes 4bn in revenue... not so much. Is the issue “How to squeeze money out of Oracle?” — On that, did anyo

Django bugfix releases 1.11.17 and 2.1.4.

Details are available on the Django project weblog: https://www.djangoproject.com/weblog/2018/dec/03/bugfix-releases/ -- 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 sto

Re: Fellow Reports -- November 2018

) Authored: https://code.djangoproject.com/ticket/29930 -- View only permissions on stacked inline result in error Kind Regards, Carlton -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubs

Re: Allow usage of widgets in generic class-based views?

s normally" isn't good advice in context.) 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 fro

Re: Default upload permissions

r almost all users. If you're deliberately leveraging `FILE_UPLOAD_PERMISSION = None` it's an easy switch back to the current behaviour. Can I ask you to comment? Thanks. Kind Regards, Carlton -- You received this message because you are subscribed to the Google Groups "Django develop

Re: PROBLEM

ing searched.) Good luck! 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-develop

Re: PEP 484 type hinting in Django

ob/master/final/0001-dep-process.rst#dep-submission-workflow I'd guess "Forming the Team" is relevant. Happy to help if I can. (I recall Frank mentioned it no too long ago...) Kind Regards, Carlton -- You received this message because you are subscribed to the Goo

Re: Proposal: Allow contrib.sites to use the request host and fallback to a SITE_ID

wever, removing SITE_ID to > allow get_site_by_request breaks all applications which do NOT pass > request, because there is no SITE_ID. > Can you explain your example more fully please? Thanks. Kind Regards, Carlton -- You received this message because you are subscribed to th

Re: Widening participation (Thoughts from DjangoCon)

offer a pointer or two to someone who wanted to take it on." I'd like to push on these avenues (and similar) before we take on the massive project of changing systems. (Ultimately I think we'd change system and find ourselves in exactly the same boat.) Kind Regards, Carlto

Re: Database connection retry

Hi Jamesie. Two things stick out from the thread: Aymeric: might be more user-friendly, which is a goal. (If not too complex...) Tim: can you show us a patch to see what it would look like. Fancy putting together a POC? C. On Saturday, 15 December 2018 08:52:15 UTC+1, Jamesie Pic wrote: > >

Breaking change vs deprecation on Sitemaps `ping_google` command

HTTP URLs in the v2.2 release notes and move on. Thoughts please. Thanks. 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 fro

Re: Breaking change vs deprecation on Sitemaps `ping_google` command

Ah, good, yes. That might do it. Thanks Markus! -- 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+unsubsc

Fellow Reports -- December 2018

Hi all. Due to life, these are a bit late. Sorry about that. Looking forward to a good 2019. Happy new year to you all! Kind Regards, Carlton Calendar Week 49 -- ending 09 December. Released Django versions 1.11.17 and 2.1.4. Triaged: https://code.djangoproject.com/ticket/29973

Re: thoughts for Django fellowship applicants

> On 10 Jan 2019, at 20:16, Adam Johnson wrote: > > It will be hard for any new fellow to match you. I go for “aspire to…” 🙂 -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from this gr

Fellow Reports -- January 2019

the `ping_google` URL 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-developer

Re: status of 2.2 release blockers

Hi Vaclav, I think current status is "Still work to do" there, so not really... C. On Wednesday, 16 January 2019 17:52:17 UTC+1, Václav Řehák wrote: > > Hi, > > is it possible to get this fix included in 2.2? > > https://github.com/django/django/pull/10643 - Fixed #29915 -- Support > hyphens

Re: [Looking for feedback] Make Admin raw_id_fields the default choice for FKs, or project-wide configurable

This topic has come up before. e.g. https://groups.google.com/d/topic/django-developers/md39xtT_JEM/discussion (In which Aymeric suggests something similar to Harro's suggestion here.) On Thursday, 17 January 2019 06:32:15 UTC+1, Harro wrote: > If you want it in your whole project you could

Django 2.2 alpha 1 released

We've made the first release on the way to Django's next major release, Django 2.2! With about two and a half months until the final release (scheduled for April 1), we'll need timely testing from the community to ensure an on time, stable release. Check out the blog post: https://www.djan

Re: [Looking for feedback] Make Admin raw_id_fields the default choice for FKs, or project-wide configurable

On Thursday, 17 January 2019 16:14:31 UTC+1, Collin Anderson wrote: > > One problem with any of the alternatives (besides making it readonly by > default) is that it requires the other model to be registered in the admin > Off-hand I don't follow you here. Can you explain. > I hope there's

Re: [Looking for feedback] Make Admin raw_id_fields the default choice for FKs, or project-wide configurable

adjustments to ModelAdmin options could be pushed forward with a PR. “Better handling of FK widgets for fields with large counts” — sounds great, but what does that involve? Kind Regards, Carlton -- You received this message because you are subscribed to the Google Groups "Django develop

Re: [Looking for feedback] Make Admin raw_id_fields the default choice for FKs, or project-wide configurable

ng raw_id_fields. (But yes, it does come up, so very happy to see suggestions.) As Adam says, something like this could be put on PyPI, even if not in Django itself. Is there not something already I wonder? Don’t be discouraged. Please pursue the thought if you want it: implement something, o

Re: Potential suspension of Channels development

quot;straight-bat" obvious tickets away. (Michael's offer to recieve is valuable there.) "...and weird WebSocket client bugs." Can I ask you to explain what you mean there? (Point to a ticket maybe.) What kind of query do you get? Is there a particular knack to working out

Re: Introduction GSoC

t make a GSoC project, so looking through Accepted tickets (take your time! 🙂) would be a good place to look for ideas. I don't think we have a ready list of GSoC-scale project ideas we can point you to I'm afraid. (Anyone?) I hope that at least gets you started. Welcome aboard

Re: Fellow Reports -- January 2019

angelist. https://code.djangoproject.com/ticket/30102 -- Optimize the `page_not_found` view after #30070 Authored: https://github.com/django/django/pull/10855 -- Refs #30102 -- Added comment on use of Template without placeholders in default page_not_found view. Kind Regards, Carlton -- You receiv

Re: revisiting the Python version support policy

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

Re: revisiting the Python version support policy

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 i

Re: Google Summer of Code 2018

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,

Re: Google Summer of Code 2019

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 JSONFie

Re: revisiting the Python version support policy

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

Re: revisiting the Python version support policy

from making useful improvements to Django. It's not that I don't hear you hear. I do. It's just that I think of this as an accessibility issue, and accessibility is a feature too. For me, if the cost of including someone is that we have to use OrderedDict for a wee-bit lon

Re: revisiting the Python version support policy

ns we can't implement important advance Y, so we're dropping that ahead of schedule." Cool. But that's really not the case here. Continuing Python 3.5 support costs us very little against the benefits to Django as a whole. Anyway, I'm spoke out here. 🙂 Have a good day

Re: Fellow Reports -- January 2019

. 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...@googlegrou

Re: Google Summer of Code 2019

oss-DB ArrayField, but I haven’t even begun to look what the support is like there, if any at all.) 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 thi

Re: Potential suspension of Channels development

e explored all other possibilities. Burnout/overwhelm is rubbish and self-care is the #1 priority. Thanks for all your work here Andrew. Have a breather. We'll try and keep it going. 🙂 (I'm sure there's other people here who can help us when we get stuck...) Kind Regards, Carlt

Help needed on Django-Guardian.

django-guardian 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 d

Re: Google Summer of Code 2019

e for > the DSF to apply for this summer. The decision to apply on behalf of the > DSF is up to Carlton, Mariusz, or another potential mentor. > > On Thursday, January 31, 2019 at 6:24:36 AM UTC-5, gaurav jain wrote: >> >> One Idea i have a one command django project maker

Re: Google Summer of Code 2019

rity with it.) I will fill do the the Organisation application today. The programme seems a good opportunity. Kind Regards, Carlton On Monday, 4 February 2019 09:40:32 UTC+1, PARTH PATIL wrote: > > > > Hey, I am really enthusiastic for doing GSoC with Django, I had been > worki

Re: Google Summer of Code 2019

Hey Tim. > For each year your organization has participated, provide the counts of successful and total students. (e.g. 2016: 3/4) I have no idea about this, could you advise? Thanks. -- You received this message because you are subscribed to the Google Groups "Django developers (Contrib

Re: App static files (#29586)

Hi Claude. Is this something you're still interested in? Do you think it might make a good GSoC project? C. On Monday, 23 July 2018 17:36:05 UTC+2, Claude Paroz wrote: > > Hi, > > I just created a new feature request [1] to be able to define static > files per application, including a POC

Re: Google Summer of Code 2019

The best way (also) to come up with project ideas is to see where there are issues already. (Much better than us providing a list.) So again, be involved. If you start now, there's still lots of time, so I'm hoping. Kind Regards, Carlton On Monday, 4 February 2019 15:43:3

Re: Fellow Reports -- January 2019

sing CSRF_USE_SESSIONS. 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+

Re: Help needed on Django-Guardian.

! Sent from my iPhone > On 5 Feb 2019, at 07:21, Asif Saif Uddin wrote: > > Hi Carlton, > > If needed I could be a collaborator of that. I get some monthly payment for > my open source python works :) > >> On Monday, February 4, 2019 at 3:01:38 AM UTC+6, Carl

Re: Extend FAQ with "How do I get Django and my JS framework to work together?"

yet more to get off the mark quickly, - and... well... those that need the full frontend toolchain would still be free to use it. I worry we'd never get anything like this into core... but I think it would be good. (As I say, I think it's one area where we are lacking/behind

Re: Fix for Django Channels issue #962

here's already a good discussion there. Also, there's really no harm in opening a PR to show the change. Even if it's not the right solution, it helps to have something to look at. Kind Regards, Carlton On Tuesday, 5 February 2019 13:15:55 UTC+1, joonhyu...@gmail.com wro

Re: Automating the process of creating models from the data file provided

ou can get that far then the existing `inspectdb` tool can get you to model files. No doubt you could improve the workflow but that should give you some guide to get started. Kind Regards, Carlton On Thursday, 7 February 2019 12:34:21 UTC+1, Abhilasha Jha wrote: > > Hi all, > I was th

Django security releases issued: 2.1.6, 2.0.11, and 1.11.19

Today the Django team issued 2.1.6, 2.0.11, and 1.11.19 as part of our security process. These releases address a security issue, and we encourage all users to upgrade as soon as possible: https://www.djangoproject.com/weblog/2019/feb/11/security-releases/ -- You received this message because

Django 2.2 beta 1 released

We've made the second release on the way to Django's next major release, Django 2.2! With less than two months until the final release, we'll need timely testing from the community to ensure a stable release. Check out the blog post: https://www.djangoproject.com/weblog/2019/feb/11/django-22-b

Re: Django security releases issued: 2.1.6, 2.0.11, and 1.11.19

Hi Riccardo. Please open a Trac ticket for this. (Current test suite passes, so it looks like we're missing coverage somewhere.) Thanks. On Monday, 11 February 2019 12:26:04 UTC+1, riccardo.magliocchetti wrote: > > Hello Carlton, > > Il 11/02/19 12:02, Carlton Gibson ha sc

Re: Django security releases issued: 2.1.6, 2.0.11, and 1.11.19

On Monday, 11 February 2019 13:15:12 UTC+1, riccardo.magliocchetti wrote: > > > Yeah, what i'm reporting is that the wheel pip downloaded here does not > match > the 1.11.19 tag in git. > OK. Thanks. I'll have a look. -- You received this message because you are subscribed to the Google G

Re: Django security releases issued: 2.1.6, 2.0.11, and 1.11.19

On Monday, 11 February 2019 13:46:04 UTC+1, Bruno Alla wrote: > > Did something go wrong during the release publication? > Yes. Additional files were packaged. (In all except the 2.2b1 release as far as I can tell.) I will release updated versions shortly. I'll then publish a post-mortem.

Django bugfix releases: 2.1.7, 2.0.12 and 1.11.20

Updated releases correcting a packaging issue from this morning are now available for the 2.1, 2.0 and 1.11 release branches. https://www.djangoproject.com/weblog/2019/feb/11/bugfix-releases/ -- You received this message bec

Post mortem on today's packaging error.

ng a test project to install against might also be worth it. (I'd guess running the test suite would be sufficient...) Any other thoughts very welcome. Kind Regards, Carlton -- You received this message because you are subscribed to the Google Groups "Django developers (Contri

Re: Post mortem on today's packaging error.

Hi All, Thanks for all the comments. Cloning to a tmp folder and checking out a specific commit is both quick and easy. That's not a bad idea: it should eliminate the point of failure that occurred here. (The `git clean` step should do that too, we use the `fdx` flags to eliminate ignored f

Django bugfix release 2.0.13.

Details are available on the Django project weblog: https://www.djangoproject.com/weblog/2019/feb/12/bugfix-release/ -- You received this message because you are subscribed to the Google Groups "Django developers (Contribut

Re: Google Summer of Code 2019

there. If we can get all that lined up then, yes, in principle we're accepting applications. Kind Regards, Carlton On Thursday, 14 February 2019 13:46:57 UTC+1, Shashank shet wrote: > > Hello Carlton sir, > I have worked on Django as a part of a project and wished to ask if the

Re: Google Summer of Code 2019

, Shashank shet wrote: > > Thank you Carlton. I had in mind an idea for providing out-of-the-box > webserver deployment capability. In the projects I've done, one of the most > time consuming tasks for us was deployment on a server, mainly due to a > lack of experience. That

Re: Google Summer of Code 2019

The timeline for GSoC is here: https://summerofcode.withgoogle.com/how-it-works/#timeline Applications are ≈ a month away. Here's an example from a previous year: https://gist.github.com/chrismedrela/82cbda8d2a78a280a129 I'd suggest drafting things in more detail and starting a new thread to

Fellow Reports -- February 2019

realpath() in Admin script tests. 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 d

Re: GSOC 2019 proposal - Dashboard

party apps, rather than in Django itself. Do you have any kind of prototype code in place? A rough demo might give more insight into both these points. In general, for GSoC, I want to look at the project ideas, the org profile, and such over the next couple of weeks. Kind Regards, Carlton On

Re: Google Summer of Code 2019

Hi. In general, for GSoC, I want to look at the project ideas, the org profile, and such over the next couple of weeks. I try and make the Org page the starting point. Kind Regards, Carlton On Sunday, 3 March 2019 15:01:12 UTC+1, Gaurav Agarwal wrote: > > Hi, I am a student from IIT Gu

Re: GSoC 2019 Project Idea

t just not something for core.) As I just posted elsewhere, I'm looking to work on the GSoC stuff over the next couple of weeks. Kind Regards, Carlton On Sunday, 3 February 2019 11:04:07 UTC+1, PARTH PATIL wrote: > > Hey, I had a project idea for GSoC. > I wanted to make a tool

Re: Fellow Reports -- February 2019

://code.djangoproject.com/ticket/29408 -- Add validation of related fields in model Meta.ordering https://github.com/django/django/pull/10636 -- Some authentication changes for improving documentation Kind Regards, Carlton -- You received this message because you are subscribed to the Google

Re: Exposing custom views in admin index page

django-admin-views was functional as recently as Django 2.0 https://github.com/frankwiles/django-admin-views/issues/34 I'm guessing it would be pretty easy to pick up. (Frank stated he was very happy for someone to become steward...) (I appreciate that doesn't address the "should we have this

GSoC 2019 Update

ns tooling and flow? And so on...? Last chance to speak up. 🙂 I'm hopeful we can get a decent application (or a few…) Let's see. Thanks. Kind Regards, Carlton -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to

Re: GSoC 2019 Update

ideas, I still want to hear them. I hope that makes sense. (I'm quite optimistic about this stuff really.) Kind Regards, Carlton -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsub

De-assigning "Easy pickings" tickets

=changetime&desc=1&order=changetime ... I'd like to suggest that after 2 months we de-assign them, so they can get picked up by people looking, who are likely not willing/able/whatever to take over an assigned ticket themselves. Any thoughts/objections to that as a policy? Thanks.

Re: De-assigning "Easy pickings" tickets

/watch?v=uOLs3QeZy7M <https://www.youtube.com/watch?v=uOLs3QeZy7M> She’s even got helpers and such on GitHub... There’s a backporting one. We could easily have that. One that looked on Trac and saw if a PR was for a New Feature and then left a comment saying. “Carlton, please remember to

Re: help regarding google summer of code

e general purpose, rather than just targeting one JS framework. (i.e. not just Vue.) Kind Regards, Carlton On Saturday, 9 March 2019 04:05:56 UTC+1, Muhammad Faraz wrote: > > i am taking part first time in any open source project using summer of > code and i was think would the idea of

Re: Exposing custom views in admin index page

Just an aside on this, after the ORM, the admin has the second highest number of open accepted tickets. If we could bring that down, adding features would be cool, but it's a bit "Gulp" at the moment, if you take my meaning. > Note that django-admin-views is not compatible with Django 2.1. Ar

Re: Support for unittest -k option

Devs, > > https://code.djangoproject.com/ticket/30245 suggests supporting Python > unittest `-k` option, to selectively run tests matching a keyword. > > Currently, `-k` is the shorthand for `--keepdb` in Django. > A `--filter` flag was suggested to preserve backward compatibility. &g

Re: status of 2.2 release blockers

Hi All, Django 2.2rc1 is scheduled for today. There's a single release blocker that just needs a little work: https://github.com/django/django/pull/10978 As such, I'm looking towards Monday at this point. Final release on April 1 should be unaffected. Kind Regards, Carlto

Django 2.2 release candidate 1 released

We've made the final (hopefully) release on the way to Django's next major release, Django 2.2! Check out the blog post: https://www.djangoproject.com/weblog/2019/mar/18/django-22-rc1/ -- You received this message because you are subscribed to the Google Groups "Django developers (Contributio

Re: GSoC 2019 proposal - Easy Ethereum Blockchain integration

e-time-passwords being at least considered, even if preferred as a third-party app, for example — but I think yes, "Using Blockchain in Django" is out of scope for us for GSoC. Kind Regards, Carlton -- You received this message because you are subscribed to the Google Groups "

Re: GSOC 19 PROPOSAL IDEA

p;stage=Accepted&col=id&col=summary&col=status&col=owner&col=type&col=component&col=version&desc=1&order=id> — I'm sure we can help find some, but any related target ticket you identify are all for the good. Time is short here. :) Kind Rega

Google "Season of Docs"

strong writing skills and you (they) might be interested here let me know and we can look into this. I can't quite work out whether if we just apply we might attract a writer, but it would be awesome if already someone in the community was keen for this. Thanks. Kind Regards, Carlton -

Re: De-assigning "Easy pickings" tickets

Given no dissenting voices, I'll act on this. I'll deassign the stalest tickets and leave a comment for more recently updated ones. -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from t

Re: Welcome Mariusz Felisiak to his first day as a Django Fellow

💃🎁🎉 Welcome aboard Mariusz! -- 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.co

Re: GSoC 2019 proposal - Easy Ethereum Blockchain integration

if you'd have suggested "django-tensorflow" (say) I'd guess I'd think, "good luck but not for Django itself". I hope that makes sense. Kind Regards, Carlton -- You received this message because you are subscribed to the Google Groups "Django de

Re: GSoC Proposal

()` etc, as with the existing functions implementations, but...) 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 fro

Re: GSoC Proposal

Also, sorry, this was the key thread here, plus links therein https://groups.google.com/d/topic/django-developers/zfred27yVPg/discussion On Thursday, 21 March 2019 16:27:14 UTC+1, Carlton Gibson wrote: > > Hey Marcio. > > If you can demonstrate that your abilities are suffic

Fellow Reports -- March 2019

are should allow subclasses 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-develo

<    1   2   3   4   5   6   7   8   >