Re: Should Django use Ada?

Thanks for the replies everybody. A few thoughts >From Adrián: > You should probably be addressing urllib devs with this inquiry (e.g. such vuln is then probably in many other web frameworks) I did that in 2021 when I found the issue with newlines in URLs. Python devs had the resources to

Should Django use Ada?

Hi all, A few years ago, I reported a vulnerability in Django because Python wasn't parsing URLs containing tabs or newlines correctly. In this ticket, it was fixed in Python: https://bugs.python.org/issue43882 But Python, being maintained mostly by volunteers, did the minimum needed work to

Re: Intermittent IntegrityError on Model Save with auto_now and auto_now_add Fields

Looks like this issue isn't affecting lots of folks, since nobody is piping up, so I'll just add that if anybody arrives here in the future, we'll be tracking this in a public issue here: https://github.com/freelawproject/courtlistener/issues/3359 My theory is it has something to do with race

Re: Pertaining the 4.2.6 release's "recreate indexes" footnote

Pardon, @Mariusz, I didn't mean to specify "non-text fields" - I had re-worded that sentence before posting. On Wednesday, October 11, 2023 at 2:29:58 AM UTC-4 Mariusz Felisiak wrote: > My immediate thought is that any indexes on non-text fields, created with > these versions, will be useless i

Pertaining the 4.2.6 release's "recreate indexes" footnote

The release notes on https://docs.djangoproject.com/en/dev/releases/4.2.6/ contain: > You may need to recreate indexes propagated to the database with Django 4.2 - 4.2.5 as they contain unnecessary ::text casting that is avoided as of this release. This doesn't give much context or give any gu

Re: Django timing

Hello thank you for the replies. The solution you mentioned is for someone using the template, the solution I am offering is just a function, I don't know if I can copy the code here for you to see and review. On Fri, Sep 9, 2022, 3:08 PM David Sanders wrote: > Hi Pelumi, > > It's kind of you to

Re: Django timing

I can connect with you on GitHub for use or work on it together On Fri, Sep 9, 2022, 3:08 PM David Sanders wrote: > Hi Pelumi, > > It's kind of you to offer code, however there is a similar functionality > in contrib.humanize: > https://docs.djangoproject.com/en/4.1/ref/contrib/humanize/#natural

Django timing

Hello. I was developing an instagram clone website but got a problem when I wanted to add timing to the post, timing like "2 minutes ago", "just now" etc. I searched through the internet I couldn't get the right solution (I don't know if there is solution for it yet). Then I decided to go on a

Re: Removal of USE_L10N setting

`USE_L10N = True` breaks all my forms that have Datetime fields. The `value` attribute of the date inputs no longer are in the right format, and the POSTing the data fails. Might be worth alerting other as part of the release. On Thursday, 11 August 2022 at 18:30:36 UTC+2 Michael wrote

Re: Removal of USE_L10N setting

Starting with version Django 5.0, with USE_L10N setting being removed, will there be any way to control how date times look in the Admin site? Removing this setting makes scientific/engineering applications lose a lot of control in the admin interface. Say I have a field created_utc and it needs

Re: Improvements to the startproject template

Problem with adam's solutions is then where do you place the project's urls.py, asgi.py and wsgi.py? Normally they are in the project dir next to settings.py. With regards to two dirs with same name, I call the outer dir 'src', which usually has related files/dirs for the project next to it, but

Settings namespaced by app_label

Models and URLSs (kind of) are namespaced by the *app_label*. I am making a Django CSS app to open source, and it requires settings. For now I am just going to copy DRF and use a dict to avoid collisions. What if in *settings.py* we could do something like this (where one has an app with an app_

Update security docs re HOST header and ALLOWED_HOSTS?

There's a vague warning in the security docs that says: > many common web servers [have] a configuration that seems to validate the > Host header [that] may not in fact do so. For instance, even if Apache is > conf

feature request: admin dark theme as an option in settings.py

Hi! We recently updated to Django==3.2.12 and were very please to find that dark theme is now supported in the admin. But, it seems this is only if the user's desktop settings are set to dark theme. It would be really great if this could be application-specific, so that the admin page always

Re: Idea

For YEARS I’ve wanted a REST solution included with Django. DRF hasn’t never felt like a great fit for Django projects. It’s very Rails-y. It would be amazing to have an official Django contrib package for REST. Never going to happen, but needs to be said. Best, Mike On Wed, Sep 15, 2021 at 4:4

runserver hangs forever, without log of error in console, in two cases

Hello, this is my first time posting, but I think bolstering django's error ouput system could be helpful as last week I spent a good amount of time debugging some issues related to django migrations 1. I began implementing DRF with DRF-Api-K

Re: #28560 - distinct() on ordered queryset with restricted list of columns returns incorrect result

Having run in to this issue in the past, automatically changing the meaning and/or breaking the query can turn in to a debug time sink. Option 3 could save people a bit of time. Cheers, Michael Manfre On Wednesday, October 28, 2020 at 8:46:46 PM UTC-4 charettes wrote: > I'm also

Re: DjangoProject

Hello Desh, I would love to collaborate with you. My Github username is* remiljw* Thanks. Virus-free. www.avast.com

Re: DEP 0008 (Formatting using Black) is accepted

I'm disappointed to learn that this was merged without a healthy debate on the deps repo. On Friday, May 10, 2019 at 8:53:44 PM UTC-5, Andrew Godwin wrote: > > One quick clarification - when I said "stable (1.0)" release, I in fact > meant the first release that the Black project officially mar

Re: Form builder application

>From my experience with similar projects, managing the data is relatively trivial in effort compared to the the effort required to make the front end useful and error free. Kind Regards, Michael Thomas On Sunday, 14 April 2019 19:56:43 UTC+5:30, Ali A Cetrefli wrote: > > Hi > We want t

Re: Potential suspension of Channels development

Hi Andrew RE: > I feel, is that is solves the wrong problem - it's focused on WebSockets, > which is a niche feature that a few people are happy we provide but most > people have no practical use for. > To me, Websockets is the defining use case for using Django Channels. From a user POV,

Re: Potential suspension of Channels development

Hi Andrew, We have a pretty active Django channel in our Slack group if you would like to direct all support requests there in the meantime. Many of us including myself are using Django Channels in production can help with basic support questions. Take care of yourself and thanks for everythi

Re: Moving database backends out of the core

tabase backend API, I suggest clearly stating that it will still be exempt from the standard deprecation policy. There was a lot of strong opposition to changing that policy in the past. Regards, Michael Manfre -- GPG Fingerprint: 74DE D158 BAD0 EDF8 keybase.io/manfre -- You received this me

Re: Updating date field using signals

This mailing list is for the development of the Django Framework. Questions related to its usage should be posted to the django-users mailing list. Regards, Michael Manfre On Fri, Nov 9, 2018 at 6:51 AM wrote: > Hi all, > > I have a very simple Profile class: > > class Profi

Re: seat selecting page .

This mailing list is for the development of Django itself, not how to use Django. The mailing list django-users is where you can ask this type of question, but you will need to make your question a bit more detailed, if you'd like to get a helpful response. Regards, Michael Manfre On Wed, O

Re: GDPR and parent domain cookies

nk we should improve that. I'm +1 on reopening the ticket to make it easier to swap in a custom ExceptionReporter for AdminEmailHandler. Regards, Michael Manfre On Mon, Aug 27, 2018 at 9:41 AM wrote: > Email error reports sent from Django (when DEBUG=False) include > information abo

Re: Deprecate PickleSerializer for session serialization?

that they would likely ignore. Regards, Michael Manfre On Sat, Aug 25, 2018 at 9:12 AM Tim Graham wrote: > Alex proposed: > > --- > > Pickle serializer has long been known to be dangerous. This is mitigated > by requiring MAC on pickle in cookies, but nevertheless, RCEs con

Re: App static files (#29586)

On Mon, Jul 23, 2018 at 12:12 PM Florian Apolloner wrote: > * Any thoughts on asset pipelines? > This seems like it would be critical functionality. It might also help users to avoid potential asset ordering issues without needing to create more apps to resolve conflicts. Regards, M

Re: default values on database level

Yeah seems like `db_default` was the felling, at least last time I scanned through this long-going discussion :D I've had to tweak Django's migration handling a bit to handle our zero-downtime requirements. SQLalchemy has had this for awhile (http://docs.sqlalchemy.org/en/latest/core/defaults

Re: Adding a tutorial for Channels

Any improvements to documentation are greatly appreciated. Thank you for taking the initiative. Regards, Michael Manfre On Mon, Feb 5, 2018, 7:05 AM David Foster wrote: > This weekend I spent several hours getting Channels configured to run a > simple chat server <https://github.com/

Re: Integrate dj-database-url into Django

me structure, how much of a safe assumption is this? > Every 3rd party database backend adheres to the internal API and must provide its own or an inherited DatabaseWrapper. Adding config_from_url seems like the best place to me. Regards, Michael Manfre -- You received this message because you ar

Re: Having a MongoDB connector for Django

as definitely a lot of fun to tinker on it, but not something I'd ever want to support in production. Regards, Michael Manfre On Fri, Sep 8, 2017 at 12:57 PM Adam Johnson wrote: > I agree, I think forcing Django's ORM to work on MongoDB is not a great > idea. Django relies he

Re: Custom Join Conditions

On Tue, Sep 5, 2017 at 5:10 AM Adam Johnson wrote: > from django.db.models import FilteredRelation is what I'd expect > This is what I'd expect too. > On 5 September 2017 at 09:44, Nicolas Delaby wrote: > >> It seems we have a consensus. >> I'll be glad to push that change. >> >> I just have

Re: Are there use cases for storing null bytes in CharField/TextField?

't support that feature. Regards, Michael Manfre On Mon, May 15, 2017 at 11:54 AM Tim Graham wrote: > Does anyone know of a use case for using null bytes in CharField/TextField? > > psycopg2 2.7+ raises ValueError("A string literal cannot contain NUL > (0x00) characters.&quo

Re: Improving MSSQL and Azure SQL support on Django

there being an officially supported MSSQL backend for Django. Microsoft has continued to be involved with Django and myself related to making a better MSSQL experience for us. Regards, Michael Manfre On Fri, Apr 28, 2017 at 3:55 PM wrote: > I wonder if there have been any updates on MS suppo

feature request: include optional html_message in send_mass_mail tuple

It seems I'm not the only one who wants to include HTML in messages sent via send_mass_mail() . It also seems an easy feature to add; i

Re: About secure-auth

atabase backend, check out the Custom Database Backends talk given at DUTH last year. Regards, Michael Manfre On Sun, Feb 19, 2017 at 8:11 PM wrote: How do I tell django to use --skip-secure-auth when connecting to mysql? 049, "Connection using old (pre-4.1.1) authentication protocol

Re: Add custom autoreload file tracking options setting

SL sounds somewhat nice, I am -0 to -1 for the debugger -- > I've seen to many sites out there running with DEBUG=True, enabling RCE > ootb seems to be pretty horrible. > I think anyone running devserver in prod deserves a breakpoint induced outage. Regards, Michael Manfre -- You

Re: Django 2.0 Python version support (Python 3.6+ only?)

it as easy as possible for them to do so (e.g. pre-notification), but not by adding more support burden (conditional code, build matricies, etc.) to Django or preventing us from using newer features from Python. Regards, Michael Manfre -- You received this message because you are subscribed to the G

Re: Guidelines to name python modules of Django applications?

As some one who maintains django packages, I wouldn't use "django_" and don't think it should be an official recommendation. I do support documenting the potential collisions to let package maintainers make a more informed decision. On Thu, Dec 8, 2016 at 7:17 AM Adam Johnson wrote: > +1 (to wha

Re: Query on Third party DB integration with DJango

go. https://docs.djangoproject.com/en/dev/internals/mailing-lists/#django-users Regards, Michael Manfre On Wed, Nov 30, 2016 at 8:14 AM Reetika Aggarwal < reetika.aggarwa...@gmail.com> wrote: > Hi, > Getting below exception while makingMigrations > > django.core.exceptions.ImproperlyConfigur

Re: Window expressions, #26608

nd > certainly nothing specific to OrderBy. Your proposed syntax is basically > what would be required `order_by=[ .. ]`. > > We (or anyone) could make an ExpressionList class that is essentially an Expression that is a list of expressions. It would basically be a Combinable with com

Re: Built-in router link generator in Django

, I don't think this is something Django should officially support for the same reasons mentioned by Marc. Regards, Michael Manfre On Mon, Oct 3, 2016 at 9:44 AM James Pic wrote: > True, this is a feature that's been invented a countless number of times. > Perhaps one impleme

Re: Django Channels Load Testing Results

Hi Robert, Thanks for doing this load testing. More context would be useful to help us outside observers to understand the potentially different variables. Is redis running locally or are you using elasticache? Regards, Michael Manfre On Mon, Sep 12, 2016 at 9:41 PM Robert Roskam wrote: >

Re: should blank POST data fallback to use model field defaults?

I believe Tom is right. The documentation is trivial but there is a need to raise an error or warning to the user when specifying required=False for boolean fields, as it is nonsensical. On Tuesday, August 16, 2016 at 12:52:06 AM UTC+1, Tom Christie wrote: > > It's not perfect but given that it'

Re: Extend support for long surnames in Django Auth

custom User model; bonus points if they make it a reusable app or even a gist. Regards, Michael Manfre On Mon, Aug 1, 2016 at 9:03 AM James Pic wrote: > Aymeric, it doesn't matter if tens of milions of names fit into your > model, it only takes one to have a issue that's goin

Re: django-mssql present and future

; I have no strong feelings either for or against it being in the official Django documentation. I've been wanting to put together a talk about creating a database backend and that will likely be the first pass at the documentation. Regards, Michael Manfre -- You received this message becaus

django-mssql present and future

ase backend, please share them. Regards, Michael Manfre -- 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-develope

Re: Should we require pytz for timezone support in Django?

I can't recall the last Django project I worked on that didn't require pytz. It makes sense to me to require it. Regards, Michael Manfre On Tue, May 17, 2016 at 6:07 AM Aymeric Augustin < aymeric.augus...@polytechnique.org> wrote: > The reasoning was based on: > >

An idea for Q filter objects

I don't know if this is possible, but I think it would highly useful if it were. Basically, I want to filter a DateField as though it were a string (see the StackOverflow post to understand why) I

Re: Feedback on Django Channels

ling with HIPAA (and some other compliance regulations) a few months ago. Regards, Michael Manfre -- 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 receivin

Re: Value of tightening URLValidator/EmailValidator regular expressions?

Simple is better. Anyone who needs/wants something more complex is not prevented by Django from doing so. Regards, Michael Manfre On Mon, Mar 14, 2016 at 2:31 PM, Aymeric Augustin < aymeric.augus...@polytechnique.org> wrote: > Indeed, for some reason, the URL and email validators get

Re: Improving MSSQL and Azure SQL support on Django

more bandwidth starting the end of this month when things are finally settled. Regards, Michael Manfre On Fri, Mar 11, 2016 at 1:54 PM, Tim Graham wrote: > Yes, I wonder if Microsoft abandoned the idea of providing engineering > resources to help out projects like django-mssql or if thin

Re: Improving MSSQL and Azure SQL support on Django

of my primary concerns because there are existing production sites that run Django on Windows. Regards, Michael Manfre On Wed, Jan 27, 2016 at 12:15 AM, Cristiano Coelho wrote: > I'm interested in the progress of this as well :) > > Sorry I didn't read through all the posts, mostly

Re: Extending JSONField serialization

to me. Allowing both to be configurable requires a trivial amount of extra effort to implement and maintain. Regards, Michael Manfre -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from t

Re: Vote on Jira as bugtracker

Agreed with the above for the same reasons. On Wed, Jan 6, 2016 at 9:17 AM, Shai Berger wrote: > What Marc and James said, and in particular what Daniele said : I get to > use Jira on a daily basis and find it cumbersome and confusing. > > Shai see > > > On 6 בינואר 2016 15:43:02 GMT+02:00, Marc

Re: Extending JSONField serialization

It should be configurable and I like the kwargs idea. I've also had to monkey patch JSONField in this way for datetimes. Regards, Michael Manfre On Tue, Jan 5, 2016 at 12:48 PM, Aymeric Augustin < aymeric.augus...@polytechnique.org> wrote: > > On 5 janv. 2016, at 18:37, To

Re: Backwards-compatibility import shims

drop support for all Django versions before the > LTS, check their package with the LTS using python -Wall and make the > deprecation warning fixes, then seamlessly add support for the next version > of Django. > > Does that make sense? > This makes sense to me. +1 Regards, M

Re: Annotation failure (Combining multiple aggregations)

On Wednesday, December 9, 2015 at 1:02:13 AM UTC-6, Anssi Kääriäinen wrote: > > This one actually does work with filter(). As the count is inside a > subselect, it can be used directly in the WHERE clause without GROUP BY or > HAVING. Using a direct count without a subselect wouldn't work. > Ha,

Re: Annotation failure (Combining multiple aggregations)

On Tuesday, December 8, 2015 at 1:26:52 AM UTC-6, Anssi Kääriäinen wrote: > > > Come to think of it, we already have a workaround: >Book.objects.annotate(author_cnt=RawSQL("(select count(*) from author > where author.book_id = book.book_id)"). > Yes, you can do a subquery to get the Sum or Co

Re: Annotation failure (Combining multiple aggregations)

I have the same problem. I tried to use `extra` but then I can't filter so it's not the best. Anybody has more info or a workaround? Thanks On Friday, December 4, 2015 at 9:47:43 AM UTC-6, Paulo Maciel wrote: > > Combining multiple aggregations with annotate() will yield the wrong > results <

Re: Fellow Report - October 17, 2015

On Tue, Oct 20, 2015 at 3:02 AM, Aymeric Augustin < aymeric.augus...@polytechnique.org> wrote: > 2015-10-20 5:04 GMT+02:00 Michael Manfre : > >> My long term plan is to switch out ADO for replaceable ODBC and FreeTDS. >> This may follow the current pattern Aymeric

Re: Fellow Report - October 17, 2015

Tim gave a good overview of the week. I'll focus my response on the MSSQL roadmap. On Sat, Oct 17, 2015 at 8:36 PM, Tim Graham wrote: > * Discussed the long-term roadmap for MSSQL support in Django. I'll let > Michael speak to the details of this. > I had the opportunity to

Re: Static typing for python methods

ssuming no core devs chime in with a -1, I'd say create a ticket and you and/or others can start working on a pull request. Regards, Michael Manfre On Sun, Oct 11, 2015 at 5:00 AM, John Michael Lafayette < johnmichaelreed...@gmail.com> wrote: > Python now has static type c

Fwd: Static typing for python methods

Python now has static type checking. All you do is follow function parameters with ": paramType" and add "-> returnType" before the colon at the end of the function declaration and auto-complete will work on the return value in IntelliJ. Can you add the function parameter types and return types

Static type checking for public API

Python now has static type checking. All you do is follow function parameters with ": paramType" and add "-> returnType" before the colon at the end of the function declaration and auto-complete will work on the return value in IntelliJ. Can you add the function parameter types and return type

Re: Making max_length argument optional

stgresql specific field should exist in django.contrib.postgres. Regards, Michael Manfre On Tue, Sep 22, 2015 at 8:40 AM, Collin Anderson wrote: > If anyone's curious, the mysql situation is as crazy as you might expect. > :) > > The max is only determined only by the total row size

Re: Making the test suite run faster

I agree with Shai. The database backend needs to be able to control this feature. Regards, Michael Manfre On Sun, Sep 6, 2015 at 12:48 PM, Shai Berger wrote: > Hi, > > On Sunday 06 September 2015 13:06:18 Aymeric Augustin wrote: > > > > This will require ./runtest

Re: revisiting the "easy pickings" flag in Trac

I never liked the "easy pickings" flag either. Your proposed change would be a good way to identify the technical ability required to make the changes to Django. Should we have a separate drop down with options to identify the non-technical (bikeshedding) difficulty of the ticket? There are certain

Re: Django ORM query syntax enhancement

+1 for making it doable for 3rd party apps. Regards, Michael Manfre On Tue, Aug 18, 2015 at 12:49 PM, Anssi Kääriäinen wrote: > I'm still thinking we shouldn't integrate any new query syntax into > 1.9. Instead lets make it easy to create 3rd party apps that offer > differ

Re: default values on database level

On Mon, Aug 3, 2015 at 9:25 AM, Podrigal, Aron wrote: > > > - Do we want to allow extending this to defaults that are applied on > every save (automatic database backed modified timestamps for example)? > > +1 for this one too. > This behavior would be a nice step toward computed (readonly) dat

Re: future of QuerySet.extra()?

As some one who has had to abuse .extra() at times to make mssql things work, I support this approach. On Fri, Jul 31, 2015 at 4:00 PM, Tim Graham wrote: > I had in mind a documentation note like this: > > Use this method as a last resort > > > This is an old API that we aim to deprecate at some

Re: default values on database level

On Wed, Jul 29, 2015 at 11:42 AM, Podrigal, Aron wrote: > Hi Loic, > > Agree with having a db_default kwarg. > > I am not using multiple databases so no experiance with db routers. So how > would should we handle routing between different databases when the > db_default value is not compatible wi

Re: Django 1.9 - JSONField

27;t support it. Regards, Michael Manfre On Tue, Jul 7, 2015 at 9:57 AM, wrote: > > Hi all, > > I'd like to know why this feature will be only available on postgres and > not as a Field for any database, like this product? This Field would be > very usefull for many users I th

CommonMiddleware DISALLOWED_USER_AGENTS logic

Dear, folks! I wonder is there some architecture rule that doesn't allow CommonMiddleware raise PermissionDenied exception? Right now if django-developer wants to use DISALLOWED_USER_AGENTS setting than all d

Re: 1.9 release planning

, and both > warnings in 1.9. > > What do you think? > > -- > Loïc > > > On Jun 17, 2015, at 08:47, Josh Smeaton wrote: > > > > I'm also +1 on the proposal as it stands, and neutral on when the semver > versioning should begin. > > > > On

Re: 1.9 release planning

I'm +1 on the Google doc proposal and like Markus, I support relabeling 1.9 to 2.0 to line the versions up with the new paradigm without the X.1 LTS oddball. Regards, Michael Manfre On Tue, Jun 16, 2015 at 12:34 PM, Collin Anderson wrote: > I also like the gdoc as it is. (1.8 LTS,

Re: 1.9 release planning

I like Colin's proposed schedule. Regards, Michael Manfre On Thu, Jun 11, 2015 at 1:12 AM, Anssi Kääriäinen wrote: > +1 to Collin's release schedule. > > This schedule should make it extremely easy to support "develop using > latest release, maintain using latest LT

Re: Django banking packages

This group is for the discussion of developing the Django framework. Discussions and questions related to using Django should take place on the django-users group. Regards, Michael Manfre On Mon, Jun 1, 2015, 7:11 AM Swapnil Bhadade wrote: > Which are Django packages for full stack developm

Re: No way to optimize batch deletion

on the post. The topic of batch deletion signaling has come up before, but I don't remember the outcome (or whether it was on here or IRC). I'll try to find it and report back when I get to a more capable device. Regards, Michael Manfre On Thu, May 7, 2015 at 7:36 PM, Antoine Cat

Re: New function to sort words with accents.

this issue. Regards, Michael Manfre On Tue, May 5, 2015 at 8:52 PM, Paulo Maciel wrote: > I am returning the query Something.objects.all().order_by(Lower('name')) > but the order is not respecting names that start with accent, causing these > results appear at the end of

Re: Guessable entry points

I like the alias. On Fri, May 1, 2015 at 5:58 AM, Aymeric Augustin < aymeric.augus...@polytechnique.org> wrote: > `python -m django` as a alias for `django-admin` sounds good. > > -- > Aymeric. > > > > On 30 avr. 2015, at 19:15, Ryan Hiebert wrote: > > https://github.com/django/django/pull/4588

Re: Must a Django Database Support Migrations?

#x27;s useful being able to modify the models that ship with Django. E.g. increasing the size of user name field. Regards, Michael Manfre -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubs

Re: 1.9 release planning

On Sat, Apr 4, 2015 at 12:56 PM, Thomas Tanner wrote: > I think rare LTS releases and frequent (6month) incremental upgrades are > a good compromise. > Third-party packages should support LTS releases and at least the latest > Django version. They may drop support for earlier non-LTS releases. >

Re: inspectdb database defaults

uses to write the model data. Regards, Michael Manfre On Tue, Mar 10, 2015 at 11:56 AM, Collin Anderson wrote: > Hi All, > > We recently added database introspection of defaults for purposes of > testing migrations. > > > https://github.com

Re: Composite fields

-1 on silently changing the field definition. At best this would result in an unnecessary migration when the error is discovered. Django should error out with a message that the composite field definition is invalid. Regards, Michael Manfre On Sun, Mar 8, 2015 at 12:29 PM, Thomas Stephenson

Re: Composite fields

ybePoint(...): >has_point = models.BooleanField() >point = Point() > > because of the inheritance limitations (which I might have to lift in the > medium-long term anyway, but which I'd like to preserve for as long as > possible to keep the initial implementation and API

Re: Composite fields

As the others have already stated, patience is required if you want meaningful feedback. Have you thought about how CompositeFields and SubFields will interact with migrations? Regards, Michael Manfre On Wed, Mar 4, 2015 at 8:16 AM, Thomas Stephenson wrote: > Considering the past

Re: A general way to batch SQL queries in Django

better than having the extra complexity of using stored procedures in a Django project. Regards, Michael Manfre On Fri, Feb 27, 2015 at 2:46 PM, Tom Evans wrote: > On Fri, Feb 27, 2015 at 3:19 PM, aRkadeFR wrote: > > What do you mean by a single roundtrip? > > He means aski

Re: Adding missing aggregate functions to contrib.postgres ?

It's reasonable to support backend specific aggregate functions. The database backend API contains BaseDatabaseOperations.check_expression_support for this exact reason. Feel free to create the ticket. Regards, Michael Manfre On Sat, Feb 7, 2015 at 9:00 AM, Andriy Sokolovskiy (coldmind) <

Re: Making the test suite run faster

test suite, but that is something that should probably happen regardless of parallelization. I'm imagining database backends being able to control whether or not they support parallelization and if each process needs its own database. Regards, Michael Manfre On Fri, Feb 6, 2015 at 11:05 A

Re: Settings: lists or tuples?

The situation you described was definitely a learning experience for your company. Your strong opinion in favor of tuples is also noted. For the various reasons stated in this thread, I'm still +1 for lists. Regards, Michael Manfre On Mon, Jan 19, 2015 at 3:13 PM, Andreas Kahnert wrote:

Re: documenting changes to the database backend API

For completeness, I'm Michael Manfre and have been the maintainer of Django-mssql [1] for the last 6+ years. Future releases of Django-mssql will officially support a single version of Django. Support for legacy versions of Django will be maintained if it requires little effort. Work on D

Re: Multiple template engines for Django - week 13

+1 to delaying the freeze to get this feature fully in place, especially since 1.8 will be an LTS release. Is there precedent to doing a freeze with an exemption for an in progress feature? If so, that is another option to an outright extension. Regards, Michael Manfre On Sat, Jan 3, 2015 at 8

Re: Multiple template engines for Django - week 12

Thanks for the explanation. It makes sense to remove select_template. Regards, Michael Manfre On Sun, Dec 28, 2014 at 3:53 AM, Aymeric Augustin < aymeric.augus...@polytechnique.org> wrote: > Hi Michael, > > > On 28 déc. 2014, at 07:12, Michael Manfre wrote: > > >

Re: Multiple template engines for Django - week 12

tensely as live sites? Regards, Michael Manfre On Sat, Dec 27, 2014 at 5:59 PM, Aymeric Augustin < aymeric.augus...@polytechnique.org> wrote: > Hello, > > My twelfth update is online: > https://myks.org/en/multiple-template-engines-for-django/#2014-12-28 > > It com

Re: Settings: lists or tuples?

+1 for lists. On Wed, Dec 17, 2014 at 3:54 PM, Carl Meyer wrote: > > On 12/17/2014 01:48 PM, Aymeric Augustin wrote: > > I’m about to introduce a new setting that is a sequence of things, > TEMPLATES, and I have to decide whether it will be a tuple of a list. > > > > Unfortunately Django is very

Re: Feature request: delegate more password related operations to auth backends (#23896)

is if you wanted to support multiple active sessions using different authentication backends for the same user object. Regards, Michael Manfre On Sat, Dec 13, 2014 at 4:28 AM, Roman Akopov wrote: > > Tim, > > It's not about the benefit, it's about the possibility. The one

Re: Optional schemes in URLValidator causes backward incompatible changes

Please open a ticket for this. On Fri, Dec 12, 2014 at 9:11 AM, Bruno Ribeiro da Silva < bruno.dev...@gmail.com> wrote: > Hey everyone, > > I just found out that the new schemes option of URLValidator causes > incompatible changes for people who were using custom regex to restrict > schemes. Coul

Re: Experimental APIs DEP

LTS? Regards, Michael Manfre -- 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...@googlegro

  1   2   3   4   5   6   7   8   9   >