Re: Proposal to upgrade django.core.mail to Python's modern email API

I agree with the approach suggested by Tom. And thanks for proposing this enhancement. Ciao, Paolo On Thu, Jun 27, 2024, 11:14 Tom Carrick wrote: > I'm in favour of this change, and nice that you're thinking about the > future, but if you're going to write a ticket for this I would focus it on

Re: Proposing the removal of Oracle from the Django supported backend databases

only intention was to understand if I were the only one to have this point of view without wanting to criticize anyone's work or past choices, things simply change in the field of information technology and choices could be reviewed after years. Ciao, Paolo -- Paolo Melchiorre https://www.paulo

Proposing the removal of Oracle from the Django supported backend databases

they are less and less. I, therefore, suggest that we start a discussion on removing Oracle from supported databases. Ciao, Paolo -- Paolo Melchiorre https://www.paulox.net -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions

Re: Fellow Reports - April 2023

Welcome Natalia 🤗 On Tue, Apr 11, 2023, 17:04 Natalia Bidart wrote: > Week ending April 9, 2023 > > Hello! I'm Natalia (AKA nessita), the new Django Fellow. I officially > started on April 1st (really :-)) though I had a slow start since I had a > long-time planned vacation. > > So far I have he

Re: Proposal for Django Core Sprints

>> >> Surely here too I left generic indications, because it seemed to me >> more than once to understand that the DSF board would not have too >> many problems in receiving new funds as long as they were destined for >> a specific objective. >> >> For exa

Re: Proposal for Django Core Sprints

ey were destined for a specific objective. For example, imagine a sprint working on only one of the proposals you listed in your last talk, it could be a point that many may have an interest in financing directly. Grazie, Paolo > On Wed, Oct 26, 2022, at 4:01 PM, Paolo Melchiorre wrote: >

Re: Proposal for Django Core Sprints

2022-core-dev-sprint-oct-3-7-sunnyvale-ca-usa/18420 [2] https://hpyproject.org/blog/posts/2022/07/dusseldorf-sprint-2022/ > On Wed, Oct 26, 2022 at 3:01 PM Paolo Melchiorre wrote: >> Following Andrew Godwin's example, I too share with you a proposal >> that I made during Dja

Proposal for Django Core Sprints

also like to have the opinions of the Django community members interested in the idea: https://www.paulox.net/2022/10/26/about-my-proposal-for-the-django-core-sprints/ Ciao, Paolo -- Paolo Melchiorre https://www.paulox.net -- You received this message because you are subscribed to the Google G

Re: Proposal: Add An in-memory data storage backend in Django

wrote: > >> Hi, >> >> I may be missing some context here but is this something distinctly >> different from setting SQLite to use in-memory storage [1]? 🤔 >> >> [1] https://www.sqlite.org/inmemorydb.html >> >> David >> >> On Fri,

Re: Proposal: Add An in-memory data storage backend in Django

ing distinctly > different from setting SQLite to use in-memory storage [1]? 🤔 > > [1] https://www.sqlite.org/inmemorydb.html > > David > > On Fri, 21 Oct 2022, 04:30 Paolo Melchiorre (paulox), < > pa...@melchiorre.org> wrote: > >> Hi all, >> >> there i

Re: Proposal: Add An in-memory data storage backend in Django

gt; [1] https://www.sqlite.org/inmemorydb.html >> >> David >> >> On Fri, 21 Oct 2022, 04:30 Paolo Melchiorre (paulox), < >> pa...@melchiorre.org> wrote: >> >>> Hi all, >>> >>> there is a package that provide in-memory data storage ba

Proposal: Add An in-memory data storage backend in Django

Hi all, there is a package that provide in-memory data storage backend, but it's now abandoned. Having support for in-memory data storage could be very useful for Django itself and furthermore it would involve adding a small code with tests that do not justify the creation of a fork of that ol

Generated Field

Hi all, I am at PyCon DE 2022 in Berlin with Markus and I shared with him this idea that I have been thinking about for a few months, given his interest I also share it with you. I figured we could add in Django a "GeneratedField" which accepts a "base_field" attribute in a similar way to "ArrayF

Re: Preparing Django code for the Black stable release

Hi all, Black 22.1.0 has just been released https://github.com/psf/black/releases/tag/22.1.0 It seems the time has come to put DEP 0008 into practice and "run Black on the entire Django code repository and make a single commit". Ciao, Paolo On Wed, Oct 20, 2021 at 10:52 PM Paolo

Re: Deprecate CICharField, CIEmailField, CITextField

docs/12/citext.html > > -- > 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: Preparing Django code for the Black stable release

On Wed, Oct 20, 2021, 21:51 Mariusz Felisiak wrote: > > I was thinking we can start right now using black in a branch and see >> which issue will show up and start fixing them. >> > > We don't want to merge multiple commits related to black. According to the > "Implementation" section in DEP 0008

Re: Preparing Django code for the Black stable release

On Wed, Oct 20, 2021, 11:37 Mariusz Felisiak wrote: > > I think we can start prepare this great migrations of the Django code so >> we will be ready when Black 22.0 will be released and we can finally >> benefit from this change. >> > > Do you have any specific steps in mind? I'm not sot sure how

Preparing Django code for the Black stable release

Hi all, More than two years ago the 'DEP 0008: Formatting using Black' was accepted with the constraint to wait until Black got to a stable release: https://github.com/django/deps/blob/main/accepted/0008-black.rst As you can see from this pull request in the Black code the first stable release

Re: makemessages management command should not touch POT-Creation-Date

nce again. >>> If the po file exists, the makemessages command uses `msgmerge` in the >>> `write_po_file` method to get the contents of the po file. (Refer this). >>> However, msgmerge is not ran in the update mode using the `--update` flag. >>> I propose on adde

Re: Translations

Hi Zain, I think you can ask on the specific mailing list for this subject https://groups.google.com/g/django-i18n Paolo On Mon, May 10, 2021, 22:36 Zain Al-abdeen wrote: > hi , > i want to translate the django website and documentation , > > can anyone show me the way to do this? > -- You r

Re: Status of 3.2 release blockers.

>>> Time to begin release process for the next major release, Django 3.2! >>> >>> Reference: https://code.djangoproject.com/wiki/Version3.2Roadmap >>> >>> The 3.2 feature freeze is scheduled for January 14. >>> We'll probably release the alph

Re: Django project 503 issue

19348723712 > > On Sat, 5 Dec 2020 at 17:06, Paolo Melchiorre > wrote: > >> Hi all, >> >> I noticed that the Django project website is responding to an HTTP status >> 503. >> >> I found an issue on github and I added a comment to it. >> >> I do

Django project 503 issue

rds, Paolo -- Paolo Melchiorre https://www.paulox.net -- 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

Re: Model Generation for CSV, XLS Files

I know my answer is not useful for other supported database backends, I only tried to share my experience. Best, Paolo -- Paolo Melchiorre https://www.paulox.net -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itse

Re: Revisiting Python support for after Django 3.2 LTS

; I think though that dropping support for Python 3.7 would be a little > aggressive ... I agree with you. Python 3.7 is still the default version in the stable version of Debian 10 (Buster) with LTS until 2024. Kind regards, Paolo -- Paolo Melchiorre https://www.paulox.net -- You received this

Re: Updating the documentation search

s with the master branch and updated a bit after reading some comments from Adam. Feedback and comments from everyone are welcome to the issue https://github.com/django/djangoproject.com/issues/1031 Have a good weekends, Paolo -- Paolo Melchiorre https://www.paulox.net -- You received this me

Updating the documentation search

t.com/pull/1032/files -- Paolo Melchiorre https://www.paulox.net -- 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 em

Critical hints about Django migrations

/surviving-django/ See you, Paolo -- Paolo Melchiorre https://www.paulox.net -- 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

Re: f-strings again.

tand against f-strings, I think we can allow them. My main >>> concerns is readability. ... >>> I'm strongly against any bulk updates to conform to this style >>> I would also be in favor of keeping only %-formatting and f-strings in >>> Coding style doc

Re: Loading lzma compressed fixtures

On 09/05/20 12:39, Tim Graham wrote: On Saturday, May 9, 2020 at 6:22:13 AM UTC-4, Paolo Melchiorre wrote: Working at my latest merged PR [1] in Django I saw in the code the lack of support for lzma compressed fixture for loaddata command so I opened a ticket [2] and a related PR [3]. I think

Loading lzma compressed fixtures

Hi all, Working at my latest merged PR [1] in Django I saw in the code the lack of support for lzma compressed fixture for loaddata command so I opened a ticket [2] and a related PR [3]. I think is a small PR to accept before Django 3.1 feature freeze but it can be a great improvement in loa

Re: Proposal: provide postgresql powered full-text search in djangoproject.com

d8bfa5f972070d83b42f On Sat, Jul 8, 2017 at 8:10 PM, Paolo Melchiorre wrote: > I'm going to start a personal branch with a PostgreSQL full-text search > functionality for the djangoproject.com website. > > I would to sprint on it during the next EuroPython 2017 in Rimini and I&

Re: Proposal: provide postgresql powered full-text search in djangoproject.com

Hi all, I'm going to start a personal branch with a PostgreSQL full-text search functionality for the djangoproject.com website. I would to sprint on it during the next EuroPython 2017 in Rimini and I've added the Sprint proposal in the wiki: https://wiki.python.org/moin/EuroPython2017/Sprints I

Re: Proposal: provide postgresql powered full-text search in djangoproject.com

On Sun, May 7, 2017 at 9:16 AM, Florian Apolloner wrote: > On Sunday, May 7, 2017 at 12:50:02 AM UTC+2, Paolo Melchiorre wrote: >> >> Hello, >> >> in the djangoproject.com the search is powered by elasticsearch. >> >> Since the site uses postgresql as databa

Proposal: provide postgresql powered full-text search in djangoproject.com

Hello, in the djangoproject.com the search is powered by elasticsearch. Since the site uses postgresql as database backend I want propose to use the Full-Text Search function provided by django.contrib.postgres.search module. I presented a talk "Full-Text Search in Django with PostgreSQL" at t