from:"Daniel Pyrathon"

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

2015-01-07 Thread Daniel Pyrathon

Hi all,

My project has just landed in master, since last night (EU time).

I just wanted to say THANK YOU for everyone that helped me review and fix 
my project. I would have never managed to reach such maturity by myself, 
and one of the best things is that I really learned a lot by contributing 
to Django (Yes! this is also a pitch to any potential SoC applicants for 
next year).

First of all, I want to thank my mentor (Russell) for his *enormous* 
patience and for all the time he dedicated to the project.
Secondly, I want to thank all the community and everyone who got involved 
in my pull request by submitting comments and/or contacting me directly for 
suggestions and advice, your suggestions have greatly shaped the final 
release and have also helped me improve as a developer.
Last but not least, I want to (re)thank the people from Django Under the 
Hood because 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

On Monday, January 5, 2015 11:11:13 AM UTC+1, Tom Christie wrote:
>
> Wonderful - great work Daniel and thanks to everyone else for their hard 
> work on review & guidance.
> Lovely stuff.
>
>   Tom
>
> On Monday, 5 January 2015 05:12:41 UTC, Russell Keith-Magee wrote:
>>
>> Hi all,
>>
>> Following up on my pre-Christmas email - I believe that PR 3114 - the 
>> formalisation of _meta - is now ready to land.
>>
>> https://github.com/django/django/pull/3114
>>
>> The code has received a detailed review by several members of the core 
>> team, including Tim, Carl, Collin, and myself; we've had review notes from 
>> many others. The documentation has also been reviewed. The issues raised by 
>> those code and documentation reviews have all (to the best of my knowledge) 
>> been addressed.
>>
>> Other than last-minute cleanups (e.g., PEP8 compliance, -Wall checks 
>> etc), and the conclusion of one discussion about how to express one 
>> particular set of relationships in code, I believe the branch is ready to 
>> land.
>>
>> Unless there are objections, my intention is to land this patch later 
>> this week (around Wednesday/Thursday UTC). If anyone has any objections, 
>> speak now, etc etc.
>>
>> Once again, a huge thanks to Daniel for his great work over the summer 
>> (and continued work into the winter as we refined the patch for trunk), and 
>> to everyone else who has contributed to reviewing his work.
>>
>> Yours,
>> Russ Magee %-)
>>
>>

-- 
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.
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/aad6a087-d142-4eae-a054-c96133256ae4%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Gsoc 2015: SQLAlchemy / NoSQL integration

2015-03-08 Thread Daniel Pyrathon

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 Russell Keith-Magee :

>
> Hi Abhishek,
>
> On Sun, Mar 1, 2015 at 1:16 PM, Abhishek Kumar 
> wrote:
>
>> Hi,
>>
>> I am Abhishek and am interested in the project titled "SQLAlchemy / NoSQL
>> integration". I am good at data-structures and algorithms and have
>> worked with C,C++, PHP, Python,C#, Javascript and Mysql. I have an
>> internship experience at Microsoft, India.
>>
>> I have some questions which will help me in understanding the tasks
>> involved in this project better.
>>
>> 1)What was the formalised meta that came out of the 2014 soc project..?
>> Where to find the details of it..?
>>
>
> The new Meta interface is documented as part of Django 1.8:
>
> https://docs.djangoproject.com/en/1.8/ref/models/meta/
>
>
>> 2) I am new to Django. So i would be learning about it. Please let me
>> know what things i should focus more on w.r.t this project.
>>
>
> The most important part is probably Django's query language - you need to
> get comfortable with how you construct queries, and what those queries
> "mean" - both in the sense of the SQL they generate, and the underlying
> "idea" that the query is trying to capture.
>
> It would also be worth becoming familiar with Django's Admin interface -
> especially with regard to what queries it generates, and when.
>
>
>> 3) Before beginning to work for the project, what things i need to do to
>> make me eligible for it..? Bug fixes..?
>>
>
> The only hard requirement is to write a project proposal. However, if you
> get involved with the community, that may improve your chances, as we will
> get a chance to know you; if there are some details lacking in your
> proposal, we might be willing to overlook them if we have a better
> understanding of who you are, and how you interact with the community.
>
> Yours,
> Russ Magee %-)
>
> --
> 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.
> 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/CAJxq848ra-rbFzLZgktfMaU%3D%3DuYQstDSu1NFjD-XwG374401%2BQ%40mail.gmail.com
> 
> .
>
> For more options, visit https://groups.google.com/d/optout.
>



-- 
*

PirosB3

https://github.com/PirosB3

-- 
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.
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/CAOmo0o93%2B3KwAxBNW7zOnE0AeQ0t088Q%2BP_BUip84YD2ZLJf_A%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Gsoc 2015: SQLAlchemy / NoSQL integration

2015-03-21 Thread Daniel Pyrathon

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
>  written by Daniel. On doing
> migrate or runserver i am getting the following error:
>
> django.core.management.base.SystemCheckError: SystemCheckError: System
> check identified some issues:
>
> ERRORS:
> : (admin.E106) The value of
> 'mailchecker.admin.MessageInline.model' must be a Model.
>
> Any suggestions on resolving it..?
>
>
>
>
> On Monday, 2 March 2015 05:03:59 UTC+5:30, Abhishek Kumar wrote:
>>
>> Hi,
>>
>> I am Abhishek and am interested in the project titled "SQLAlchemy / NoSQL
>> integration". I am good at data-structures and algorithms and have
>> worked with C,C++, PHP, Python,C#, Javascript and Mysql. I have an
>> internship experience at Microsoft, India.
>>
>> I have some questions which will help me in understanding the tasks
>> involved in this project better.
>>
>> 1)What was the formalised meta that came out of the 2014 soc project..?
>> Where to find the details of it..?
>> 2) I am new to Django. So i would be learning about it. Please let me
>> know what things i should focus more on w.r.t this project.
>> 3) Before beginning to work for the project, what things i need to do to
>> make me eligible for it..? Bug fixes..?
>>
>> I will choose the particular  Nosql database later.
>>
>> Thanks,
>> Abhishek Kumar
>> CSE, IIIT Hyderabad
>> India
>>
>  --
> 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.
> 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/c0c29b70-c849-464b-b34f-a1c02cb3e4bf%40googlegroups.com
> 
> .
>
> For more options, visit https://groups.google.com/d/optout.
>



-- 
*

PirosB3

https://github.com/PirosB3

-- 
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.
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/CAOmo0o9iG4LVsru0kYSR9-W7C_deqS7%3D8UojV8gsfyyDUVvtNg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[GSOC] Introduction and task proposal

2014-03-05 Thread Daniel Pyrathon

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, Java, and I am currently using C++ for many
university projects. I have attended the last 3 EuroPython conferences and
I have been a staff member of the conference for the last 2 years.

I am currently looking for a way to contribute to Django. Working on Django
would increase my knowledge of the framework as well as let me share my own
experience.

Reading the ideas list I found 2 of them that are very interesting for me,
and so the reason behind this post is not only to present myself but also
to discuss their feasibility.

Formalizing the Meta object

This task is very challenging because it digs in the internals of Django. I
feel that I could learn a lot from it because I am very committed to
refactoring and write most of my code in TDD. I have also experience with
backwards compatibility.

Do you have any resources (code) I should read to get up to date and to
understand better how it is currently implemented?

Improved error reporting

The idea of making people’s lives better by improving error messages is
fundamental. There would be a lot to discuss: what type of imports would we
want to mask? I have read BetterErrorMessages and would be happy to get
started soon. My idea behind this task would be to expand on this ticket:
what would be great is to add a web console with live REPL support, similar
to what Werkzeug debugger does. This could be a great starting point and
would lead to a better use of Django.

Said this, I have to be very honest. I have never contributed to Django up
till now and I want to hear your feedback on which proposal would suit me
best. However I learn a lot through experience and I am attracted by new
and challenging tasks.
Also, it would be nice if I could have some suggestions on what to read and
if there are some specific parts of the code I should be directed to.

Please let me know,
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...@googlegroups.com.
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/0b1cc1e7-063a-48ea-9c92-eaa0344d396d%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [GSOC] Introduction and task proposal

2014-03-11 Thread Daniel Pyrathon

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,
>
> On Wed, Mar 5, 2014 at 11:48 PM, Daniel Pyrathon 
> 
> > wrote:
>
>> 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, Java, and I am currently using C++ for many 
>> university projects. I have attended the last 3 EuroPython conferences and 
>> I have been a staff member of the conference for the last 2 years.
>>
>> I am currently looking for a way to contribute to Django. Working on 
>> Django would increase my knowledge of the framework as well as let me share 
>> my own experience.
>>
>> Reading the ideas list I found 2 of them that are very interesting for 
>> me, and so the reason behind this post is not only to present myself but 
>> also to discuss their feasibility.
>>
>> Formalizing the Meta object
>>
>> This task is very challenging because it digs in the internals of Django. 
>> I feel that I could learn a lot from it because I am very committed to 
>> refactoring and write most of my code in TDD. I have also experience with 
>> backwards compatibility. 
>>
>> Do you have any resources (code) I should read to get up to date and to 
>> understand better how it is currently implemented?
>>
>
> Unfortunately not; at least, not other than just trying to untangle the 
> mess that is django/db/models/options.py and the things that depend on it 
> (ModelForms and Admin in particular). This project really is the very model 
> of untangling a ball of string. The reason it's listed as a potential 
> project is specifically *because* there are no resources we can point you 
> at.
>
> If, after looking at the code, you feel it's a little "thin" for 12 weeks, 
> one way to bulk it out is to build a proof of concept alternate 
> implementation of Meta. Aside from the "it would be good to document this" 
> aspect, the practical reason for wanting to formalise Meta is that it would 
> allow people to build duck-typed implementations of Meta. If you can build 
> an alternate implementation of the Meta interface, then you should be able 
> to deploy your "duck" into a Django project and build a ModelForm, or 
> browse it in Admin.
>
> So, for example, you could build a wrapper around a NoSQL store, or around 
> an LDAP or email store, that *looked* like a Django model from the outside. 
> This means you could view your NoSQL data, or LDAP records, or emails in 
> Admin without needing to go through a SQL database. 
>
> The aim of proof of concept wouldn't be to commit something to Django's 
> core - it would be to build an external, standalone proof-of-concept, 
> demonstrating that your documentation was complete and correct. Depending 
> on what backend you choose, it might turn into a fully viable project on 
> it's own.
>  
>
>> Improved error reporting
>>
>> The idea of making people’s lives better by improving error messages is 
>> fundamental. There would be a lot to discuss: what type of imports would we 
>> want to mask? I have read BetterErrorMessages and would be happy to get 
>> started soon. My idea behind this task would be to expand on this ticket: 
>> what would be great is to add a web console with live REPL support, similar 
>> to what Werkzeug debugger does. This could be a great starting point and 
>> would lead to a better use of Django.
>>
>
> This is an interesting idea; however, I see two problems:
>
> 1) It would involve reinventing the wheel. Werkzeug exists, and does its 
> job well; a GSoC project to "duplicate Werkzeug" doesn't strike me as a 
> good use of GSoC resources. However, a project to integrate Werkzeug's live 
> debugging capabilities into Django might be more viable.
>
> 2) Security implications. Unfortunately, more than one site has been 
> launched with debug=True accidentally left on; all you need to do then is 
> stimulate a server error, and you have REPL shell access to the server. 
> This strikes me as a remarkably effective foot-gun :-) Before you get too 
> involved in the implementation, I'd want to know the security issues have 
> been locked down.
>  
&

Re: [GSOC] Introduction and task proposal

2014-03-18 Thread Daniel Pyrathon

Hi all,

As promised, I have been working on the formalizing Meta task.
I apologize to not have posted in the last days, but I have come back with 
my proposal. I want to post this now to the community, in order to gain 
feedback and re-iterate.

Formalizing Meta

Enabling users to build custom 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 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,
>>
>> On Wed, Mar 5, 2014 at 11:48 PM, Daniel Pyrathon wrote:
>>
>>> 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, Java, and I am currently using C++ for many 
>>> university projects. I have attended the last 3 EuroPython conferences and 
>>> I have been a staff member of the conference for the last 2 years.
>>>
>>> I am currently looking for a way to contribute to Django. Working on 
>>> Django would increase my knowledge of the framework as well as let me share 
>>> my own experience.
>>>
>>> Reading the ideas list I found 2 of them that are very interesting for 
>>> me, and so the reason behind this post is not only to present myself but 
>>> also to discuss their feasibility.
>>>
>>> Formalizing the Meta object
>>>
>>> This task is very challenging because it digs in the internals of 
>>> Django. I feel that I could learn a lot from it because I am very committed 
>>> to refactoring and write most of my code in TDD. I have also experience 
>>> with backwards compatibility. 
>>>
>>> Do you have any resources (code) I should read to get up to date and to 
>>> understand better how it is currently implemented?
>>>
>>
>> Unfortunately not; at least, not other than just trying to untangle the 
>> mess that is django/db/models/options.py and the things that depend on it 
>> (ModelForms and Admin in particular). This project really is the very model 
>> of untangling a ball of string. The reason it's listed as a potential 
>> project is specifically *because* there are no resources we can point you 
>> at.
>>
>> If, after looking at the code, you feel it's a little "thin" for 12 
>> weeks, one way to bulk it out is to build a proof of concept alternate 
>> implementation of Meta. Aside from the "it would be good to document this" 
>> aspect, the practical reason for wanting to formalise Meta is that it would 
>> allow people to build duck-typed implementations of Meta. If you can build 
>> an alternate implementation of the Meta interface, then you should be able 
>> to deploy your "duck" into a Django project and build a ModelForm, or 
>> browse it in Admin.
>>
>> So, for example, you could build a wrapper around a NoSQL store, or 
>> around an LDAP or email store, that *looked* like a Django model from the 
>> outside. This means you could view your NoSQL data, or LDAP records, or 
>> emails in Admin without needing to go through a SQL database. 
>>
>> The aim of proof of concept wouldn't be to commit something to Django's 
>> core - it would be to build an external, standalone proof-of-concept, 
>> demonstrating that your documentation was complete and correct. Depending 
>> on what backend you choose, it might turn into a fully viable project on 
>> it's own.
>>  
>>
>>> Improved error reporting
>>>
>>> The idea of making people’s lives better by improving error messages is 
>>> fundamental. There would be a lot to discuss: what type of imports would we 
>>> want to mask? I have read BetterErrorMessages and would be happy to get 
>>> started soon. My idea behind this task would be to expand on this ticket: 
>>> what would be great is to add a web console with live REPL support, similar 
>>> to what Werkzeug debugger does. This could be a great starting point and 
>>> would lead to a bette

Re: [GSOC] Introduction and task proposal

2014-03-19 Thread Daniel Pyrathon

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?

https://docs.google.com/document/d/1yp2_skqkxyrc0egdRv6ofnRGCI9nmvxDFBkCXgy0Jwo/edit#heading=h.wyxx4xxijubt

Thanks,
Dan

On Wednesday, March 19, 2014 7:32:10 AM UTC, Aymeric Augustin wrote:
>
> On 19 mars 2014, at 06:27, Zach Borboa > 
> wrote: 
>
> > Curious, how do you get REPL shell access to the server with DEBUG=True 
> with a vanilla Django deployment? 
>
> That part of the discussion was about adding the werkzeug interactive 
> debugger to Django’s default error page. 
>
> -- 
> Aymeric. 
>
>
>
>
>

-- 
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...@googlegroups.com.
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/16264cb7-3f44-434d-865a-8c33baa4d921%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [GSOC] Introduction and task proposal

2014-03-26 Thread Daniel Pyrathon

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-Magee wrote:
>
>
> For the benefit of those reading along at home; I gave some revised notes 
> and had a conversation with Daniel on IRC a couple of hours ago.
>
> Yours,
> Russ Magee %-)
>
>
> On Thu, Mar 20, 2014 at 4:10 AM, Daniel Pyrathon 
> 
> > wrote:
>
>> 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?
>>
>>
>> https://docs.google.com/document/d/1yp2_skqkxyrc0egdRv6ofnRGCI9nmvxDFBkCXgy0Jwo/edit#heading=h.wyxx4xxijubt
>>
>> Thanks,
>> Dan
>>
>> On Wednesday, March 19, 2014 7:32:10 AM UTC, Aymeric Augustin wrote:
>>
>>> On 19 mars 2014, at 06:27, Zach Borboa  wrote: 
>>>
>>> > Curious, how do you get REPL shell access to the server with 
>>> DEBUG=True with a vanilla Django deployment? 
>>>
>>> That part of the discussion was about adding the werkzeug interactive 
>>> debugger to Django’s default error page. 
>>>
>>> -- 
>>> Aymeric. 
>>>
>>>
>>>
>>>
>>>  -- 
>> 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-develop...@googlegroups.com .
>> To post to this group, send email to 
>> django-d...@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/16264cb7-3f44-434d-865a-8c33baa4d921%40googlegroups.com<https://groups.google.com/d/msgid/django-developers/16264cb7-3f44-434d-865a-8c33baa4d921%40googlegroups.com?utm_medium=email&utm_source=footer>
>> .
>>
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>

-- 
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...@googlegroups.com.
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/ad5d6016-2c6a-45b4-91c8-0e4500befc74%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [GSOC] Introduction and task proposal

2014-04-01 Thread Daniel Pyrathon

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 on your 
> development machine, I *highly* recommend checking out 
> https://github.com/jphalip/djangocore-box. It's a vagrant VM environment 
> that already has MySQL, PostgreSQL, and SQLite installed (plus most GIS 
> installations), along with various versions of python. Unfortunately it 
> doesn't have Oracle - but being able to run tests on 3/4 databases is 
> especially handy.
>
> Josh
>
> On Thursday, 27 March 2014 11:14:35 UTC+11, Russell Keith-Magee wrote:
>>
>>
>> Hi Daniel,
>>
>> Nope - other than "cross your fingers" that your proposal is accepted :-)
>>
>> But seriously…
>>
>> If you haven't already, I'd suggest reading Django's contribution docs, 
>> and getting your development environment set up. Make sure you can run 
>> Django's test suite. If you're particularly enthused, try your hand at 
>> working on a patch for an open ticket so you can get used to the toolchain 
>> and the review process. That way you'll be up to speed with Django's 
>> development process, so when the GSoC period starts, you'll be comfortable 
>> with our basic process, so you'll just have to deal with the actual GSoC 
>> work.
>>
>> Yours,
>> Russ Magee %-)
>>
>> On Wed, Mar 26, 2014 at 7:22 PM, Daniel Pyrathon wrote:
>>
>>> 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-Magee wrote:
>>>
>>>>
>>>> For the benefit of those reading along at home; I gave some revised 
>>>> notes and had a conversation with Daniel on IRC a couple of hours ago.
>>>>
>>>> Yours,
>>>> Russ Magee %-)
>>>>
>>>>
>>>> On Thu, Mar 20, 2014 at 4:10 AM, Daniel Pyrathon wrote:
>>>>
>>>>> 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?
>>>>>
>>>>> https://docs.google.com/document/d/1yp2_skqkxyrc0egdRv6ofnRGCI9nmvxDFB
>>>>> kCXgy0Jwo/edit#heading=h.wyxx4xxijubt
>>>>>
>>>>> Thanks,
>>>>> Dan
>>>>>
>>>>> On Wednesday, March 19, 2014 7:32:10 AM UTC, Aymeric Augustin wrote:
>>>>>
>>>>>> On 19 mars 2014, at 06:27, Zach Borboa  wrote: 
>>>>>>
>>>>>> > Curious, how do you get REPL shell access to the server with 
>>>>>> DEBUG=True with a vanilla Django deployment? 
>>>>>>
>>>>>> That part of the discussion was about adding the werkzeug interactive 
>>>>>> debugger to Django’s default error page. 
>>>>>>
>>>>>> -- 
>>>>>> Aymeric. 
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>  -- 
>>>>> 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-develop...@googlegroups.com.
>>>>> To post to this group, send email to django-d...@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/16264cb7-3f44-434d-865a-
>>>>> 8c33baa4d921%40googlegroups.com<https://groups.google.com/d/msgid/django-developers/16264cb7-3f44-434d-865a-8c33baa4d921%40googlegroups.com?utm_medium=email&utm_source=footer>
>>>>> .
>>>>>
>>>>> For more options, visit https://groups.google.com/d/optout.

[GSOC] Hi from Daniel!

2014-04-23 Thread Daniel Pyrathon

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/1yp2_skqkxyrc0egdRv6ofnRGCI9nmvxDFBkCXgy0Jwo/edit#heading=h.wyxx4xxijubt

I'm really looking forward to getting started: I am already in contact with 
my mentor and I was hoping to get to know the community a bit more too :)
Also, if you have any suggestions please let me know. I am quite new and I 
have 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...@googlegroups.com.
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/44198942-c5cf-4205-9eb1-395ea8c16fa4%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [GSOC] Hi from Daniel!

2014-05-04 Thread Daniel Pyrathon

Hi Ramiro,

Sorry for the late reply! I am currently stormed in university exams and 
this made me forget to get back to you. Luckily this will finish soon.

I am really happy you are looking forward to the project. It's great to 
know that you will be participating in the discussions. Please give me as 
much feedback as possible, especially in early stages. I want to make sure 
I am going in the right direction.
I will be posting an update every Friday on my work, this will be useful 
for you and anyone else to understand my progress and give me suggestions.

For anything else, just give me 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 
> > 
> wrote: 
> > 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/1yp2_skqkxyrc0egdRv6ofnRGCI9nmvxDFBkCXgy0Jwo/edit#heading=h.wyxx4xxijubt
>  
> > 
> > I'm really looking forward to getting started: I am already in contact 
> with 
> > my mentor and I was hoping to get to know the community a bit more too 
> :) 
>
> I hope you enjoy your summer working on this project. 
>
> I have some ideas regarding i18n-related (de)coupling of Meta 
> atributes like verbose_name{,_plural} to/from such a core part of 
> Django. I'll be participating in the discussion and following your 
> work. 
>
> Welcome and good luck! 
>
> Regards, 
>
> -- 
> Ramiro Morales 
> @ramiromorales 
>

-- 
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...@googlegroups.com.
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/62d88ea0-dea5-4602-b123-e2aadc40c48b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[GSOC] Weekly update

2014-05-19 Thread Daniel Pyrathon

Hi All,

Today I will be starting my weekly updates on my SoC project: refactoring
Meta to a stable API. For anyone who missed out, you will be able to view
it
here:
https://docs.google.com/document/d/1yp2_skqkxyrc0egdRv6ofnRGCI9nmvxDFBkCXgy0Jwo/edit

This week is the first official week of SoC. Me and my mentor (Russell) are
initially approaching the work in the following way:

- *Document the existing Meta API*
For each endpoint, document the following:
- Input parameters and return type
- Caching pattern used
- Where it's called from (internally and externally to Meta)
- Why is it being called
- When is it being called

- *Propose an initial refactor plan*
Once the documentation has been done, I should have a better idea of the
current implementation. This will allow me to mock a proposed
implementation that will be reviewed at my next update call, on Monday.

My next update will be posted on Friday, just to make sure the community is
informed of my progress. For any major updates that require community
approval, I will be creating separate threads.
My name on the internet is pirosb3, so if you want to have a chat about my
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 this group and stop receiving 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 http://groups.google.com/group/django-developers.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-developers/c0d9a1f7-4fae-4c47-aae1-59b472c46939%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

43 matches

Mail list logo