Re: GitHub migration done!

[Camilo Nova]

Great Job. This will make easier for a lot of people to be involved on the 
project.

On Friday, April 27, 2012 10:08:09 PM UTC-5, Adrian Holovaty wrote:
>
> On Fri, Apr 27, 2012 at 11:50 AM, Adrian Holovaty  
> wrote: 
> > We're going to do the migration to GitHub today. This means we'll no 
> > longer be committing code to our Subversion repository. Committers, 
> > please hold off on making commits until the migration is done. 
>
> OK, it's live! 
>
> https://github.com/django/django 
>
> A few quick points (though this definitely deserves a more in-depth 
> writeup): 
>
> * I renamed the old (mirror) repository to 
> https://github.com/django/django-old. We had talked about deleting it 
> outright to avoid confusion, but I realized at the last minute that 
> doing so would have deleted all the pull requests. I didn't want to 
> throw all of that out, and I think we can figure out a way to use 
> those pull requests in the new repository. 
>
> * I only migrated trunk (now called "master"), rather than including 
> all of the branches. This was the result of a bunch of discussion on 
> IRC with Brian R., et al. The thinking is that it kept the migration a 
> lot cleaner/simpler, and we can always add branches later. Of course, 
> we'll need to create the latest release branches. Otherwise, we can 
> consider the SVN branches on an individual basis. 
>
> * As expected, all forks of the old repository are now broken. Can 
> somebody volunteer to write some documentation on how to upgrade your 
> old fork to use the new upstream repo (rebase? simple patch?)? 
>
> * We're going to keep the Subversion repository around indefinitely, 
> but it'll no longer be updated. 
>
> * We're going to keep using Trac for tickets, but pull requests on 
> GitHub are also welcome. 
>
> * Clearly there are lots of bits of process that need to be updated 
> now, from the django-updates mailing list to our "contributing" 
> documentation, etc. We'll take care of all of that in the coming days, 
> and we should all expect some degree of confusion and unsettlement in 
> the community. That's totally fine, and we'll get through it. :-) 
>
> * Finally, big thanks to the folks on IRC today who helped me through 
> the process and contributed good ideas. 
>
> I'm planning to write up a blog post on how the process went, for the 
> benefit of the five open-source projects still using Subversion. 
>
> Adrian 
>

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers" group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/django-developers/-/3AYxf2T_uFgJ.
To post to this group, send email to django-developers@googlegroups.com.
To unsubscribe from this group, send email to 
django-developers+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-developers?hl=en.

Re: first() and last(), earliest() and latest()

[Camilo Nova]

+1 for first and last

-- 
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?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.

CSRF Header broken on uWSGI

[Camilo Nova]

Hi, im currently on:

- Django version 1.3 rc 1
- uWSGI 0.9.6.8
- Python 2.6.5
- jQuery 1.5.1

This is my configuration from my production server, where i have an
application that does
simple operations on data, the general case is to have a form and send
data over POST.

Everything works fine until i try to make an AJAX call to a single
view that pulls me some
data from DB, when i access my view from a non-ajax way it returns me
the data, but when
i try to get it via ajax the uWSGI process hangs until it been killed.

I use this snippet (from 
http://docs.djangoproject.com/en/dev/ref/contrib/csrf/#ajax)
:
$('html').ajaxSend(function(event, xhr, settings) {
function getCookie(name) {
var cookieValue = null;
if (document.cookie && document.cookie != '') {
var cookies = document.cookie.split(';');
for (var i = 0; i < cookies.length; i++) {
var cookie = jQuery.trim(cookies[i]);
// Does this cookie string begin with the name we
want?
if (cookie.substring(0, name.length + 1) == (name +
'=')) {
cookieValue =
decodeURIComponent(cookie.substring(name.length + 1));
break;
}
}
}
return cookieValue;
}
if (!(/^http:.*/.test(settings.url) || /
^https:.*/.test(settings.url))) {
// Only send the token to relative URLs i.e. locally.
xhr.setRequestHeader("X-CSRFToken", getCookie('csrftoken'));
}
});

Local works great, but in production it fails, first i discover this
snippet won't work
on jQuery 1.5, it only works on jQuery 1.5.1, seems good for me to put
that in the
docs, to avoid people dont waste time as me.

It works fine in my production server using this snippet:
$('html').ajaxSend(function (event, xhr, settings) {
function getCookie(name) {
var cookieValue = null;
if (document.cookie && document.cookie !== '') {
var cookies = document.cookie.split(';');
for (var i = 0; i < cookies.length; i++) {
var cookie = $.trim(cookies[i]);
// Does this cookie string begin with the name we
want?
if (cookie.substring(0, name.length + 1) === (name +
'=')) {
cookieValue =
decodeURIComponent(cookie.substring(name.length + 1));
break;
}
}
}
return cookieValue;
}
if (!(/^http:.*/.test(settings.url) || /
^https:.*/.test(settings.url))) {
// Only send the token to relative URLs i.e. locally.
//xhr.setRequestHeader("X-CSRFToken", getCookie('csrftoken'));
if (settings.data === null) {
settings.data = '';
}
settings.data = settings.data + '&csrfmiddlewaretoken=' +
getCookie('csrftoken');
}
});

For me seems like a problem when django reads the request header or
something, i would
like to share this, and see if we can find any solution, because for
me using the header is
more cleaner than sending the csrf value on the data.

What you guys think?

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers" group.
To post to this group, send email to django-developers@googlegroups.com.
To unsubscribe from this group, send email to 
django-developers+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-developers?hl=en.

Re: CSRF Header broken on uWSGI

[Camilo Nova]

Gabriel, thanks for your response.

How can i test the code that makes this crsf verification from the
header, from my
other testings this only happens after django make a fix in the latest
security release.

I would like to make a test enviroment, where can i start to look?

On Mar 8, 12:59 am, Gabriel Hurley  wrote:
> From the information you've given I can't say what's causing your process to
> hang, but as to your other point about jQuery... yes, jQuery 1.5.0 had a
> legitimate bug  that prevented headers
> from being properly set on AJAX requests. It was one of the reasons they
> pushed out the 1.5.1 release so quickly. In general we haven't documented
> cases where specific point releases of third party libraries had known bugs,
> but since I got bit by this as well I'm more inclined than usual to make an
> exception. Obviously, though, the impact of that problem will decrease over
> time as people catch up on newer jQuery releases.
>
> All the best,
>
>     - Gabriel

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers" group.
To post to this group, send email to django-developers@googlegroups.com.
To unsubscribe from this group, send email to 
django-developers+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-developers?hl=en.

Getting max_length for forms.IntegerField

[Camilo Nova]

Hi all,

Were im working we usually take in mind that fields in web forms
should have a max length value for input, and we apply them well in
cases like:

username = forms.CharField(
max_length=30,
)

But in cases like:

cash = forms.IntegerField(
min_value=0,
max_value=100,
)

Should it be good to set the max_length property too, even it will be
great if by defaults max_length value would be 'len(max_value)'

you see this usefull as me?

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers" group.
To post to this group, send email to django-developers@googlegroups.com.
To unsubscribe from this group, send email to 
django-developers+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-developers?hl=en.

Re: ANNOUNCE: Django 1.0 released

[Camilo Nova]

+1 Django Party @ Bogota, Colombia.

Thanks to all the team, there was a HUGE work, and totally awesome
what you did with django, cheers to jacob, my dear friend at IRC
Magus- and everyone.

Django, just a piece of art.

On Sep 3, 9:40 pm, "Ariel Mauricio Nunez Gomez"
<[EMAIL PROTECTED]> wrote:
> +1 for Django 1.0 party in Bogota, Colombia.
>
> Thanks to the development team. And especially for Justin Bronn, for his gis
> contribution.
>
> Ariel Núñez // Project Manager // Puenti Ltda
> Barranquilla // Colombia // South America
> [EMAIL PROTECTED] // +57(300)8438443 // +57(317)3205876
>
> On Wed, Sep 3, 2008 at 8:53 PM, Diego Andrés Sanabria Martin (diegueus9) <
>
> [EMAIL PROTECTED]> wrote:
> > Hi,
>
> > I'm a happy user of django, and I want to say this is the better
> > framework for a good, elegant and fast development, i wanna be a
> > developer of django but is something hard, in my country Colombia, I
> > say to everybody about this amazing framework and work in a couple of
> > projects for make more people use it.
>
> > Congratulations.
>
> > PS: my english is not very good.
>
> > On Wed, Sep 3, 2008 at 20:00, Martin Diers <[EMAIL PROTECTED]> wrote:
>
> > > On Sep 3, 2008, at 7:07 PM, James Bennett wrote:
>
> > >> The Django team is pleased to announce the release of Django 1.0
> > >> this evening:
>
> > >> Download:http://www.djangoproject.com/download/
> > >> Release notes:http://docs.djangoproject.com/en/dev/releases/1.0/
>
> > >> Have fun with it, and we'll see you in a few days for DjangoCon.
>
> > > And there was much rejoicing!
>
> > > Congratulations to the entire development team. It has been a pleasure
> > > to watch the development of Django. The leadership and focus of this
> > > team is a model that few open source projects achieve, but to which
> > > all should aspire.
>
> > --
> > Diego Andrés Sanabria
> > Ingeniería de Sistemas Universidad Distrital
> > blog trágico mágico cómico musical:http://diegueus9.blogspot.com
> > blog geek:http://pyautoservicio.blogspot.com
> > cel 3015290609
>
> >http://www.el-directorio.org/Diegueus9
> > El sitio de linux y el Software Libre en Colombia
>
> > "Hay pecados cuya fascinación está más en el recuerdo que en la
> > comisión de ellos." Oscar Wilde

--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django developers" group.
To post to this group, send email to django-developers@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-developers?hl=en
-~--~~~~--~~--~--~---