gmane.comp.python.porting

Re: Stuck with raw unicode literals

Lennart Regebro — 2013-05-23T06:00:54

Well the first question is why you need a raw unicode literal in the
first place?

Raw string literals simply interpret escape sequences literally, so
that '\0x00' is interpreted as a four character string, while in
normal strings it's interpreted as a once character string.

Unicode literals are weird beasts, where most backslash escape
sequences are interpreted literally, but not the Unicode escape
sequences, so '\0x00' is four characters, but '\u0000' is one.

The simplest way to handle it might simply to be to escape the
backslashes, ie change ur'\0x57bla\foo' to u'\\0x57bla\\foo'

//Lennart

Stuck with raw unicode literals

Chitrank Dixit — 2013-05-23T05:37:47

Hello Python developers

I am working on Python Porting 2.7 >=3.3 . unicode literals will be fine
but still raw unicode literals is an issue (ur' '). I have found the
solution in six module.

This is the solution

original python 2.7 code
ur'Pythondev'

using six module for py 2.7>=3.3
six.u(r'Pythondev')

Does my solution is okay or something else is needed to do I am very
confused with this.


*Regards
*
*Chitrank Dixit
*
*IIPS-DAVV
*
*Indore (M.P.) , India *
*MCA
*
*trackleech.blogspot.in*
_______________________________________________
Python-porting mailing list
Python-porting-+ZN9ApsXKcEdnm+yROfE0A< at >public.gmane.org
http://mail.python.org/mailman/listinfo/python-porting

Re: Questions for porting unicode with backward compatibility

2013-05-22T07:40:24

Quoting Lennart Regebro <regebro-Re5JQEeQqe8AvxtiuMwx3w< at >public.gmane.org>:


My guess is that it is the html module from emeraldtree. Of course,  
this *ought* to be
emeraldtree.html, not a toplevel html package. So it would also be  
helpful to see whether
/home/chitrank/Documents/Google_Summer_of_code/moinmoin_pre/Emeraldtree/EmeraldTree/emeraldtree
happens to be in sys.path (which it ought not to).

Regards,
Martin

Re: Questions for porting unicode with backwardcompatibility

Lennart Regebro — 2013-05-22T06:38:45

On Wed, May 22, 2013 at 12:38 AM, Chitrank Dixit
<chitrankdixit-Re5JQEeQqe8AvxtiuMwx3w< at >public.gmane.org> wrote:

Can you do this:

    import html
    print(html.__file__)

It sounds like the html module somehow has been shadowed by something else.

//Lennart

Re: Questions for porting unicode with backwardcompatibility

Chitrank Dixit — 2013-05-21T22:38:48

Okay module six is made good but it lacks in some cases

I am referring this documentation of six module
http://pythonhosted.org/six/

and getting problem in this line *from six.moves import html_entities,
html_parser*
I have installed six module in both python 2 and python 3.3 but I am
getting problem in python 3.3 it says

Traceback (most recent call last):
  File "html.py", line 34, in <module>
    from six.moves import html_entities, html_parser
  File "/usr/local/lib/python3.3/dist-packages/six.py", line 84, in __get__
    result = self._resolve()
  File "/usr/local/lib/python3.3/dist-packages/six.py", line 103, in
_resolve
    return _import_module(self.mod)
  File "/usr/local/lib/python3.3/dist-packages/six.py", line 74, in
_import_module
    __import__(name)
  File
"/home/chitrank/Documents/Google_Summer_of_code/moinmoin_pre/Emeraldtree/EmeraldTree/emeraldtree/html.py",
line 34, in <module>
    from six.moves import html_entities, html_parser
  File "/usr/local/lib/python3.3/dist-packages/six.py", li

Re: Questions for porting unicode with backwardcompatibility

Lennart Regebro — 2013-05-21T17:03:28

Yeah, sorry, I misread that.

//Lennart

Re: Questions for porting unicode with backward compatibility

Martin v. Löwis — 2013-05-21T16:30:18

Am 21.05.13 10:32, schrieb Chitrank Dixit:

I agree with Lennart: "chr", and "it depends".


I disagree with Lennart: the next() *method* does not exist in Python 3.3:

Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
AttributeError: 'str_iterator' object has no attribute 'next'

The next() *function* exists in both versions, and has the same behavior.

Regards,
Martin

Re: Questions for porting unicode with backward compatibility

Tim Golden — 2013-05-21T08:52:52

Since you mention the next() *method*: in Python 3, the iterator
protocol changed slightly. Previously, the protocol demanded that a
Python iterator have a .next() method which was invoked by the protocol
or by the next() builtin function. In Python 3, the iterator has a
.__next__() method instead. Otherwise, the protocol works as before:
"for x in iterable:" works as expected, and the next() builtin invokes
".__next__()" rather than ".next()"

TJG

Re: Questions for porting unicode with backwardcompatibility

Lennart Regebro — 2013-05-21T08:46:14

On Tue, May 21, 2013 at 10:32 AM, Chitrank Dixit
<chitrankdixit-Re5JQEeQqe8AvxtiuMwx3w< at >public.gmane.org> wrote:

chr()


Depends on what, and how much of six you end up using.


As far as I know, yes.

//Lennart

Questions for porting unicode with backwardcompatibility

Chitrank Dixit — 2013-05-21T08:32:17

Hello Python Developers

I need to ask you some questions please answer me some questions

1) alternative to unichr() in python 3.3 (is it chr() or anything else is
available).

2) does using six module rather than doing some try catch stuff is a better
option.

3) does next() method behavior is same in both python 2.7 and python 3.3.




*Regards
*
*Chitrank Dixit
*
*IIPS-DAVV
*
*Indore (M.P.) , India *
*MCA
*
*trackleech.blogspot.in*
_______________________________________________
Python-porting mailing list
Python-porting-+ZN9ApsXKcEdnm+yROfE0A< at >public.gmane.org
http://mail.python.org/mailman/listinfo/python-porting

Re: Questions regarding relative import

Lennart Regebro — 2013-05-17T04:47:41

Absolute imports work in both Python 2 and Python 3, yes.

Importing from within the module requires the relative syntax in Python 3.

//Lennart

Questions regarding relative import

Chitrank Dixit — 2013-05-16T19:59:03

Hello Python developers

I am working on Porting to Python 2 to Python 3.3 and the refactoring using
2to3 says to use relative import at the place of the import. but ignoring
the relative import does the work for both the python 2 as well as python
3.3

So Does 2to3 is made as per refactoring from python 2 to python 3.2 ?



*Regards
*
*Chitrank Dixit
*
*IIPS-DAVV
*
*Indore (M.P.) , India *
*MCA
*
*trackleech.blogspot.in*
_______________________________________________
Python-porting mailing list
Python-porting-+ZN9ApsXKcEdnm+yROfE0A< at >public.gmane.org
http://mail.python.org/mailman/listinfo/python-porting

Re: Python porting from 2 to 3.3.1 discuss

Lennart Regebro — 2013-05-14T10:06:28

On Tue, May 14, 2013 at 11:44 AM, Chitrank Dixit
<chitrankdixit-Re5JQEeQqe8AvxtiuMwx3w< at >public.gmane.org> wrote:

Is this because of the lack of a u''-literal?

//Lennart

Python porting from 2 to 3.3.1 discuss

Chitrank Dixit — 2013-05-14T09:44:30

Hello

I am porting to python 3.3.1 with backward compatibility to python 2.7.3
but still some users of python 3.2 are left as the porting does not support
python 3.2 users. So the upcoming versions are more likely to follow the
python 3.3.1.


*Regards
*
*Chitrank Dixit
*
*IIPS-DAVV
*
*Indore (M.P.) , India *
*MCA
*
*trackleech.blogspot.in*
_______________________________________________
Python-porting mailing list
Python-porting-+ZN9ApsXKcEdnm+yROfE0A< at >public.gmane.org
http://mail.python.org/mailman/listinfo/python-porting

[ANN] six 1.3.0 released

Benjamin Peterson — 2013-03-18T21:02:41

I'm happy to announce the release of six 1.3.0. There's nothing
particularly ground-breaking here; gradual improvement on a few
fronts. Thanks to Marc Abramowitz for some pull requests.

Six is a Python 2 and 3 compatibility library.  It provides utility functions
for smoothing over the differences between the Python versions with the goal of
writing Python code that is compatible on both Python versions.  See the
documentation for more information on what is provided.

Six supports Python 2.4+.

Online documentation is at http://packages.python.org/six/.

Bugs can be reported to http://bitbucket.org/gutworth/six.  The code can also be
found there.

Here is the changelog for six 1.3.0:

- Issue #21: Add methods to access the closure and globals of a function.

- In six.iter(items/keys/values/lists), passed keyword arguments through to the
  underlying method.

- Add six.iterlists().

- Issue #20: Fix tests if tkinter is not available.

- Issue #17: Define callable to be builtin callable when it is available

Re: (no subject)

Lennart Regebro — 2013-03-05T15:47:20

You are running it with Python 2. To run it with Python 3, you need to
call python3.

It seems like GNURadioCompanion should support Python 2.7, though, so
I don't think that's the issue. But by all means, try. :-)

//Lennart

(no subject)

2013-02-15T16:25:05


I am using using ubuntu 12.10 i am trying to run a python block, namely OP25, in GNU Radio Companion v3.6.3-35-g4435082f, which uses python version 2.7.3 for some reason although python3.2 is in the lib folder. ! run the following command in terminal:

~$ python -m trace --count -C . op25_grc.py

Here is the output with an error:

Imported legacy fsk4
Using Volk machine: ssse3_32
Traceback (most recent call last):
File "/usr/lib/python2.7/runpy.py", line 162, in run_module_as_main
"_main__", fname, loader, pkg_name)
File "/usr/lib/python2.7/runpy.py", line 72, in run_code
exec code in run_globals
File "/usr/lib/python2.7/trace.py", line 819, in
main()
File "/usr/lib/python2.7/trace.py", line 807, in main
t.runctx(code, globs, globs)
File "/usr/lib/python2.7/trace.py", line 513, in runctx
exec cmd in globals, locals
File "op25_grc.py", line 493, in
tb = op25_grc()
File "op25_grc.py", line 231, in __init_
self.wxgui_fftsink2_0_0.set_callback(wxgui_fftsink2_0_0_callback)
File "/usr/local/lib/python2.7/dist-pa

Re: Python 3 porting clinic at Pycon 2013

Brett Cannon — 2013-01-14T20:20:32

No, I meant http://docs.python.org/3/howto/pyporting.html

On Mon, Jan 14, 2013 at 5:37 AM, Barry Warsaw <barry-+ZN9ApsXKcEdnm+yROfE0A< at >public.gmane.org> wrote:

Re: Python 3 porting clinic at Pycon 2013

Brett Cannon — 2013-01-12T18:30:38

Why not the porting howto? Still need to re-orient towards common code over
2to3.
On Jan 12, 2013 12:02 PM, "Barry Warsaw" <barry-+ZN9ApsXKcEdnm+yROfE0A< at >public.gmane.org> wrote:

_______________________________________________
Python-porting mailing list
Python-porting-+ZN9ApsXKcEdnm+yROfE0A< at >public.gmane.org
http://mail.python.org/mailman/listinfo/python-porting

Re: Python 3 porting clinic at Pycon 2013

Éric Araujo — 2013-01-14T21:06:10

Le 14/01/2013 05:37, Barry Warsaw a écrit :

I assume Brett was thinking about the Python and C porting howtos in the
official documentation.

Regards
_______________________________________________
Python-porting mailing list
Python-porting< at >python.org
http://mail.python.org/mailman/listinfo/python-porting

Re: Python 3 porting clinic at Pycon 2013

Lennart Regebro — 2013-01-14T20:44:56

Nope. I've though about making that possible, but currently decided
against it. I'm thinking about a second edition though, but I have no
time for the moment.