[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kwrite-devel
Subject:    Re: Python built-in functions
From:       J._Pablo_Martín_Cobos <goinnn () gmail ! com>
Date:       2013-05-14 11:50:41
Message-ID: CALNyWLGp2p-AA-rBW9yJ47U7hv+=2vO80qjdsAVyia7cAFMhYg () mail ! gmail ! com
[Download RAW message or body]

[Attachment #2 (multipart/alternative)]


2013/5/14 Alex Turbov <i.zaufi@gmail.com>

> another idea is to make a new syntax file for python3.xml (w/o any
> deprecated functions) w/ other priority -- so if I'm doing Python3 code, =
I
> don't want to see outdated stuff... just like we have C++ and C++11 (and
> C++11/Qt) nowadays.
>
>
>
But How can kate distinguish if you are working with python 2 or python 3??


> On Tue, May 14, 2013 at 1:41 PM, J. Pablo Mart=EDn Cobos <goinnn@gmail.co=
m>wrote:
>
>> I think that this is a good idea... "backwards compatibility" is
>> important.
>>
>>
>> 2013/5/14 Gerald Senarclens de Grancy <gerald@senarclens.eu>
>>
>>> Hi,
>>> would anybody mind if I updated the built-in functions in python.xml
>>> to http://docs.python.org/3/library/functions.html while leaving the
>>> old Python 2 elements (like xrange) there?
>>> /g
>>>
>>> PS: Note that this would mean moving print from commands to built-in
>>> functions...
>>>
>>> --
>>> Gerald Senarclens de Grancy
>>> http://senarclens.eu/~gerald/
>>> Open minds on open source!
>>> _______________________________________________
>>> KWrite-Devel mailing list
>>> KWrite-Devel@kde.org
>>> https://mail.kde.org/mailman/listinfo/kwrite-devel
>>>
>>
>>
>> _______________________________________________
>> KWrite-Devel mailing list
>> KWrite-Devel@kde.org
>> https://mail.kde.org/mailman/listinfo/kwrite-devel
>>
>>
>
> _______________________________________________
> KWrite-Devel mailing list
> KWrite-Devel@kde.org
> https://mail.kde.org/mailman/listinfo/kwrite-devel
>
>

[Attachment #5 (text/html)]

<div dir="ltr">2013/5/14 Alex Turbov <span dir="ltr">&lt;<a \
href="mailto:i.zaufi@gmail.com" \
target="_blank">i.zaufi@gmail.com</a>&gt;</span><br><div class="gmail_extra"><div \
class="gmail_quote"><blockquote class="gmail_quote" style="margin:0px 0px 0px \
0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
 another idea is to make a new syntax file for python3.xml (w/o any deprecated \
functions) w/ other priority -- so if I&#39;m doing Python3 code, I don&#39;t want to \
see outdated stuff... just like we have C++ and C++11 (and C++11/Qt) nowadays.<div \
class=""> <div class="h5"><br>
<br></div></div></blockquote><div><br></div><div style>But How can kate distinguish \
if you are working with python 2 or python 3?? </div><div> </div><blockquote \
class="gmail_quote" style="margin:0px 0px 0px \
0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
 <div class=""><div class="h5"><div class="gmail_quote">On Tue, May 14, 2013 at 1:41 \
PM, J. Pablo Martín Cobos <span dir="ltr">&lt;<a href="mailto:goinnn@gmail.com" \
target="_blank">goinnn@gmail.com</a>&gt;</span> wrote:<br> <blockquote \
class="gmail_quote" style="margin:0px 0px 0px \
0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
 <div dir="ltr">I think that this is a good idea... &quot;backwards \
compatibility&quot; is important.</div><div><div><div \
class="gmail_extra"><br><br><div class="gmail_quote">2013/5/14 Gerald Senarclens de \
Grancy <span dir="ltr">&lt;<a href="mailto:gerald@senarclens.eu" \
target="_blank">gerald@senarclens.eu</a>&gt;</span><br>


<blockquote class="gmail_quote" style="margin:0px 0px 0px \
0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">Hi,<br>
 would anybody mind if I updated the built-in functions in python.xml<br>
to <a href="http://docs.python.org/3/library/functions.html" \
target="_blank">http://docs.python.org/3/library/functions.html</a> while leaving \
the<br> old Python 2 elements (like xrange) there?<br>
/g<br>
<br>
PS: Note that this would mean moving print from commands to built-in<br>
functions...<br>
<br>
--<br>
Gerald Senarclens de Grancy<br>
<a href="http://senarclens.eu/~gerald/" \
target="_blank">http://senarclens.eu/~gerald/</a><br> Open minds on open source!<br>
_______________________________________________<br>
KWrite-Devel mailing list<br>
<a href="mailto:KWrite-Devel@kde.org" target="_blank">KWrite-Devel@kde.org</a><br>
<a href="https://mail.kde.org/mailman/listinfo/kwrite-devel" \
target="_blank">https://mail.kde.org/mailman/listinfo/kwrite-devel</a><br> \
</blockquote></div><br></div> \
</div></div><br>_______________________________________________<br> KWrite-Devel \
mailing list<br> <a href="mailto:KWrite-Devel@kde.org" \
target="_blank">KWrite-Devel@kde.org</a><br> <a \
href="https://mail.kde.org/mailman/listinfo/kwrite-devel" \
target="_blank">https://mail.kde.org/mailman/listinfo/kwrite-devel</a><br> \
<br></blockquote></div><br> \
</div></div><br>_______________________________________________<br> KWrite-Devel \
mailing list<br> <a href="mailto:KWrite-Devel@kde.org">KWrite-Devel@kde.org</a><br>
<a href="https://mail.kde.org/mailman/listinfo/kwrite-devel" \
target="_blank">https://mail.kde.org/mailman/listinfo/kwrite-devel</a><br> \
<br></blockquote></div><br></div></div>



_______________________________________________
KWrite-Devel mailing list
KWrite-Devel@kde.org
https://mail.kde.org/mailman/listinfo/kwrite-devel


[prev in list] [next in list] [prev in thread] [next in thread] 

Configure | About | News | Add a list | Sponsored by KoreLogic