Re: Post mortem on today's packaging error.

On Monday, February 11, 2019 at 11:01:55 PM UTC+1, Adam Johnson wrote: > > Jamesie’s suggestion to use CI is also valid but a bunch more work. I > guess the main advantage is you get a blank slate container to work in, > which a fresh checkout to a temp dir provides most of the gain for less

Re: Use CDN for djangoproject.com

Especially cloudflare is a service we do not want to use. as for the docs only, does the mirror on rtd work better for you? They are probably behind a CDN. Cheers, Florian On Tuesday, February 12, 2019 at 6:43:41 AM UTC+1, Cheng C wrote: > > Hi, > > Is it possible to utilize a CDN service for

Use CDN for djangoproject.com

Hi, Is it possible to utilize a CDN service for djangoproject.com, or at least on docs.djangoproject.com? The site is actually quite fast for me but I think there is still room for improvement. Cloudflare sponsored dozens of open source projects

Re: Post mortem on today's packaging error.

Thanks for the detailed post mortem Carlton. Andrew’s suggested approach to do at least a checkout to a fresh directory makes sense to me. Even got checkout and clean aren’t enough to bring an exisiting checkout folder to the same state as git won’t touch files in the gitignore. Note you can do a

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

Hi, As we are heavy ExtJS and DojoToolkit users we've encountered quite a much problems since both frameworks do have their own toolchain and it doesn't seem to fit to webpack or rollup or anything like that. So if such a feature is planned for core I really hope that non mainstream tools are

Re: Post mortem on today's packaging error.

Hi Carlton ! Seems like you're having as much fun as I had when doing releases manually :D Just sharing some food for thought here. Nowadays I have it automated and rely on setupmeta to keep myself away from touching setup.py, and just have to push git tags : http://github.com/zsimic/setupmeta

Re: Post mortem on today's packaging error.

I also ran into this several times while releasing Channels - several releases had the wrong files ship out in them due to Git weirdness. In the end, my solution was to build the release artifacts over on Travis to guarantee a fresh build environment each time, but I doubt that would work for

Re: include only columns from selected related models in select_related query

Hello Collin, Il 11/02/19 17:35, Collin Anderson ha scritto: So would you "defer" the other columns like "only()"? Yeah, something like that If nothing else, you could try using .annotate(F('author__hometown')) (not sure if that works) or .values('author__hometown') to just get the values

Re: include only columns from selected related models in select_related query

So would you "defer" the other columns like "only()"? If nothing else, you could try using .annotate(F('author__hometown')) (not sure if that works) or .values('author__hometown') to just get the values you need. On Mon, Feb 11, 2019 at 5:50 AM Riccardo Magliocchetti <

Post mortem on today's packaging error.

Hi all. This morning I released four versions of Django. Three of which, for 2.1, 2.0 and 1.11. (i.e. all the actually supported versions) were broken. In the package were additional files from `master`/2.2 which shouldn't have been there. This afternoon I have released follow-ups to

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

DJANGO FILE

PLEASE I AM NEW IN DJANGO, PLEASE I NEED THE FILES THAT WILL PUT ME THROUGH -- 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

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.

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

It looks like 2.1.6 has unexpected new migrations as well https://code.djangoproject.com/ticket/30174 Did something go wrong during the release publication? On Monday, 11 February 2019 12:07:19 UTC, Raffaele Salmaso wrote: > > On Mon, Feb 11, 2019 at 12:25 PM Riccardo Magliocchetti < >

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

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

Il 11/02/19 13:06, Raffaele Salmaso ha scritto: On Mon, Feb 11, 2019 at 12:25 PM Riccardo Magliocchetti < riccardo.magliocche...@gmail.com> wrote: InvalidTemplateLibrary: Invalid template library specified. ImportError raised when trying to load 'django.contrib.admin.templatetags.base': cannot

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

Hello Carlton, filed here: https://code.djangoproject.com/ticket/30175 Il 11/02/19 12:58, Carlton Gibson ha scritto: 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

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

On Mon, Feb 11, 2019 at 12:25 PM Riccardo Magliocchetti < riccardo.magliocche...@gmail.com> wrote: > InvalidTemplateLibrary: Invalid template library specified. ImportError > raised > when trying to load 'django.contrib.admin.templatetags.base': cannot > import name > getfullargspec > > 1.11.18

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 scritto: > > Today

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

Hello Carlton, Il 11/02/19 12:02, Carlton Gibson ha scritto: 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:

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:

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

include only columns from selected related models in select_related query

Hello, I'm debugging views leaking lots of memory in django 1.11. It looks like there is some connections with my usage of select_related(). But that's mail is not about that, not sure about my findings yet :) So I have looked again at the select_related documentation here: