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
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
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
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
Hi 'st...@jigsawtech.co.uk',
I'm sorry but I can't find your name in the email.
In my proposal I explicitly propose that the few people invited should
be financed in various ways, precisely to avoid excluding someone.
Grazie,
Paolo
On Thu, Oct 27, 2022 at 8:02 AM 'st
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:
>
t the end of DjangoCon where people sprint on different
things.
To avoid further misunderstandings, I reiterate that the sprints I
propose are in some way similar to what already happens in other
communities, for example CPython [1] and HPy [2].
Grazie,
Paolo
[1]
https://discuss.python.org/t/rsvp-
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
Yes, exactly.
Paolo
On Fri, Oct 21, 2022, 10:59 Joshua Thomas wrote:
> Not to speak for Paulo, but I believe he meant using in-memory storage as
> a file storage backend, not data/database backend.
>
> On Thursday, October 20, 2022 at 4:50:49 PM UTC-7 shang.xia...@gmail.com
>
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
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
that old package.
We are talking about this during the sprints at DjangoCon US 2023 in San
Diego with Josh Thomas and Mariusz Felisiak proposed to us to ask here on
this list.
What do you think about adding an in-memory data storage backend directly
in the Django core?
Ciao,
Paolo
--
You rec
uing to investigate.
Greetings from PyCon DE 2022 in Berlin,
Paolo
--
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 receiv
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
Hi Mariusz,
I agree with you on deprecating and then removing CI fields.
I only would suggest adding some examples of migrations from CI fields
to collations in the deprecation notes to help users to easily
migrate.
So +1 for me too.
Ciao,
Paolo
On Tue, Jan 25, 2022 at 1:39 PM Mariusz
"Implementation" section in DEP 0008, we're going to run Black on the
> entire Django code repository and make a single commit. Running black
> should not encounter any issues …
>
Okay, I also hope the migration to Black will be this smooth.
So now we just have to wait for 2
done in advance. We (Fellows and OPS team) should be able to implement it
> within a few days.
>
Hi,
I was thinking we can start right now using black in a branch and see which
issue will show up and start fixing them.
Ciao,
Paolo
>
--
You received this message because you are subscri
his.
Ciao,
Paolo
--
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
Hi all,
I'm also in favour of the change, I also find the current behaviour annoying.
Paolo
On Tue, Aug 31, 2021 at 1:10 PM אורי wrote:
>
> I also find it annoying that one line changes always even if there are no
> changes in translations. I prefer the file not to ch
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
I agree with Adam.
I've also left a small comment on the PR.
Paolo
On Tue, Jan 12, 2021 at 5:59 PM Adam Johnson wrote:
>
> I think it's worth merging into 3.2. The change is quite small, the potential
> benefits are quite large, and some users live LTS to LTS so could be
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
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 don't know if there's a better way to report this type of error.
https://github.com/django/djangoproject.com/issues/1051
Best rega
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
; 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
On Sat, Oct 10, 2020 at 10:56 AM Carlton Gibson
wrote:
> Hi Paolo,
> Thank you for this! Absolutely super that you’ve taken this on.
> I’ve noted your PRs and they’re on my list to look at, hopefully next week.
> (Others please do too! )
Thanks Carlton,
I've aligned both my PR
as already reviewed the PR 1032 and I'm asking for some
other feedback and reviews on the issue and both opened PRs.
Thanks,
Paolo
[1] https://github.com/django/djangoproject.com/issues/1031
[2] https://github.com/django/djangoproject.com/pull/1030/files
[3] https://github.com/django/djangoprojec
/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
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
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 big fixtures.
I would ask someone to review my PR [3].
Thanks,
Paolo
[1] https://github.com/django/django/pull/12871
[2] https://code.djangoproject.com/ticket/31552
[3] https://github.com/django/django/pull/12879
--
https://www.paulox.net
--
You received this message because you are
an test locally.
https://github.com/django/djangoproject.com/pull/797
Can you send me some suggestions on it thanks ?
Regards,
Paolo
P.S. I've develop the multilingual search too, but it need Django 2.0
version because of this commit
https://github.com/django/django/commit/19b2dfd1bfe7fd716dd3
17/Sprints
I'll be there on Saturday 15/07/0217 and if someone would to join me I
would be happy.
--
Paolo
On Mon, May 8, 2017 at 6:28 PM, Tim Graham wrote:
> I agree that eliminating elasticsearch could be a simplification win from
> a maintenance perspective. For example, I s
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
anize a related
sprints at the next EuroPython 2017
https://ep2017.europython.eu/en/events/sprints
--
Paolo
--
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 recei
Dear Russell, PaulM and Django-devs,
I'm Paolo Coffetti, a software engineer living in Amsterdam, the
Netherlands.
I'm very close to a master degree at University of Bergamo, Italy: I've
finished all the courses and currently working on my thesis which I'll be
defending o
ill contact you again!
Cheers,
Paolo
Il giorno giovedì 6 marzo 2014 13:53:12 UTC+1, Roman Valls Guimerà ha
scritto:
>
> Hello Django-ers,
>
> I have been wondering if it would be appropiate to announce this here, but
> since it's about Django and GSoC I thought about giving
couldn't manage to be clear enough, I can link it here (I haven't done it
because I don't want to spam)
Cheers,
Paolo
--
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To unsubscribe from this group and stop receivin
Hi, I have attached a new patch to ticket 2367 to add pagination
capabilities to date based generic views.
I'd appreciate if someone interested could give feedback.
Thanks
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Gr
Hi Rob, your patch works pretty well, thanks! Finally the script
supports full completion of names ;-)
Just a couple of things.
I'd like to change the "grep -v django" line with "grep -v
django.contrib" so that applications containing "django" as a part of
their name (ex. djangotestproject.appna
Your solution looks good to me, as it adds more power to generic views
keeping their behavior consistent, without exceptions (and this point
was exactly what I tried to express in #3134).
--~--~-~--~~~---~--~~
You received this message because you are subscribed
41 matches
Mail list logo