1 |
On Wednesday 16 October 2013 23:42:26 Arfrever Frehtes Taifersar wrote: |
2 |
> 2013-10-17 04:53 Mike Frysinger napisał(a): |
3 |
> > On Wednesday 16 October 2013 22:51:17 Mike Frysinger wrote: |
4 |
> > > On Wednesday 16 October 2013 20:02:50 Arfrever Frehtes wrote: |
5 |
> > > > 2013-10-16 23:03 Mike Frysinger napisał(a): |
6 |
> > > > > Rather than each module implementing its own shim around the |
7 |
> > > > > various methods for accessing extended attributes, start a |
8 |
> > > > > dedicated module that exports a consistent API. |
9 |
> > > > |
10 |
> > > > Some things are incompatible with Python 3. |
11 |
> > > > See other comments below. |
12 |
> > > |
13 |
> > > i can run a linter on the code (probably should make this a git hook). |
14 |
> > > i'm interested more in review on the bigger picture. |
15 |
> > |
16 |
> > also, none of your comments were py3 issues that i saw |
17 |
> |
18 |
> I said "other comments", so I meant comments not related to incompatibility |
19 |
> with Python 3. |
20 |
|
21 |
well, w/out providing specific concerns, it's hard to address feedback |
22 |
|
23 |
> About incompatibility with Python 3: |
24 |
> - subprocess.check_output(), subprocess.Popen().stdout.read(), |
25 |
> subprocess.Popen().stderr.read() return bytes, which is incorrectly |
26 |
> compared with str in your patches. |
27 |
|
28 |
i've changed the mock code to use subprocess directly so the tests catch this |
29 |
|
30 |
> - dict.iteritems() was renamed to dict.items() (and its return type was |
31 |
> changed from dictionary-itemiterator to dict_items, but it does not matter |
32 |
> here). |
33 |
|
34 |
fixed |
35 |
|
36 |
> - Queue module was renamed to queue. |
37 |
|
38 |
i've sent a patch upstream for this |
39 |
|
40 |
> - cStringIO module should not be used. io module is a replacement available |
41 |
> since Python 2.6. |
42 |
|
43 |
unfortunately, that doesn't work as well as it should. python 2.7's interface |
44 |
is annoyingly different when using other python 2.7 modules. i'll have the |
45 |
code import the old module and then fallback to using the new io module. |
46 |
|
47 |
> - Maybe other problems... |
48 |
|
49 |
sorry, but this isn't useful. i'm going to run the unittests against python |
50 |
3.2 and 3.3 and once those pass, i'm done looking at it. |
51 |
-mike |