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 : > Hi, > > I was trying to run the django-mailer >

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

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: 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: [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: [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: [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

Hi All, I am currently working on the new Options API (https://github.com/django/django/pull/2894). The Options API is at the core of Django, it enables introspection of Django Models with the rest of the system. This enables lookups, queries, forms, admin to understand the capabilities of

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

Hi All, Following this week's work. I have made progress in optimisation and design of the API. I have opened a wiki page that contains all: - Main concepts - Decision process - Benchmarks - API designs - How you can help! Please see attached: https://code.djangoproject.com/wiki/new_meta_api

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: [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!

only contributed a few patches. 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, send an email to django-developers+unsubscr...@google

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?

Re: [GSOC] Introduction and task proposal

stores that work well with Django https://docs.google.com/document/d/1yp2_skqkxyrc0egdRv6ofnRGCI9nmvxDFBkCXgy0Jwo/edit# Kind regards, Daniel On Tuesday, March 11, 2014 10:48:43 PM UTC, Daniel Pyrathon wrote: > > Hi Russel, > > Sorry for getting back now (I

Re: [GSOC] Introduction and task proposal

Hi Russel, Sorry for getting back now (I did not have notifications set up!). Thank you very much for the suggestions, I will have a look at models/options.py right away. Regards, Daniel Pyrathon On Thursday, March 6, 2014 12:03:04 AM UTC, Russell Keith-Magee wrote: > > Hi Daniel, >

[GSOC] Introduction and task proposal

Hi, My name is Daniel Pyrathon. I am currently a third year BSc student in Computer Science at the University of Plymouth. I love programming and I have always been active in the Open Source community (especially Python). In the past years I have written lots of Python, Javascript, Ruby