On Nov 28, 7:14 pm, Vinay Sajip wrote:
> suite is a boon in this regard. Though having worked through the
> tests, it doesn't seem like the DRY principle is followed as much as
> it could be ... for example, the same literals being used over and
> over again in
On Nov 28, 5:36 pm, Jannis Leidel wrote:
>
> Ah, that makes sense, in fact your approach is much closer to what I
> remember doing when pip and virtualenv was ported.
Right, since I did those ports originally :-)
> Honestly, I'm not sure how hard the merge is, as I'm not sure
On 28.11.2011, at 18:08, Vinay Sajip wrote:
> On Nov 28, 1:04 pm, Jannis Leidel wrote:
>>
>> I'm a bit concerned that you didn't get in touch with us before you
>> started with the work, since tracking the changes would have been
>> easier. FWIW, Martin von Löwis, Alex and me
On Nov 28, 9:29 am, Kiril Vladimirov wrote:
> 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.
Well, it's
On Nov 28, 1:04 pm, Jannis Leidel wrote:
>
> I'm a bit concerned that you didn't get in touch with us before you
> started with the work, since tracking the changes would have been
> easier. FWIW, Martin von Löwis, Alex and me would be those you can
> ask if you need any
Hi Vinay,
Many thanks for your efforts so far, as you can imagine I have a few
questions, both procedural and technical. I should note though that
I haven't reviewed all your changes in detail yet, since they are..
massive :)
I'm a bit concerned that you didn't get in touch with us before you
On Sat, Nov 26, 2011 at 1:33 AM, Vinay Sajip wrote:
> I'm working on a port of Django to Python 3. I'm getting close, and in
> terms of
> test coverage pretty much almost there, but a few remaining test
> failures are
> eluding me, and I could probably use some help to
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
BitBucket has full git support btw.
--
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/-/Ax7zncVO2FYJ.
To post to this group, send email to
On Nov 27, 2:10 pm, Kiril Vladimirov wrote:
> 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?
I would say: just clone the repo, try to reproduce the results, report
any differences you find from my
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
Hi,
I'm just learning python at the moment to use Django so I don't have the
knowledge to help you but keep up the good work.
I'm looking forward to seeing the result of your work.
Cheers. :)
--
You received this message because you are subscribed to the Google Groups
"Django developers"
Sorry the formatting of the post got mangled - not sure what happened
there!
Regards,
Vinay Sajip
--
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
I'm working on a port of Django to Python 3. I'm getting close, and in
terms of
test coverage pretty much almost there, but a few remaining test
failures are
eluding me, and I could probably use some help to speed things up.
I started with the features/py3k branch on the BitBucket Django mirror
> Some examples:
Thanks for posting them:
> >>> Template(u"{{ foo }}").render(Context({"foo":"bar"}))
> u'bar'
I get
py> Template("{{ foo }}").render(Context({b"foo":b"bar"}))
''
I think that's correct: the dictionary has no key "foo".
I'm also unsure what this has to do with UTF-8: isn't
By the way, did you the effort of porting reported on the python website:
http://wiki.python.org/moin/PortingDjangoTo3k
Seems to the good way to achieve it some times...
On Tue, Feb 2, 2010 at 5:37 PM, Dave wrote:
> Ok everyone, a bit of a status update.
>
> We finished our
> > In many cases, this is true, but there are other scenarios (certain
> > forms of exception handling, for example) where there is no syntax
> > that's valid in both versions. That's syntax, not just libraries and
> > functions. There's no way to even get a file to parse in both Python 2
> > and
2010/1/14 Marty Alchin :
> On Thu, Jan 14, 2010 at 2:32 PM, Karen Tracey wrote:
>> Martin's approach was single codebase where the 3.x version for execution is
>> generated by 2to3, not single source for execution across 2.x and 3.x. Thus
>> I'm wondering
On Thu, Jan 14, 2010 at 2:32 PM, Karen Tracey wrote:
> Martin's approach was single codebase where the 3.x version for execution is
> generated by 2to3, not single source for execution across 2.x and 3.x. Thus
> I'm wondering if this difference is accounted for by 2to3? If
On Thu, Jan 14, 2010 at 2:17 PM, Marty Alchin wrote:
> 2010/1/14 Łukasz Rekucki :
> > It is possible to write 3.x code that is backwards-compatible with
> > python 2.6+. There are some rough edges like, names of stdlib modules,
> > instance checks for
2010/1/14 Łukasz Rekucki :
> It is possible to write 3.x code that is backwards-compatible with
> python 2.6+. There are some rough edges like, names of stdlib modules,
> instance checks for strings and some introspection details. In my
> opinion, it's pretty much the same as
2010/1/14 Jesus Mager :
> Hi!
>
> I don't think we can have a library working on python 2 and at the
> same time on python 3.(Dont know if 3to2 is a good solution).
It is possible to write 3.x code that is backwards-compatible with
python 2.6+. There are some rough edges like,
>From my experience with the 2to3 tool, it's no silver bullet for
porting to 3. I have had plenty of cases where manual tweeking of the
code was needed. The tool does help a lot on getting trivial things
changed over, but certain things it just can't do. Now this is with a
very small library of
Having survived the update of pywin32 to python 3, let me say that
both comments are correct:
1) you do NOT create a fork, you convert the existing code so that it
will run through 2to3
2) it takes a LOT of hand refactoring of older 2.x code to get ready
for 2to3.
and, may I add:
3) it's worth the
On Wed, Jan 13, 2010 at 4:21 AM, Hanne Moa wrote:
> 2010/1/13 Tobias McNulty :
> > I am by no means an expert on the matter, but I remember seeing a comment
> > awhile back suggesting that it generally makes more sense to fix the 2to3
> > script than
On Wed, Jan 13, 2010 at 5:21 PM, Hanne Moa wrote:
> 2010/1/13 Tobias McNulty :
>> I am by no means an expert on the matter, but I remember seeing a comment
>> awhile back suggesting that it generally makes more sense to fix the 2to3
>> script than to
2010/1/13 Tobias McNulty :
> I am by no means an expert on the matter, but I remember seeing a comment
> awhile back suggesting that it generally makes more sense to fix the 2to3
> script than to maintain two branches of the same library. Might that be the
> case here as
I am by no means an expert on the matter, but I remember seeing a comment
awhile back suggesting that it generally makes more sense to fix the 2to3
script than to maintain two branches of the same library. Might that be the
case here as well?
Sent from a mobile phone, please excuse any typos.
On
On Tue, Jan 12, 2010 at 10:52 PM, Joshua Partogi
wrote:
> On Jan 9, 1:02 pm, Russell Keith-Magee wrote:
>> On Sat, Jan 9, 2010 at 2:25 AM, Dave wrote:
>> > Hello everyone,
>>
>> > My name is Dave Weber, and I'm a student at
On Jan 9, 1:02 pm, Russell Keith-Magee wrote:
> On Sat, Jan 9, 2010 at 2:25 AM, Dave wrote:
> > Hello everyone,
>
> > My name is Dave Weber, and I'm a student at the University of Toronto,
> > studying Computer Science. For one of our undergraduate
Hi all!
I'm CS student at the National Autonomous University of Mexico, and
I'm very interested to porting Django to Python 3 too. I hope the
efforts porting Django will be public on a svn branch, so I can also
collaborate. And of course, if a core developer can guide us, it will
be much better
On Sat, Jan 9, 2010 at 2:25 AM, Dave wrote:
> Hello everyone,
>
> My name is Dave Weber, and I'm a student at the University of Toronto,
> studying Computer Science. For one of our undergraduate courses led by
> Greg Wilson (http://www.cs.utoronto.ca/~gvwilson/), myself and a
Dave:
Wonderful! I am presently working on a project to get adodbapi
(http://sourceforge.net/projects/adodbapi) working in django. That
may be important to you since it is one of few db interfaces which has
a working python 3 version for Windows. Keep in touch.
--
Vernon Cole
On Jan 8, 11:25
Best of luck in your port.
On that note, I'm hoping when the 3k port will be officially supported, it
will not be backwards compatible. The core idea of 3k itself is the lack of
backwards compatibility ...
J. Leclanche / Adys
On Fri, Jan 8, 2010 at 8:25 PM, Dave wrote:
>
Hello everyone,
My name is Dave Weber, and I'm a student at the University of Toronto,
studying Computer Science. For one of our undergraduate courses led by
Greg Wilson (http://www.cs.utoronto.ca/~gvwilson/), myself and a group
of 10 other computer science students will be trying to port Django
35 matches
Mail list logo