Re: Select API choice when starting new project.

thank you i didn't know. On Mon, Apr 17, 2023 at 8:26 AM Florian Apolloner wrote: > Hi, this is something which is already supported via the template argument > to startproject/startapp. > > Cheers, > florian > > On Sunday, April 16, 2023 at 11:47:44 PM UTC+2 Daniel Azub

Select API choice when starting new project.

When starting a new Django project, the user can select if he wants to build an API or use the Django template. If he chooses API, then Django-rest framework will be installed, and then serializers.py will be added to the folders. -- You received this message because you are subscribed to the

Re: Add a minimal Gitignore

Mar 9, 2023, 14:13 Daniel Azubuine > wrote: > >> Yeah >> >> What I meant is for the default ‘startproject’ template to include a >> minimal .gitignore file. >> >> I've added the template. >> Just wanted to ask before I push >> >> On Thu, M

Re: Add a minimal Gitignore

Yeah What I meant is for the default ‘startproject’ template to include a minimal .gitignore file. I've added the template. Just wanted to ask before I push On Thu, Mar 9, 2023, 20:00 James Bennett wrote: > On Thu, Mar 9, 2023 at 10:27 AM 'Adam Johnson' via Django developers > (Contributions

Add a minimal Gitignore

I think it will be a little bit helpful to add a very minimal .gitignore file to the django project. Maybe one that just ignores the environments, test files -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)"

Warning in documentation about filtering queryset in ClassBasedViews

this query filter by the date the server was started. So the solution is to use a dynamic filtering. Could be a good idea to include some warning about this in the documentation? Thanks, Daniel -- You received this message because you are subscribed to the Google Groups "Django devel

Re: What happens if a Fellow has a holiday?

Enjoy your week off! El jueves, 4 de junio de 2020, 12:47:57 (UTC+2), Carlton Gibson escribió: > > Hi all. > > Short answer is we don't really know, since we never take holidays.  > > I though am having a much needed week off from tomorrow, to be back on the > 16th. > > Mariusz will need

#30646 - close_if_unusable_or_obsolete fails to close unusable connections

ere would correspond to what I've proposed in the ticket and the associated PR. Kind regards, Daniel -- 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

Should django.contrib.auth.authenticate check is_active?

This is essentially an RFC. I've become more familiar with Django's authentication backend system lately, and something has stood out to me that I'd like to draw attention to. A new site built with Django is likely to use the default ModelBackend, which includes a user_can_authenticate

Re: Proposal to re-open #27017 (updating only dirty fields in save())

hs and wrap them in select_for_update to ensure the data doesn't get into an inconsistent state? On Monday, January 28, 2019 at 8:00:21 AM UTC-6, Daniel Tao wrote: > > Hi! > > This is my first post on this list. I recently left a comment on #27017 > <https://code.django

Proposal to re-open #27017 (updating only dirty fields in save())

Hi! This is my first post on this list. I recently left a comment on #27017 requesting to re-open the topic of only saving dirty fields in save(). Tim Graham helpfully directed to #4102 and

Re: Idea: Allow queryset.get() and queryset.filter() to accept a positional argument for implicit primary key filtering

This is something I've also experimented while working with a shell, I often mislead the .get(pk), with .get(pk=pk), but only at the shell, not in the views or other places (not sure why). For that, I'm -1 to to include it in the core, and possible the best place is a third package app like

Re: Django and Cython

ou can drop in > for up to 3.5.x Python versions. > > On Wednesday, August 1, 2018 at 5:21:38 PM UTC-4, Daniel Anechitoaie wrote: >> >> I'm looking at frameworks like https://vibora.io/ that make use of >> Cython to greatly improve the performance and I'm just wonderin

Django and Cython

I'm looking at frameworks like https://vibora.io/ that make use of Cython to greatly improve the performance and I'm just wondering if something like this would work with Django? Was there any discussion (taken into consideration) about using Cython to boost the performance of certain aspects

Re: PEP 484 type hinting in Django

ot randomly you need to do it bottom up (covering basic abstractions first). So the place to start is probable the parts of django that change less and are more solid foundations (in my case I started with requests, views and URL resolvers, etc) -- Daniel F. Moisset - UK Countr

Re: PEP 484 type hinting in Django

ing emails from it, send an > email to django-developers+unsubscr...@googlegroups.com. > To post to this group, send email to django-developers@googlegroups.com. > Visit this group at https://groups.google.com/group/django-developers. > To view this discussion on the web visit https://gr

binding framework third-party package for Channels 2

Hi, I'm not sure where to ask this question because it doesn't seem to fit anywhere but I hope this group is the best place. The Channels 2.0 docs say that the binding framework will appear in a third-party

Re: Proposal: Make CSRF token validation for other HTTP Methods (PUT, PATCH, DELETE) The Same as POST

Thanks, Tom Christie. Now i understand why. On Saturday, May 6, 2017 at 11:49:57 PM UTC+1, Osaetin Daniel wrote: > > I came across this issue, because i'm building a SPA with Vue and Django > Rest Framework as the backend. > > I'm using SessionAuthentication Which requires that

Proposal: Make CSRF token validation for other HTTP Methods (PUT, PATCH, DELETE) The Same as POST

I came across this issue, because i'm building a SPA with Vue and Django Rest Framework as the backend. I'm using SessionAuthentication Which requires that the CSRF token must be sent along with the data for HTTP methods that Change State on the Server if not the request would be flagged as

Re: Adding Support for a Float32 Field

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 thinking? I might as well justify my use case a little more: I am building a

Adding Support for a Float32 Field

". Any thoughts? I could write up a patch for this. Best, Daniel --- https://github.com/ddasilva -- 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

Re: Provide a simpler way to default runserver IP/port to 0.0.0.0:8000

I'd find this really helpful right now. Solution 1, overriding the default in a settings file is the easiest solution to understand and the fastest to set up, against 2 and 3 standalone. Solution 2 comes for free with Solution 1 - a user can read from environment variables via settings files

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

t;> -- > 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

Re: GeoDjango OffdbRasterField

ization issues depending on the type of network > mapping used. > > If this addition is too problematic to be added in core, I could just > isolate the code and release it as a plugin, with some documentation > about the limits of the approach. > > On Thursday, December 29, 20

Re: GeoDjango OffdbRasterField

/raster_file_field An ideal solution would be a mixture of the two, but I am not sure if PostGIS can handle remote storages. On Tuesday, December 20, 2016 at 4:33:21 PM UTC, Tim Graham wrote: > > Daniel Wiesmann did all the work for RasterField. I'm not sure if he > follows this list bu

Re: Javascript Templating Package

Hi Nick, I'm not sure what kind of generation are you suggesting. What I've used a couple of times is creating a template tag to convert a json-like data structure in the context to a javascript object, so in the template I have something like this in a

Re: PEP 484 type hinting in Django

than other python stuff (like the requests example Florian mentioned Feel free to comment and follow-up details on the project issue tracker. I posted this update here in case it helps in the future to follow the discussion about adding inline annotations. Best, D. On 20 September 2016 a

Re: PEP 484 type hinting in Django

ers/5bf15a4b-8360-4ee0-a985- > 01f42e7e27fd%40googlegroups.com > <https://groups.google.com/d/msgid/django-developers/5bf15a4b-8360-4ee0-a985-01f42e7e27fd%40googlegroups.com?utm_medium=email_source=footer> > . > > For more options, visit https://groups.google.com/d/optout. >

Re: PEP 484 type hinting in Django

<https://groups.google.com/d/msgid/django-developers/ac0102f7-9106-40dd-be62-17fcb30c0f1f%40googlegroups.com?utm_medium=email_source=footer> > . > > For more options, visit https://groups.google.com/d/optout. > -- Daniel F. Moisset - UK Country Manager www.machinalis.com Skyp

Re: PEP 484 type hinting in Django

- > 65944d30ccf5%40googlegroups.com > <https://groups.google.com/d/msgid/django-developers/b5dcb500-4706-407f-8e42-65944d30ccf5%40googlegroups.com?utm_medium=email_source=footer> > . > > For more options, visit https://groups.google.com/d/optout. > -- Daniel F. Moisset - UK Co

Re: PEP 484 type hinting in Django

zFXjU%3D2-isw%40mail.gmail.com?utm_medium=email_source=footer> > . > For more options, visit https://groups.google.com/d/optout. > -- Daniel F. Moisset - UK Country Manager www.machinalis.com Skype: @dmoisset -- You received this message because you are subscribed to the Google Groups &

Re: Collectstatic and determine which files need to be updated by comparing their checksum

; > On Thursday, April 14, 2016 at 1:16:39 PM UTC-4, bliy...@rentlytics.com > wrote: >> >> This makes a lot of sense to me. >> >> On Tuesday, April 12, 2016 at 9:07:51 AM UTC-7, Daniel Blasco wrote: >>> >>> Hi, >>> >>> I posted

Collectstatic and determine which files need to be updated by comparing their checksum

Hi, I posted this in django-users but I think that it goes better here. I'm using django-storages to upload my static files to Amazon S3 and I'm serving my application from Heroku. In my local development, when I run collectstatic for a second time just after the first one, no files are

Re: Django template 'if ... is' feature design

The *is* comparator is quite error prone for misunderstanding it (as we could observed some times) maybe it worths to link python docs about it: https://docs.python.org/3.5/reference/expressions.html#is Well, that Python docs doesn't say to much (lack of examples) >>> a = 'pub' >>> b =

Re: Should DecimalField have special rounding to make float assignments match string assignments?

this group at https://groups.google.com/group/django-developers. > To view this discussion on the web visit > https://groups.google.com/d/msgid/django-developers/07CD3A6B-EC86-42CC-A6BC-03D74112A0C3%40polytechnique.org > <https://groups.google.com/d/msgid/django-developers/07CD3A6B-EC86-42CC-A6BC-03D7

Make STATIC_URL context variable aware of backing storage with staticfiles

I've always used the STATIC_URL context processor variable in templates and didn't have trouble with it up until a few days ago when a customer required to use the STATICFILES_STORAGE. I then realized I would need to change all the {{STATIC_URL}} template references to use a {% static %} tag

Re: Django Integration

Hello, There are more information about the project in the doc page: https://channels.readthedocs.org/en/latest/ El sábado, 5 de marzo de 2016, 1:16:31 (UTC+1), Chad Paulson escribió: > > I was happy to read that part of the Mozilla Open Source Support program > funding that was recently

Re: [Discussion] Legacy documentation / Boken docs Django v1.2

IMHO We should keep the older version of docs somewhere, ReadTheDocs it's fine. But we can't only remove them. We may notice the users instead of returning a simple 404. There are a lot of people still using those versions. To keep happy search engines, we should give a 301 to somewhere, not

Spatial lookups for RasterField

or the api that shoudl be considered? - If not, which of the two approaches would be better? Thanks, Daniel -- 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 r

Re: add prefered/default protocol in the sites framework #26079

Hi, I think the same in the case of: > >1. It would make data less portable between development (where SSL is >often not in use) and production. > > So maybe a settings option could work. El miércoles, 13 de enero de 2016, 14:21:14 (UTC+1), Eric Rouleau escribió: > > Hi > > I've

Re: FYI: pip install django is failing

There was a issue with pypi from some locations, although the status page doesn't say anything about it. https://status.python.org/ El viernes, 25 de diciembre de 2015, 13:03:05 (UTC+1), john...@gmail.com escribió: > > >pip install django --upgrade > Collecting

Re: MOSS Award to Django

Hi, Just saying congrats to people involved and the community. Great step for Django! El viernes, 11 de diciembre de 2015, 19:19:00 (UTC+1), Andrew Godwin escribió: > > Hi everyone, > > For those who haven't seen, Mozilla has awarded $150,000 to Django for > work on Channels and

Ticket 2273: django.contrib.auth.models.User: username is case-sensitive

Following the end of https://code.djangoproject.com/ticket/2273 over a year ago, could this be reconsidered please? By using username__iexact when checking for uniqueness for new usernames, this wouldn't affect any usernames that already exist, and it's then up to the administrators to decide

Re: Future of the development server's auto-reloading

t; To post to this group, send email to django-developers@googlegroups.com. > Visit this group at http://groups.google.com/group/django-developers. > To view this discussion on the web visit > https://groups.google.com/d/msgid/django-developers/8E08AB59-2450-40D5-A52B-C8803DA39D5F%40polytechni

Ticket #25236: Remove ifequal from the template language

medium ground would be to remove it from the documentation. Any comments? Regards, Daniel Roy Greenfeld -- 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

Re: MigrationTestCase

='email') assert user.profile.pk == old_profile.pk == profile.pk assert profile.user.email == 'email' assert profile.user.first_name == 'firstname' assert profile.user.last_name == 'lastname' https://gist.github.com/blueyed/4fb0a807104551f103e6 Cheers, Daniel. Am Donnerstag

Re: Is improving Django's communication with Oracle databases on the roadmap?

, I'd be thrilled. On Thursday, May 14, 2015 at 9:02:52 PM UTC-4, Josh Smeaton wrote: > > Hi Daniel, > > Can you provide links to the patches and discussion you're referring to? > It'll be easier to provide some feedback if we have the detail in front of > us. > > I'm all f

Is improving Django's communication with Oracle databases on the roadmap?

, then I'm sure we can just keep our own, patched version of django. I would be stoked for there to be a main branch solution, though. Thanks! Daniel -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)&q

Re: Gsoc 2015: SQLAlchemy / NoSQL integration

Hi Abhishek, I am in the process of updating the mailer in the next month. I will let you know when this has been done. Regards, Daniel 2015-03-16 11:53 GMT+01:00 Abhishek Kumar <abhi170...@gmail.com>: > Hi, > > I was trying to run the django-mailer > <https://github.com/

Re: Gsoc 2015: SQLAlchemy / NoSQL integration

Hi Abhishek, I am the GSOC 2014 student who refactored the Meta API, please contact me if you need any details on my work, or if you want to know more about implementation and/or design of the new Meta API. You can also find me on IRC as pirosb3. Good luck! Daniel 2015-03-02 1:32 GMT+01:00

Re: User.username max_length 254

> > I'd bet an extremely large portion of those users don't absolutely have to > have an increased username field. They've gone this long without it. > They (we) have gone this long, not because we didn't need it, but because we didn't think of it in the very beginning, and after that it was

Re: User.username max_length 254

dea? :( On Wednesday, February 11, 2015 at 3:27:35 AM UTC-5, Daniel Hawkins wrote: > > Yes please! Since contrib.auth.models.User.email is an EmailField, that > change will require everyone to run a migration, right? Then we might as > well change the character limit on the username field

Re: User.username max_length 254

Yes please! Since contrib.auth.models.User.email is an EmailField, that change will require everyone to run a migration, right? Then we might as well change the character limit on the username field at the same time, no? And any other defaults that might be less-than-reasonable? I was going

Re: Last call: Meta API (GSoC 2014/PR 3114) is ready for commit

the brainstorming that happened over the sprints as well as the very technical talks have greatly helped this project grow. This is not a farewell, I plan on sticking around (as I am sure tickets will be assigned to me very soon!) so feel free to blame me on IRC or Twitter (PirosB3). Daniel Pyrathon

Are rasters on the GeoDjango roadmap?

something that is already underway. Does anyone know about the state of rasters in GeoDjango and/or if its on the roadmap for future development? Thanks, Daniel -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)&q

Re: The greatest proposal yet: rename this damn group

Hi, I think that changing the name the community on google will create many broken links, this will be a huge loss. What we can do instead, is create 2 domains (or subdomains) such as core-development.djangoproject.com and community.djangoproject.com that will serve as the official URLs to

Re: [RFC] Python 3 and MySQL

Aside from the technical issues, there are the licensing issues. The Django community strongly prefers BSD-style licensing and both mysqldb and MySQL Connector/Python use GPL licenses. For an e-mail thread which addresses these GPL issues, see

Documentation tool

Hello, I'm looking for a documentation tool for my django project. Something like JavaDoc or PHPDoc, to be able to generate a HTML|PDF with the models, views, urls.. I've used sphinx to non-related Django projects, but I've never tried with Django Any suggest? Thanks. Chimeno -- You

Re: GSoC Meta refactor: Bikeshedding time!!

Hi Shai, Thanks for the comments! On Wednesday, August 20, 2014 8:21:36 PM UTC+2, Shai Berger wrote: > > On Wednesday 20 August 2014 10:29:49 Anssi Kääriäinen wrote: > > On Wednesday, August 20, 2014 11:19:33 AM UTC+3, Russell Keith-Magee > wrote: > > > > > > This yields the following formal

Re: GSoC Meta refactor: Bikeshedding time!!

Hi Colin, Thanks for getting back On Monday, August 18, 2014 4:58:20 PM UTC+2, Collin Anderson wrote: > > The goal is to have "API methods that let you introspect the fields and > relations that exist on a model", right? Why go though the trouble of > finding the one specific type for each

Re: GSoC Meta refactor: Bikeshedding time!!

Hi Shai, Thanks for getting back, so.. On Monday, August 18, 2014 1:44:49 PM UTC+2, Shai Berger wrote: > > Hi again, > > Below, ">D" are quotations from Daniel's message I'm replying to, and > ">R" are from Russell's message that opened this thread. > > >D *Regarding FileField* > > It took

Re: GSoC Meta refactor: Bikeshedding time!!

Hi Anssi With regards to Michal Petrucha's changes, I have the feeling you are correct. A solution to this could be to provide a cached property called **foreign_keys** that will disguise the actual identity of a ForeignKey. Once the Michael's changes are introduced, we could start deprecating

Re: GSoC Meta refactor: Bikeshedding time!!

Hi All, First of all, thanks Russell for bringing this discussion up. *Regarding get_fields complication* Throughout the development of this project, I have realised that 90% of the API usage inside and outside of Django can rely entirely on 4 or 5 cached properties. The most used API calls

Re: Proposal new Django Admin css style

Thanks for the mention, but I haven't had time to work or maintain that for months. I'm not sure how it works with the upcoming Django 1.7. Also, for the sake of simplicity, the default skin for it is bootstrap 3. Any CSS in there is per skin, and probably doesn't belong in this discussion.

Re: [GSOC] Weekly update

, Daniel On Saturday, August 9, 2014 4:10:31 PM UTC+2, Daniel Pyrathon wrote: > > Hi All, > > This week I have been working on mainly 3 tasks: > > *- Formalizing the PR* > 2 days were dedicated on fixing all the small issues on the PR. I am now > ready for another r

Re: Requiring GitHub login for actions on Trac

On Sunday, August 10, 2014 2:37:01 AM UTC-7, Aymeric Augustin wrote: Using GitHub for auth a giant +1 from me. For me, this ranks up with the SVN to Github move as a: "Why hasn't this been done already?" Daniel Greenfeld co-author Two Scoops of Django -- You received this messa

Re: [GSOC] Weekly update

> documentation examples etc...) > > All the best & keep up the great work, > > Tom > > > On Wednesday, 6 August 2014 01:33:53 UTC+1, Russell Keith-Magee wrote: >> >> >> On Tue, Aug 5, 2014 at 12:54 AM, Łukasz Rekucki <lrek...@gmail.com> >

Re: [GSOC] Weekly update

. It overrides a tuple (so it should be performant) and is still conceptually a list. Is this clear? please let me know if you want me to explain further our decision on this. Daniel On Monday, August 4, 2014 4:54:45 PM UTC+2, Łukasz Rekucki wrote: > > On 4 August 2014 16:14, Daniel Pyratho

State of concrete fields

PI (https://groups.google.com/forum/#!topic/django-developers/XfMUjK59Sls) it would be great to reduce complexity even more by removing the entire term "concrete fields". Thanks, Daniel Pyrathon -- You received this message because you are subscribed to the Google Groups "Django develope

Re: [GSOC] Weekly update

Hi All, This has been resolved by using the ImmutableList datastructure https://github.com/PirosB3/django/blob/soc2014_meta_refactor_upgrade_flags_get_field_tree/django/db/models/options.py#L629 On Monday, August 4, 2014 2:44:38 PM UTC+2, Collin Anderson wrote: > > if we do really need a list,

Re: [GSOC] Weekly update

Hi Aymeric, Thanks for writing back On Sunday, August 3, 2014 4:24:27 PM UTC+2, Aymeric Augustin wrote: > > On 3 août 2014, at 15:11, Daniel Pyrathon <pir...@gmail.com > > wrote: > > *1) get_fields should return a list instead of a tuple* > Previously, get_fields would

Re: [GSOC] Weekly update

> > On Sat, Jul 19, 2014 at 2:38 AM, Raffaele Salmaso <raff...@salmaso.org > > wrote: > >> On Fri, Jul 18, 2014 at 7:32 PM, Daniel Pyrathon <pir...@gmail.com >> > wrote: >> >>> *- Started on my GMail Store* >>> (...) >>> >> Pirosb

Re: Pull django-registration into contrib?

of django.contrib.auth. --Daniel Greenfeld On Friday, August 1, 2014 9:17:30 AM UTC-7, Collin Anderson wrote: > > It seems to me, in any case, the first step is to get django-registration > actively maintained again. James Bennett is welcoming proposals of people > to take over maintenance of

Re: [GSoC] Update of my work

Nice work! amazing as usual Anubhav ;) 2014-07-27 9:24 GMT+02:00 anubhav joshi : > Hi all > > My project "*Improving error reporting & Fixing up the related issues" > *proposal > can be seen here: GSoC Proposal > >

Fields terminology for official Options API

bjects waiting on the other end. I also like the symmetry between "m2m" and "reverse_m2m". - Django isn't always consistent (and sometime actually wrong) in naming relations, especially indjango/db/models/fields/related.py. Now that we start docume

Re: [GSOC] Weekly update

oing a lightning talk on the new Options API, or the GMail store depending on progress. For anything, as usual, let me know Daniel Python On Friday, July 11, 2014 4:59:09 PM UTC+2, Daniel Pyrathon wrote: > > Hi All, > > Following this week's work. I have made progress in optimisat

Re: [GSOC] Weekly update

For anything, as usual, just let me know :) Daniel On Saturday, July 5, 2014 12:11:07 PM UTC+2, Josh Smeaton wrote: > > Excellent work, well done. I have a couple of questions/ideas though. > > 1. The use of bit flags irks me. Would it be possible just to use numerous > ke

Re: [GSOC] Weekly update

Hi Curtis, Of course! I will be happy to open a document with my performance tuning experience. Said this, I am very far away from being a "performance master" and I am still looking at places where my code can improve. It would be nice if it was a wiki page, where everyone can share and

Re: [GSOC] Weekly update

Hi Josh, Thanks to your advice. On Saturday, July 5, 2014 12:11:07 PM UTC+2, Josh Smeaton wrote: > > Excellent work, well done. I have a couple of questions/ideas though. > > 1. The use of bit flags irks me. Would it be possible just to use numerous > keyword arguments to the new get_fields ? >

Re: [GSOC] Weekly update

RE work in progress code The main functions to optimize are get_new_fields, get_new_field, they are found here: https://github.com/PirosB3/django/blob/a92c37f0cad6bdd7a3b24ef235c81a7dab6bee72/django/db/models/options.py On Sunday, June 22, 2014 11:49:05 AM UTC+2, Daniel Pyrathon wrote

Re: [GSOC] Weekly update

- Small optimizations (BIG work in progress) If you have any suggestions please let me know! Dan On Sunday, June 22, 2014 2:14:56 AM UTC+2, Curtis Maloney wrote: > > Is there somewhere I can look at your work in progress code? > > > On 21 June 2014 19:57, Daniel Pyrathon &l

Re: [GSOC] Weekly update

ou can make it work. > > Just check that you don’t "overload" fields, by storing in field objects > information that doesn’t belong there. > > -- > Aymeric. > > > > On 13 juin 2014, at 19:53, Daniel Pyrathon <pir...@gmail.com > > wrote: > >

[GSOC] model/options.py test suite released

and advice, so if you would like to say something, just write it here or on the PR. Regards, Daniel Pyrathon -- You received this message because you are subscribed to the Google Groups "Django developers" group. To unsubscribe from this group and stop receiving emails from it, sen

Re: [GSOC] Weekly update

l, let me know Dan On Friday, June 6, 2014 7:03:36 PM UTC+2, Daniel Pyrathon wrote: > > Hi All, > > Based on the work done last week, this week I have worked on the following: > > *1) Covered the current _meta implementation of unittests* > The current Options is not covered b

Re: Loading fixtures once for each TestCase to improve running time

A long time ago (django 1.3 era) I wrote a library (no need to change django) to do exactly this, using savepoints to rollback: https://github.com/machinalis/django-fasttest It worked pretty well for a large project and provided a large speedup (i think it was about 5x) on a large test suite. But

Re: Support for function application in ORDER BY

> > On Mon, Jun 9, 2014 at 4:00 PM, Daniel Moisset <dmois...@machinalis.com> > wrote: > >> I see everyone trying to put the direction (ascending vs decending) >> inside the expression, while it's actually a property of the ordering >> clause. Woul

Re: Support for function application in ORDER BY

I see everyone trying to put the direction (ascending vs decending) inside the expression, while it's actually a property of the ordering clause. Wouldn't it make more sense and avoid ambiguities to do: qs.order_by(..., descending=True) ? Then you can add functions (and even a __neg__ operator

Re: [GSOC] Weekly update

mplementation as is for personal use only For any questions, let me know! Dan On Sunday, June 1, 2014 6:10:53 PM UTC+2, Daniel Pyrathon wrote: > > Hi All, > > An update on my side, some interesting work has happened this week: me and > Russell have decided to start on the i

Re: [GSOC] Weekly update

a lot more of the current implementation. We are testing each combination of fields and options together. My current implementation is visible here: https://github.com/PirosB3/django/compare/soc2014_meta_refactor For any questions or suggestions, let me know. Daniel Pyrathon On Monday,

Re: [GSOC] Weekly update

Hi All, Just to make you know, I have put up the current _meta API documentation here: http://162.219.6.191:8000/ref/models/meta.html?highlight=_meta As always, feel free to ask questions. Daniel On Monday, May 26, 2014 1:26:27 AM UTC+2, Daniel Pyrathon wrote: > > Hi Josh, > >

Re: [GSOC] Weekly update

will be approved. My current proposal (https://gist.github.com/PirosB3/371704ed40ed093d5a82) and it will be discussed tomorrow with Russell. I will post as soon as I have updates. Daniel Pyrathon On Saturday, May 24, 2014 10:37:49 AM UTC+2, Josh Smeaton wrote: > > Hi Daniel, > &g

Re: [GSOC] Weekly update

Hi Chris, Oh sorry about that! big typo over there. Modifying the gist. Thanks, Daniel Pyrathon On Saturday, May 24, 2014 7:44:15 AM UTC+2, Chris Beaven wrote: > > Hi Daniel, > > The proposal looks interesting - I've only skimmed it so far but one > question: you mention

Re: [GSOC] Weekly update

appreciated. Hi from Pycon IT! Daniel Pyrathon On Tuesday, May 20, 2014 3:25:45 PM UTC+2, Josh Smeaton wrote: > > Best of luck! > > On Tuesday, 20 May 2014 03:56:06 UTC+10, Daniel Pyrathon wrote: >> >> Hi All, >> >> Today I will be starting my weekly updates on

[GSOC] Weekly update

progress feel free to contact me! The branch I am currently working on is https://github.com/PirosB3/django/tree/meta_documentation Regards, Daniel Pyrathon -- You received this message because you are subscribed to the Google Groups "Django developers" group. To unsubscribe from

Re: [GSOC] Hi from Daniel!

a shout Regards, Daniel Pyrathon On Thursday, April 24, 2014 1:29:03 AM UTC+1, Ramiro Morales wrote: > > Hi Daniel, > > On Wed, Apr 23, 2014 at 4:23 PM, Daniel Pyrathon > <pir...@gmail.com> > wrote: > > Hi, > > > > My name is Daniel, and this summe

[GSOC] Hi from Daniel!

Hi, My name is Daniel, and this summer I will be working on formalising Meta. This will allow developers to build custom implementations of Meta and deploy them into their Django project. In case you missed my proposal, you can have a look at it here: https://docs.google.com/document/d

Re: Revisiting multiline tags

Hmm, that does seem like a great idea! On Thu, Apr 3, 2014 at 10:17 AM, dude wrote: > Very good idea i think! > > Many people love format source codes to be beauty. But they can’t because > django templates does’t support multiline tags. > > > 03 апр. 2014 г., в 21:13,

Re: [GSOC] Introduction and task proposal

Hi Josh, Sorry for getting back now. I have just finished my exam session, so I will be trying out the djangocore-box VM. Regards, Daniel Pyrathon On Thursday, March 27, 2014 5:45:36 AM UTC+1, Josh Smeaton wrote: > > If you haven't already got all your databases installed o

Re: [GSOC] Introduction and task proposal

Hi all, It's been a while since I submitted my GSOC proposal. Although I am currently under exams, is there anything you would recommend me to do at this point (other than hope that my proposal is successful)? Thanks, Daniel Pyrathon On Thursday, March 20, 2014 6:05:40 AM UTC, Russell Keith

Re: [GSOC] Introduction and task proposal

Hi! Thanks for all the comments yesterday. They really helped me make the proposal stronger. I have changed to proposal to reflect the changes. Would anyone like to have a look and, possibly, comment more?

  1   2   3   4   >