Jannis, that's great news indeed, I'll help with testing.
--
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/-/jzva36TUYGcJ.
To post to this group, sen
@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
https://groups.
If you want to test Linux deployment, install Ubuntu under VirtualBox:
https://www.virtualbox.org/
Brian Schott
bfsch...@gmail.com
On Nov 8, 2011, at 11:37 AM, richard.prosser wrote:
> Yes I know but Vista isn't the best platform and my laptop isn't that
> hot!
>
> Plus I have very good Unix/
Yes I know but Vista isn't the best platform and my laptop isn't that
hot!
Plus I have very good Unix/Linux experience, which may help.
Richard
On Nov 7, 2:01 pm, "Jonas H." wrote:
> On 11/07/2011 12:00 PM, richard.prosser wrote:
>
> > I may be willing to support this. I have 18 month's of Pyt
On 11/07/2011 12:00 PM, richard.prosser wrote:
I may be willing to support this. I have 18 month's of Python
experience (mostly 2.4) and I have been out of work for a long time
due to illness, so a project like this may look good on my CV!
I have never been involved in an OS project before, thou
I may be willing to support this. I have 18 month's of Python
experience (mostly 2.4) and I have been out of work for a long time
due to illness, so a project like this may look good on my CV!
I have never been involved in an OS project before, though I am aware
of the guidelines.
At present the
I'm not going to rehash everything Vernon says below, but I will say
that as someone who maintains a module which installs and runs on
Python 2.4 - 3.2, Vernon's comments are spot on.
We first started supporting Python 3.0 almost immediately after its
release and we had a few misconceptions going
> One assumption of the strategy I outlined was the fact that Django is
> as close to 3.X as possible. Django 1.4 will require Python 2.5 or
> higher, but I'm not sure how quick we can do the jump to 2.6, which
> is recommended by the Python porting docs [1].
>
Don't confuse "recommended" with "ne
On Wed, Sep 14, 2011 at 8:42 PM, Jannis Leidel wrote:
>
> > Anybody knows somebody who started a django/py3 port already? We should
> unify our efforts.
>
> As I said earlier in this thread, there is now a Python 3 branch in the
> Django SVN.
>
Thank you! Really good to see that.
>
> > If core
On 14.09.2011, at 19:19, Cal Leeming [Simplicity Media Ltd] wrote:
> Can I ask, have the django core team already accepted that Django will
> eventually be a 3.x framework, or will it be un-officially forked?
Yes, the core team has identified the port to Python 3 as a needed step which
is why
On 14.09.2011, at 18:57, Ákos Péter Horváth wrote:
> Really, I started to port that with a recursive 2to3. It is not too far from
> good working. There are no big magic things, altough I think a py2 and py3
> support isn't possible from a common source tree. Some deep core improvement
> is nee
Can I ask, have the django core team already accepted that Django will
eventually be a 3.x framework, or will it be un-officially forked?
Personally - I'd love to see people ride the 2.x train until its last dying
breath, but that's just me ;)
Cal
2011/9/14 Ákos Péter Horváth
> Another vote to
Another vote to python3 :-)
Really, I started to port that with a recursive 2to3. It is not too far from
good working. There are no big magic things, altough I think a py2 and py3
support isn't possible from a common source tree. Some deep core improvement
is needed too, mostly on the unicode line
Hi,
On Wed, Sep 14, 2011 at 10:03 AM, Jannis Leidel wrote:
> Hi all,
>
> After last week's sprint I wanted to get you up-to-speed about the
> current state of porting Django to Python 3.
>
I'm very happy with this news.
> As some may be aware Martin von Löwis has been working on a port for
> a
Daniel,
> I wasn't trying to suggest we leave anyone behind, far from it. I
> was suggesting move the code to Python 3 now, while there's less code
> there (than some future date) but using 3to2[1] to help others on
> Python 2.X. Since Django still supports 2.5, it's possible that this
> isn't e
Help to cite appropriately. [1] was http://pypi.python.org/pypi/3to2.
On Sep 14, 10:55 am, Daniel Lindsley wrote:
> Jannis,
>
> I wasn't trying to suggest we leave anyone behind, far from it. I
> was suggesting move the code to Python 3 now, while there's less code
> there (than some future d
Jannis,
I wasn't trying to suggest we leave anyone behind, far from it. I
was suggesting move the code to Python 3 now, while there's less code
there (than some future date) but using 3to2[1] to help others on
Python 2.X. Since Django still supports 2.5, it's possible that this
isn't even an o
Daniel,
> "You have my sword." I want to see this happen & would love to be a
> part of it.
Huzzah!
> A couple questions:
>
> * How should patches be provided? Trac? BitBucket?
For now via Trac, that's why we've moved the changes into a SVN branch.
Unless anyone has a better idea I could cre
Jannis,
"You have my sword." I want to see this happen & would love to be a
part of it. A couple questions:
* How should patches be provided? Trac? BitBucket?
* Where should feedback go? This mailing list? Somewhere else?
* This is further off, but once we have a ported Django, how do get
the
Hi all,
After last week's sprint I wanted to get you up-to-speed about the
current state of porting Django to Python 3.
As some may be aware Martin von Löwis has been working on a port for
a while [1] but only recently I've had the chance to meet with him and
talk through the porting process.
I'
20 matches
Mail list logo
