1 |
Hello everyone! |
2 |
|
3 |
Since I'm going to reimplement catalyst in GSoC, I'd like to tell my |
4 |
opinion if it has some weight. :-) |
5 |
Some years have passed since Python 3 was created, and nowadays I |
6 |
think it is stable enough to select it. I'd rather thought about |
7 |
Python 2 compatibility than Python 3, since it seems to become a |
8 |
standart soon. To cut a long story short, I'd rather oriented to |
9 |
Python 3 than Python 2, though I prefer to use Python 2 nowadays. Of |
10 |
course compatibility will be one of main aims, but I see some benefit |
11 |
if we will choose Python 3 rather than Python 2, though users may |
12 |
successfully use catalyst with Python 2 in the future. It's just a |
13 |
proposal, so I'd like to hear your opinions. If you don't agree, we |
14 |
may rather think about Python 2. |
15 |
Even more, I'd like to avoid some generators and provide this support |
16 |
manually: I've always hated generators, especially code generators |
17 |
(and GUI ones). |
18 |
|
19 |
What do you think about it? |
20 |
|
21 |
2013/5/21, Brian Dolbec <dolsen@g.o>: |
22 |
> On Mon, 2013-05-20 at 17:06 -0400, Matthew Ruffalo wrote: |
23 |
>> Hi all- |
24 |
>> |
25 |
>> First, thanks for the great tool. I've been using Gentoo for about 10 |
26 |
>> years, and I use Catalyst to build custom Gentoo live CDs that contain |
27 |
>> extra software (e.g. netcat6, rsync, ddrescue, etc.). |
28 |
>> |
29 |
> |
30 |
> Yeah, py3 support is on our list of things todo. We would love to get |
31 |
> help porting. BUT, things are rather slow at getting done at the moment. |
32 |
> I have started a rewrite branch that I am told is what they intend to |
33 |
> change the development branch to. It has been restructured with |
34 |
> numerous other fixes done to clean up the code. There are still a ton |
35 |
> more things to do. |
36 |
> |
37 |
> There are a few of us waiting for the change to happen before doing a |
38 |
> bunch of work that may need rebasing because of other changes done to |
39 |
> the current master. I had that happen once where I did a big re-write |
40 |
> (another project) and it took nearly 4 years to get merged. I had to |
41 |
> rebase numerous times as well as port changes to the new code many |
42 |
> times. :( I also had to migrate the VCS in the midst of it. |
43 |
> |
44 |
> Personally I think it may be better to wait a bit on the py3 |
45 |
> compatibility changes. Many of the potential problem spots will need |
46 |
> fixing anyway, so conversion would likely be smoother after some more |
47 |
> re-write work is done. |
48 |
> |
49 |
> |
50 |
> I hadn't heard of pycharm, I have been using pyflakes and pylint. |
51 |
> I'll check it out. |
52 |
> |
53 |
> |
54 |
> you can get my rewite branch so far at |
55 |
> http://dev.gentoo.org/~dolsen/catalyst/ |
56 |
> |
57 |
> When you clone it, it will compain about not being able to check out |
58 |
> master. You will need to "git checkout re-write". But I would just add |
59 |
> my url as another remote to your current clone and fetch it. |
60 |
> |
61 |
> I have also made changes for the code to be easily run from the |
62 |
> checkout. Edit the testpath file then in the terminal you wish to run |
63 |
> catalyst from: |
64 |
> |
65 |
> source ./tesptath |
66 |
> |
67 |
> |
68 |
>> Thanks for your time and any feedback, |
69 |
>> MMR... |
70 |
> |
71 |
> |
72 |
> |
73 |
> |
74 |
|
75 |
|
76 |
-- |
77 |
With best regards, |
78 |
Dmitry Selyutin |
79 |
|
80 |
E-mail: ghostmansd@×××××.com |
81 |
Phone: +7(985)334-07-70 |