We shouldn't bloat the API. Obviously there are nice looking approaches and
not to mention the different behaviour in some of them.
-1 on this proposal from me.
On Tuesday, July 3, 2012 8:22:59 AM UTC+3, Ćukasz Rekucki wrote:
>
> On 3 July 2012 06:27, Maxime Haineault
While I'm reading all topics, listed below I'm thinking... is it too early
to announce **experimental** Python 3.2 support in Django 1.4?
- Python 3 port - all tests now pass on 2.5.4, 2.6.2, 2.7.2 and 3.2.2
with the same codebase
- *Release version 1.4.*
- *Move to Git/GitHub.* I
Now, that's a start!
--
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To view this discussion on the web visit
My point was the social factor. I mean the GitHub community is quite
bigger. It's not big issue if we're using mercurial instead of git. Sure, I
prefer git, it's faster and stuff, but it's not a big deal, right now.
Anyway, I'm trying to get into making the tests run and if I see some
result
+1
--
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/-/Xn1dFyUtjJsJ.
To post to this group, send email to django-developers@googlegroups.com.
To
Have you made some sort of TODO list I could use?
Or selecting some failing test and make it run fine would be fine as well?
Also, how about moving this project to GitHub?
Django is there, too(https://github.com/django/) and I thing we could find
more participants.
--
You received this
@Jannis Leidel, is there some plan, tasks or something for new contributors
and how could I(python developer and django user) help?
--
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To view this discussion on the web visit