Re: Extended category support for feeds

Ah sorry, didn't see that Tim suggested that you should find other reviewers. Either way, please open a pull request, since that makes it easier to commit on commits. On Tuesday, January 31, 2017 at 12:05:33 PM UTC+1, Florian Apolloner wrote: > > Hi, > > there is no need to wri

Re: Template sets for widgets

On Wednesday, February 1, 2017 at 3:28:44 PM UTC+1, Tim Graham wrote: > > Hi Gert, I think the renderer API could be used for this use case. Did you > look at that? > > > https://docs.djangoproject.com/en/dev/ref/forms/renderers/#the-low-level-render-api > What I currently miss here is that there

Re: Problem UnicodeDecodeError when run createsuperuser

Please show the output of the locale command and your full settings. On Saturday, February 4, 2017 at 10:58:28 PM UTC+1, Lucas Simon Rodrigues Magalhaes wrote: > > Hello everyone, > > I have a problem when run createsuperuser.py command in python 3.4. How > can I solve it definitely? > > Look th

Re: CITextField base class

On Wednesday, February 8, 2017 at 12:00:23 PM UTC+1, Mads Jensen wrote: > > Shouldn't https://code.djangoproject.com/ticket/26610 just be reopened? > Nope, since that ticket indeed got fixed. A bug in something that got committed usually also means new ticket. -- You received this message bec

Re: Should Model.save() fix incorrect types that happen to save correctly?

On Monday, February 13, 2017 at 3:57:49 PM UTC+1, Tim Graham wrote: > > What do you think? Absent a better suggestion, we could document this > pitfall so that there's something to point to when related tickets come in. > Seems sensible. -- You received this message because you are subscribe

Re: Some thoughts about improving migration squashing

Fwiw I think by default it could/should try to optimize all migrations of an app, manually specifying the migration name should be optional. On Wednesday, February 15, 2017 at 2:00:54 PM UTC+1, rap...@makeleaps.com wrote: > > I ended up having some time today, so wrote up a management command fo

Re: Template handling of undefined variables

As much as I'd like variables to raise an error if they cannot resolve, I am with Karen here -- the backwards compatibility considerations should take priority here. At least we should have a possibility in the templates to check if variables are undefined before we start raising exceptions. Ch

Re: Adding Support for a Float32 Field

Personally I do not see much need for it in core. > If I switched to single precision, I could cut the storage size of my database in half with no loss of information. Can you elaborate more on that? For it to be able to be usable you most likely at least have also a serial field (which is anot

Re: Adding Support for a Float32 Field

On Monday, February 27, 2017 at 6:50:27 AM UTC+1, Daniel da Silva wrote: > > I'm not sure of the design rationale behind including options to specify > variants of integers, but not floats. We already have SmallIntegerField, > IntegerField, and BigIntegerField. Why is this not in the same line of

Re: Project idea for GSoC page - Support for expressions in indexes

On Saturday, March 4, 2017 at 6:52:01 AM UTC+1, akki wrote: > > @Josh Absolutely correct. I meant since this involves a lot of things (a > couple of them are listed by Markus on the ticket itself) to do, they can > use a helping hand from a student developing full-time. > The GSoC program does n

Re: Project idea for GSoC page - Support for expressions in indexes

On Saturday, March 4, 2017 at 7:10:57 PM UTC+1, akki wrote: > > First of all let's not call the work done by the 1000s of GSoC mentors > every year "putting down hands and doing nothing". > I am pretty sure I did not say that, please don't put words into my mouth. That said, the fact remains tha

Re: Project idea for GSoC page - Support for expressions in indexes

On Monday, March 6, 2017 at 3:57:48 AM UTC+1, akki wrote: > > > > On Sunday, 5 March 2017 01:53:28 UTC+5:30, Florian Apolloner wrote: >> >> On Saturday, March 4, 2017 at 7:10:57 PM UTC+1, akki wrote: >>> >>> First of all let's not call the work do

Re: Feature idea: forms signals

On Friday, March 10, 2017 at 10:12:54 AM UTC+1, David Seddon wrote: > > What are the next steps? Shall I create a pull request, or does this need > more consensus first? > Imo absolutely more consensus, especially (to minimize the work for you), please do not just suggest the signals but also t

Re: Add ability to choose a different secret for PasswordResetToken

On Saturday, March 18, 2017 at 11:11:38 AM UTC+1, jann@googlemail.com wrote: > > I'll give the override_settings a closer look, but this seems like > something one wouldn't want in a production environment. > Yes, this is only ment for tests. -- You received this message because you are

Re: Supporting a template database for test db

Sounds sensible to me. On Wednesday, March 22, 2017 at 11:53:11 AM UTC+1, Melvyn Sopacua wrote: > > Hi, > > > > I'm currently running into the problem that in order to run tests, I need > to grant my database user super-user privileges. > > No problem for dev, but I'd like to avoid that on any

Re: Typing Annotations to django core (PEP 484)

Hi, On Wednesday, March 22, 2017 at 1:43:22 PM UTC+1, matthaus woolard wrote: > > 1) makes the code easier to read > I disagree, they imo make the code harder to read, especially when the annotations are becoming a bit more complex. > Im not sure if there is any large performance hit from usi

Re: delegating our static file serving

I think there is no need to vendor nowadays, we can just depend on whitenoise. (like we do for pytz) On Wednesday, March 22, 2017 at 5:14:58 PM UTC+1, Aleksej Manaev wrote: > > Am I on the right track with the integration of WhiteNoise into Django? > Can Someone lead me to the next steps that ne

Re: Changing how Channels/ASGI receives messages

That sounds like a massive improvement and goes in line with the issues I've observed. On Tuesday, March 28, 2017 at 3:51:20 AM UTC+2, Andrew Godwin wrote: > > Hi all, > > I wanted to ask your feedback on a proposed change I want to make to the > ASGI spec for channel layers. > > In particular,

Re: Django 1.11 released

Not on purpose no -- if it doesn't work with 4.1 that is a bug On Wednesday, April 5, 2017 at 11:07:13 AM UTC+2, jorr...@gmail.com wrote: > > Is the required version of Pillow pinned at 4.0.0? I upgraded to Django > 1.11 and from Pillow 4.0.0 to 4.1.0 but now Django doesn't start because it > sa

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

What would be the benefit of using django.contrib.postgresql aside from much work? 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 database backend I want pro

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

On Sunday, May 7, 2017 at 12:45:27 PM UTC+2, Adam Johnson wrote: > > I guess we'd also have the benefit of not having to keep elasticsearch > running. > On the contrary, putting it into postgres means we have to care about it. Putting it into Elasticsearch means we can let our hoster take care a

Problems around SchemaEditor._alter_field

I am currently trying to (again?) write a database backend for Informix. So far so good, but I am running into one major issue: All of Django's other databases support changing null/default properties via "ALTER TABLE ALTER col DROP NULL/DEFAULT" or what not. In Informix I can only use "ALTER TA

Re: Problems around SchemaEditor._alter_field

I've pushed an initial PR [1], sadly I had to change one of the signatures. But I think this is an okayish change for 2.0 given that it is internal API anyways. Cheers, Florian https://github.com/django/django/pull/8487/ On Tuesday, May 9, 2017 at 3:24:46 PM UTC+2, Florian Apolloner

Re: Review of DEP 201 - simplified routing syntax

On Friday, May 12, 2017 at 12:33:28 PM UTC+2, Aymeric Augustin wrote: > > Django's URL resolver matches URLs as str (Unicode strings), not bytes, > after percent and UTF-8 decoding. As a consequence \d matches any > character in Unicode character category Nd >

Re: Cython usage within Django

On Monday, May 22, 2017 at 1:30:20 AM UTC+2, Tom Forbes wrote: > > As I understand it the Django project itself would not distribute > pre-compiled wheels, the setup.py Cython 'stuff' would handle this (and > fail gracefully if anything goes wrong, like no C compiler being > available). > Si

Re: Integrate dj-database-url into Django

Hi Kenneth, I think there are a few things to consider before we can merge/reuse dj-database-url. * How are third party backends going to fit into this scheme? * What about other options like CACHES which very much suffers from the same problem. Cheers, Florian -- You received this message

Re: migration lock file implementation

On Wednesday, May 24, 2017 at 9:42:20 PM UTC+2, Andrew Godwin wrote: > > I am personally unsure about this - it's extra overhead for smaller Django > sites, and something that larger teams could easily adopt themselves. > Yeah, I do not see an immediate need for this either. -- You received th

Re: Integrate dj-database-url into Django

On Thursday, May 25, 2017 at 9:46:56 AM UTC+2, Aymeric Augustin wrote: > > I'm wary of possible security ramifications: if we do this, changing a > configuration value will import an arbitrary module, which could make it > easier to run arbitrary code in some scenarios. I don't have a clear threa

Re: Tabs in Django Admin forms?

> to group form fields in tabs (as django-crispy-form does)?. For those who do not know django-crispy-form, how does that look like? Cheers, Florian -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsu

Re: Vendoring Select2

On Tuesday, June 6, 2017 at 11:54:16 AM UTC+2, Johannes Hoppe wrote: > > I think we made some good progress in the regarding this issue. The > inclusion of select2 is at a stage where I wouldn't want to jump to a > different library. Especially considering that now one acted at this ticket > f

Re: django.core.signing and safe characters

Hi, On Tuesday, June 20, 2017 at 12:18:21 PM UTC+2, Ole Laursen wrote: > > Yet, : is specifically mentioned as a reserved character: > It depends on the context. The assumption here is that the encoded data is always used as part of the path/querystring, for which rfc1738 says: Within the and

Re: django.core.signing and safe characters

Hi Ole, On Wednesday, June 21, 2017 at 12:42:39 PM UTC+2, Ole Laursen wrote: > > I'm sorry if I gave the impression that I'm trying to nitpick > adherence to a standard. > You absolutely did not, I guess my mail was tenser than it was intended to be. > What I'm addressing here is specificall

Re: Improving Windows users experience at the command line

Hi Ramiro, On Tuesday, July 11, 2017 at 10:55:38 PM UTC+2, Ramiro Morales wrote: > > - I run django-admin.py startproject and I get an error message stating > django-admin.py isn't a known command > FWIW django-admin.py shouldn't be used any more nowadays -- my latest changes should install dja

[newforms-admin] Confusion about queryset_add

I tried to find out for what queryset_add (http:// code.djangoproject.com/browser/django/branches/newforms-admin/django/ contrib/admin/options.py#L289) is used for. But it seems as if it is not used in the admin app (besides of defining it). So for what (is it|should it be) used? Thx Florian -

refactoring has_perm (and other permission stuff)

Hi, I am planning to rewrite the permission system in Django. Why? I am currently working a lot with ldap and use the auth_backend to auth users against the ldap-server. But working with permissions is somewhat painful, so I am planning to move the permission stuff to the auth_backend. I would im

<    4   5   6   7   8   9