On 16 févr. 2012, at 23:35, Reinout van Rees wrote:
> I didn't realize that I could mark it "ready for check-in" myself. (But there
> are 35 tickets ready for check-in, so I guess I still need to bug people to
> get it to be actually checked in).
That's mostly the consequence of a sprint that h
Just wanted to ask from curiosity if it were other factors besides broad
popularity, as BB is a great alternative. Most dev probably use both
services, at least passively, as lots of good code is here and there, and
I'm not against GH in any way. Per-line comments are actually a very good
point
On Thursday, February 16, 2012 at 6:06 PM, Carl Meyer wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Hi Reinout,
>
> On 02/16/2012 03:35 PM, Reinout van Rees wrote:
> > Partially related question: several tickets have a pull request on
> > github instead of an svn patch. Is that eno
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Reinout,
On 02/16/2012 03:35 PM, Reinout van Rees wrote:
> Partially related question: several tickets have a pull request on
> github instead of an svn patch. Is that enough? I assume a real svn
> patch is better?
A link on the ticket to a github
I am not a Django contributor, just a user. Whether it's github or
bitbucket or something else, the more important question is stick with the
current system and workflow as well as policies or move the code and then
of course also have a somewhat different workflow when you start using
githubs/
On 16-02-12 22:54, Aymeric Augustin wrote:
>
Related, a suggestion for the next release cycle: send an email to the
mailinglist that there's a beta coming up and that you ought to hurry up to get
new features in.
I sort of did, just after the alpha:
https://groups.google.com/group/django-deve
Hi Reinout,
> I'm pretty sure that "beta" means "nope, you won't get any changes that
> aren't bug fixes in", but I cannot find the page that says that. I assume I'm
> right?
That's true.
> Related, a suggestion for the next release cycle: send an email to the
> mailinglist that there's a bet
On 16-02-12 16:42, Łukasz Rekucki wrote:
1) I can't argue about popularity, because I have no data, but most
Django applications I use come from github, so it's also quite
popular.
Last year's djangocon.eu was instructive for me. We were debating
github/bitbucket at the office at the time.
B
On 16-02-12 05:27, James Bennett wrote:
Hot off the presses, it's the first Django 1.4 beta! Blog post with
more information is here:
https://www.djangoproject.com/weblog/2012/feb/15/14-beta-1/
I'm pretty sure that "beta" means "nope, you won't get any changes that
aren't bug fixes in", but I
On Feb 16, 10:10 pm, Aaron Merriam wrote:
> A while back I adopted a new way of extending managers and querysets that
> has been around for quite a while. It seems to originate from this django
> snippet (http://djangosnippets.org/snippets/734/)
There was a long thread about allowing the use of
The topic is: start using less (and bootstrap!)
Please, no more offtopic.
Thanks
On Thu, Feb 16, 2012 at 6:49 PM, Brendan Smith <
bren...@nationalpriorities.org> wrote:
> i also regrettably give a +1 to github over bitbucket. while I like
> others would love to see a python based solution, esp
i also regrettably give a +1 to github over bitbucket. while I like others
would love to see a python based solution, especially django, give github a run
for it's money, i think github is years ahead of bitbucket in terms of features
and ease of use.
i also think git itself is going to remai
heya,
You know what, I have to say the same thing =).
BitBucket/Mercurial would seem like a better match.
Also, with the buy-out by Atlassian, they seem to be iterating more
frequently, in terms of features, and I would love to see a major Python
project, like Django, behind them.
Cheers,
Victo
On 16 February 2012 18:27, Jacob Kaplan-Moss wrote:
> Hi folks --
>
> Please can we not have this argument? This is one of those holy wars
> that can get really, really ugly and I'd like to nip it in the bud.
>
Sorry for fueling this up. Should have think a few times more before
sending that. Als
Hi folks --
Please can we not have this argument? This is one of those holy wars
that can get really, really ugly and I'd like to nip it in the bud.
There's no way we'll come to consensus here any more than we'd be able
to come to consensus on a choice of text editor, operating system, or
favorit
A heavy bitbucket user here.
I personally prefer hg to git and bitbucket to github but I think github +
git would be better for django because of much larger community.
Guys, but please stop bashing bitbucket. Bitbucket supports both hg and git
(github don't), has nice bugtracker; bitbucket has
Here are my 2 cents.
IMHO, any developer that is currently contributing with Django can easily
work with both Bitbucket or Github.
AFAIK, the purpose o this big change is to enable more people to contribute
lowering the contribution barrier. With that in mind, I don't think the
decision should si
Github is just lightyears ahead of Bitbucket in design and usability. Beats
it on features and community too. They only time I consider Bitbucket is
only the circumstance that I need free private repos. That situation hasn't
come up yet.
On Thu, Feb 16, 2012 at 10:44 AM, Andrew Ingram wrote:
> On
On 16 February 2012 15:42, Łukasz Rekucki wrote:
> 1) I can't argue about popularity, because I have no data, but most
> Django applications I use come from github, so it's also quite
> popular.
>
> 2) I don't think Django should care if the collaboration tool runs
> python/django or java/grails a
On 16 February 2012 16:02, Stan wrote:
>
>
> On Feb 9, 1:49 pm, zalew wrote:
>> > We're going
>> > to solve that with our move to Git/GitHub, which will make it much
>> > easier for people to fork and much easier for core developers to
>> > integrate contributions.
>>
>> a bit offtopic: why notht
On Feb 9, 1:49 pm, zalew wrote:
> > We're going
> > to solve that with our move to Git/GitHub, which will make it much
> > easier for people to fork and much easier for core developers to
> > integrate contributions.
>
> a bit offtopic: why nothttp://bitbucket.org?similar features, it's on
> pyt
heya,
Are you willing to share your Bootstrap-themed admin, so others can see
what it's about, and contribute?
Cheers,
Victor
--
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
On Wed, Feb 15, 2012 at 10:37 PM, Donald Stufft wrote:
> I know this has been discussed before, but I wanted to bring it up again in
> light of the oncoming Djnago 1.4 beta.
>
> Can we increase the length of the username field in auth.User?
> I think that a max_length of 75 (to match the default E
Hi,
since it's a new feature and the beta release is already out, there is no
chance of getting that into 1.4 -- I think it's best if you push this
thread again after 1.4 has been released.
Cheers,
Florian
--
You received this message because you are subscribed to the Google Groups
"Django
24 matches
Mail list logo
