Re: [Zim-wiki] plans for python3? Github?

[Dimitrij Lisov]

Will do, thanks!

Jaap Karssenberg  schrieb am So., 9. Apr. 2017
um 18:13 Uhr:

> Sure go ahead and use the github issue tracker. One thing i would like to
> different though is to keep it more clean and "actionable " than the
> launchpad tracker.
>
> Regards,
>
> Jaap
>
> On Sat, Apr 8, 2017, 13:50 Dimitrij Lisov  wrote:
>
> Great news!
>
> Jaap, would you prefer to have new issues reported on GitHub
>  already, or
> still on Launchpad ?
>
> Best wishes!
>
> Jaap Karssenberg  schrieb am Sa., 8. Apr.
> 2017 um 11:05 Uhr:
>
> Jiri, Brendan, all,
>
> Synchronized latest commit in the bazaar branch to github here:
> https://github.com/jaap-karssenberg/zim-desktop-wiki
>
> Let's use this as a basis for patches and work towards python 3 / gtk 3.
> Until the next release I will sync bazaar to github for each commit. After
> the release wil turn around and sync launchpad from git. So work on git
> will be for the release after this.
>
> Regards,
>
> Jaap
>
>
> On Thu, Mar 23, 2017 at 1:12 AM Brendan Kidwell  wrote:
>
> Added my 'me too' to the Launchpad ticket about migrating to Git format --
> in the 'persons affected' field. My personal reasons probably match
> something someone else already said.
>
> On Mon, Mar 20, 2017, at 17:30, Dimitrij Lisov wrote:
>
> There's already a similar request regarding moving to GitHub:
> https://bugs.launchpad.net/zim/+bug/1639439
>
>
> ___
> Mailing list: https://launchpad.net/~zim-wiki
> Post to : zim-wiki@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~zim-wiki
> More help   : https://help.launchpad.net/ListHelp
>
> ___
> Mailing list: https://launchpad.net/~zim-wiki
> Post to : zim-wiki@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~zim-wiki
> More help   : https://help.launchpad.net/ListHelp
>
>
___
Mailing list: https://launchpad.net/~zim-wiki
Post to : zim-wiki@lists.launchpad.net
Unsubscribe : https://launchpad.net/~zim-wiki
More help   : https://help.launchpad.net/ListHelp

Re: [Zim-wiki] plans for python3? Github?

[Jaap Karssenberg]

Sure go ahead and use the github issue tracker. One thing i would like to
different though is to keep it more clean and "actionable " than the
launchpad tracker.

Regards,

Jaap

On Sat, Apr 8, 2017, 13:50 Dimitrij Lisov  wrote:

> Great news!
>
> Jaap, would you prefer to have new issues reported on GitHub
>  already, or
> still on Launchpad ?
>
> Best wishes!
>
> Jaap Karssenberg  schrieb am Sa., 8. Apr.
> 2017 um 11:05 Uhr:
>
> Jiri, Brendan, all,
>
> Synchronized latest commit in the bazaar branch to github here:
> https://github.com/jaap-karssenberg/zim-desktop-wiki
>
> Let's use this as a basis for patches and work towards python 3 / gtk 3.
> Until the next release I will sync bazaar to github for each commit. After
> the release wil turn around and sync launchpad from git. So work on git
> will be for the release after this.
>
> Regards,
>
> Jaap
>
>
> On Thu, Mar 23, 2017 at 1:12 AM Brendan Kidwell  wrote:
>
> Added my 'me too' to the Launchpad ticket about migrating to Git format --
> in the 'persons affected' field. My personal reasons probably match
> something someone else already said.
>
> On Mon, Mar 20, 2017, at 17:30, Dimitrij Lisov wrote:
>
> There's already a similar request regarding moving to GitHub:
> https://bugs.launchpad.net/zim/+bug/1639439
>
>
> ___
> Mailing list: https://launchpad.net/~zim-wiki
> Post to : zim-wiki@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~zim-wiki
> More help   : https://help.launchpad.net/ListHelp
>
> ___
> Mailing list: https://launchpad.net/~zim-wiki
> Post to : zim-wiki@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~zim-wiki
> More help   : https://help.launchpad.net/ListHelp
>
>
___
Mailing list: https://launchpad.net/~zim-wiki
Post to : zim-wiki@lists.launchpad.net
Unsubscribe : https://launchpad.net/~zim-wiki
More help   : https://help.launchpad.net/ListHelp

Re: [Zim-wiki] plans for python3? Github?

[Dimitrij Lisov]

Great news!

Jaap, would you prefer to have new issues reported on GitHub
 already, or
still on Launchpad ?

Best wishes!

Jaap Karssenberg  schrieb am Sa., 8. Apr. 2017
um 11:05 Uhr:

> Jiri, Brendan, all,
>
> Synchronized latest commit in the bazaar branch to github here:
> https://github.com/jaap-karssenberg/zim-desktop-wiki
>
> Let's use this as a basis for patches and work towards python 3 / gtk 3.
> Until the next release I will sync bazaar to github for each commit. After
> the release wil turn around and sync launchpad from git. So work on git
> will be for the release after this.
>
> Regards,
>
> Jaap
>
>
> On Thu, Mar 23, 2017 at 1:12 AM Brendan Kidwell  wrote:
>
> Added my 'me too' to the Launchpad ticket about migrating to Git format --
> in the 'persons affected' field. My personal reasons probably match
> something someone else already said.
>
> On Mon, Mar 20, 2017, at 17:30, Dimitrij Lisov wrote:
>
> There's already a similar request regarding moving to GitHub:
> https://bugs.launchpad.net/zim/+bug/1639439
>
>
> ___
> Mailing list: https://launchpad.net/~zim-wiki
> Post to : zim-wiki@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~zim-wiki
> More help   : https://help.launchpad.net/ListHelp
>
> ___
> Mailing list: https://launchpad.net/~zim-wiki
> Post to : zim-wiki@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~zim-wiki
> More help   : https://help.launchpad.net/ListHelp
>
___
Mailing list: https://launchpad.net/~zim-wiki
Post to : zim-wiki@lists.launchpad.net
Unsubscribe : https://launchpad.net/~zim-wiki
More help   : https://help.launchpad.net/ListHelp

Re: [Zim-wiki] plans for python3? Github?

[Jaap Karssenberg]

Jiri, Brendan, all,

Synchronized latest commit in the bazaar branch to github here:
https://github.com/jaap-karssenberg/zim-desktop-wiki

Let's use this as a basis for patches and work towards python 3 / gtk 3.
Until the next release I will sync bazaar to github for each commit. After
the release wil turn around and sync launchpad from git. So work on git
will be for the release after this.

Regards,

Jaap


On Thu, Mar 23, 2017 at 1:12 AM Brendan Kidwell  wrote:

> Added my 'me too' to the Launchpad ticket about migrating to Git format --
> in the 'persons affected' field. My personal reasons probably match
> something someone else already said.
>
> On Mon, Mar 20, 2017, at 17:30, Dimitrij Lisov wrote:
>
> There's already a similar request regarding moving to GitHub:
> https://bugs.launchpad.net/zim/+bug/1639439
>
>
> ___
> Mailing list: https://launchpad.net/~zim-wiki
> Post to : zim-wiki@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~zim-wiki
> More help   : https://help.launchpad.net/ListHelp
>
___
Mailing list: https://launchpad.net/~zim-wiki
Post to : zim-wiki@lists.launchpad.net
Unsubscribe : https://launchpad.net/~zim-wiki
More help   : https://help.launchpad.net/ListHelp

Re: [Zim-wiki] plans for python3?

[Jiří Janoušek]

Hello Jaap,

> I'm still planning a release to be made in April, prefer to start on that
> code base. Current status here:
> https://code.launchpad.net/~jaap.karssenberg/zim/zim-refactor will make it
> pass test suite again next week, after that smaller patches until release.
> Will do an export to github when I reach the point all tests pass again.
>
> Also I will take the task to further untangle the main gui modules such that
> it becomes easier to port module by module. Basically will move out more
> core functions to plugins that can be loaded ad hoc. And I should probably
> help cleaning up the code documentation: current API docs do not compile, so
> want to convert to spinx and get them back online.

I totally agree with the proposed steps.

> With respect to type hints I have no experience, but willing to give it a
> go. My tooling is pretty basic, just a code editor and a unix shell :)

I used to develop with only geany and shell, but then I tried PyCharm
Community Edition and fell in love immediately. The mypy checker can
be used from shell, so we could try it and discard the annotations if
you don't like it.

> For the last phase there is also a pygtk to gi script available. Not even
> close to full conversion, but handles the basic search and replace to start
> with. Could be helpful.

That's a good idea.

> Per phase we should probably keep track of who-is-doing-what to avoid
> difficult merges. And we need to set up a smaller mail group to coordinate
> the work with a low threshold of asking detail questions on the code base.
> Maybe both can be facilitated through the github issue tracker ?

Who-is-doing-what could be tracked via GitHub issues:
* Each task is one issue
* Issues can be assigned
* It is possible to create a "project", which is a board that contains
only a subset of issues related to a particular topic (e.g. [1],
columns are editable).

We could create one master issue (e.g. "Port to Python3") for general
discussion and questions.

[1]: https://github.com/tiliado/nuvolaplayer/projects

Best regards,

Jiri Janousek

___
Mailing list: https://launchpad.net/~zim-wiki
Post to : zim-wiki@lists.launchpad.net
Unsubscribe : https://launchpad.net/~zim-wiki
More help   : https://help.launchpad.net/ListHelp

Re: [Zim-wiki] plans for python3? Github?

[Brendan Kidwell]

Added my 'me too' to the Launchpad ticket about migrating to Git format
-- in the 'persons affected' field. My personal reasons probably match
something someone else already said.


On Mon, Mar 20, 2017, at 17:30, Dimitrij Lisov wrote:

> There's already a similar request regarding moving to GitHub:
> https://bugs.launchpad.net/zim/+bug/1639439

___
Mailing list: https://launchpad.net/~zim-wiki
Post to : zim-wiki@lists.launchpad.net
Unsubscribe : https://launchpad.net/~zim-wiki
More help   : https://help.launchpad.net/ListHelp

Re: [Zim-wiki] plans for python3?

[Jaap Karssenberg]

Hi Jiri,

Thanks for thinking this through in detail.

I'm still planning a release to be made in April, prefer to start on that
code base. Current status here:
https://code.launchpad.net/~jaap.karssenberg/zim/zim-refactor will make it
pass test suite again next week, after that smaller patches until release.
Will do an export to github when I reach the point all tests pass again.

Also I will take the task to further untangle the main gui modules such
that it becomes easier to port module by module. Basically will move out
more core functions to plugins that can be loaded ad hoc. And I should
probably help cleaning up the code documentation: current API docs do not
compile, so want to convert to spinx and get them back online.

With respect to type hints I have no experience, but willing to give it a
go. My tooling is pretty basic, just a code editor and a unix shell :)

For the last phase there is also a pygtk to gi script available. Not even
close to full conversion, but handles the basic search and replace to start
with. Could be helpful.

Per phase we should probably keep track of who-is-doing-what to avoid
difficult merges. And we need to set up a smaller mail group to coordinate
the work with a low threshold of asking detail questions on the code base.
Maybe both can be facilitated through the github issue tracker ?

Regards,

Jaap


On Mon, Mar 20, 2017 at 3:45 PM Jiří Janoušek 
wrote:

> Hello Jaap,
>
> I would prefer to port to both GTK 3 and Python 3 in one go (2) after
> a thorough preparatory phase (1). Here are my thoughts:
>
> (1) The first phase - Forward-compatible Python 2.7
>
> # Goal:
>
> To make the Python 2 codebase as much forward compatible with Python 3
> as possible, identify tricky code and (for me) to get familiar with
> the codebase.
>
> # Key requirements:
>
> - Zim is stable and fully functional.
> - It is still possible to add new features, fix bugs and make releases.
> - A working branch (py27?) can be regularly merged to the trunk after
> a code review.
>
> # Plan
>
> a) We should study the incompatibilities between Python 2 and 3 (e.g.
> [1][2]) and review the whole Zim codebase file by file. If the
> incompatibility can be solved with a forward-compatible Python 2.7
> code (e.g. `except KeyError as e:` istead of `except KeyError, e:`),
> port it immediately. Otherwise mark it with `# py2!` (optionally with
> a description).
>
> [1]: http://python-future.org/compatible_idioms.html
> [2]: http://python3porting.com/
>
> b) We should use `from __future__ import ...` features such as
> print_function, unicode_literals, division and absolute_import.
>
> c) We may run Zim with `python -3` option to enable extra warnings.
>
> d) We should port Zim to the new PyGTK 2.24 APIs (e.g. widget.window →
> widget.get_window(), container.child → container.get_child(), etc.) to
> make it compatible with PyGTKCompat [3].
>
> [3]: https://wiki.gnome.org/Projects/PyGObject/PyGTKCompat
>
> e) I propose using a Python-2 compatible variant of type hints [4][5].
> I use them a lot in my Python 3 + GTK+ 3 project at work and they have
> proved to be really useful as the PyCharm IDE supports them quite well
> (including the free Community Edition). It can even generate
> type-checking stubs for GTK+. I don't know what is your tooling but
> the mypy type checker can be used independently. There is no extra
> run-time dependency as the typing module is necessary only during the
> static type analysis.
>
> [4]: http://mypy.readthedocs.io/en/latest/python2.html
> [5]: https://www.python.org/dev/peps/pep-0484/
>
> If you are not fond of the type annotations, we may strip them off
> easily after porting (regex "#\s*type:\s+.*$"). However, I believe the
> annotations will help me to get familiar with the code and should spot
> some (but not all) errors without the need to run Zim again and again.
>
> # Outcome
>
> After this first phase, we will have a fully functional Python 2.7
> version of Zim. We may even keep it around as a LTS release for users
> who cannot switch to Python 3.
>
> (2) The second phase - Python 3 and GTK 3 port
>
> # Goal
>
> To port Zim to Python 3 and Gtk3 in one go
>
> # Plan
>
> - Decide on a minimal Python 3 and GTK+ 3 version. Python 3.4 is
> available in Debian Jessie and Ubuntu 14.04 LTS, Python 3.5 in Debian
> Stretch and Ubuntu 16.04 LTS.
> - A new branch is created.
> - All plugins and non-essential modules are disabled.
> - We may try to run Python's 2to3 script. I don't know how useful it
> actually is.
> - All code marked with # py2! is ported manually.
> - PyGTKCompat [3] module is used to get the app running fast and then
> GUI is ported flle-by-file to PyGObject GTK+ 3.
>
> Best regards,
>
> Jiri Janousek
>
> On Tue, Mar 14, 2017 at 12:22 PM, Jaap Karssenberg
>  wrote:
> > Hi Jiri,
> >
> > Would like to take you on on that offer. I will set up a branch to be
> used
> > for porting (I have a preferred starting point, not current trunk).
> >
> > Strategy wise I believe

Re: [Zim-wiki] plans for python3?

[Murat Güven]

count me in. I'm happy to support with code review / update.

Regards,
Murat

On 20.03.2017 15:44, Jiří Janoušek wrote:

Hello Jaap,

I would prefer to port to both GTK 3 and Python 3 in one go (2) after
a thorough preparatory phase (1). Here are my thoughts:

(1) The first phase - Forward-compatible Python 2.7

# Goal:

To make the Python 2 codebase as much forward compatible with Python 3
as possible, identify tricky code and (for me) to get familiar with
the codebase.

# Key requirements:

- Zim is stable and fully functional.
- It is still possible to add new features, fix bugs and make releases.
- A working branch (py27?) can be regularly merged to the trunk after
a code review.

# Plan

a) We should study the incompatibilities between Python 2 and 3 (e.g.
[1][2]) and review the whole Zim codebase file by file. If the
incompatibility can be solved with a forward-compatible Python 2.7
code (e.g. `except KeyError as e:` istead of `except KeyError, e:`),
port it immediately. Otherwise mark it with `# py2!` (optionally with
a description).

[1]: http://python-future.org/compatible_idioms.html
[2]: http://python3porting.com/

b) We should use `from __future__ import ...` features such as
print_function, unicode_literals, division and absolute_import.

c) We may run Zim with `python -3` option to enable extra warnings.

d) We should port Zim to the new PyGTK 2.24 APIs (e.g. widget.window →
widget.get_window(), container.child → container.get_child(), etc.) to
make it compatible with PyGTKCompat [3].

[3]: https://wiki.gnome.org/Projects/PyGObject/PyGTKCompat

e) I propose using a Python-2 compatible variant of type hints [4][5].
I use them a lot in my Python 3 + GTK+ 3 project at work and they have
proved to be really useful as the PyCharm IDE supports them quite well
(including the free Community Edition). It can even generate
type-checking stubs for GTK+. I don't know what is your tooling but
the mypy type checker can be used independently. There is no extra
run-time dependency as the typing module is necessary only during the
static type analysis.

[4]: http://mypy.readthedocs.io/en/latest/python2.html
[5]: https://www.python.org/dev/peps/pep-0484/

If you are not fond of the type annotations, we may strip them off
easily after porting (regex "#\s*type:\s+.*$"). However, I believe the
annotations will help me to get familiar with the code and should spot
some (but not all) errors without the need to run Zim again and again.

# Outcome

After this first phase, we will have a fully functional Python 2.7
version of Zim. We may even keep it around as a LTS release for users
who cannot switch to Python 3.

(2) The second phase - Python 3 and GTK 3 port

# Goal

To port Zim to Python 3 and Gtk3 in one go

# Plan

- Decide on a minimal Python 3 and GTK+ 3 version. Python 3.4 is
available in Debian Jessie and Ubuntu 14.04 LTS, Python 3.5 in Debian
Stretch and Ubuntu 16.04 LTS.
- A new branch is created.
- All plugins and non-essential modules are disabled.
- We may try to run Python's 2to3 script. I don't know how useful it
actually is.
- All code marked with # py2! is ported manually.
- PyGTKCompat [3] module is used to get the app running fast and then
GUI is ported flle-by-file to PyGObject GTK+ 3.

Best regards,

Jiri Janousek

On Tue, Mar 14, 2017 at 12:22 PM, Jaap Karssenberg
 wrote:

Hi Jiri,

Would like to take you on on that offer. I will set up a branch to be used
for porting (I have a preferred starting point, not current trunk).

Strategy wise I believe we need to go to Gtk3 before we can go to Python3,
so that will be 2 phases.
For the first step going to Gtk3 I would like to split up the application in
modules. Trying to get the basic application running first, than port
additional modules and plugins one-by-one.

Let's simply use a wiki page to track progress and who-does-what. I prefer
(private) email for quick questions / discussions.

Is this what you had in mind?

Regards,

Jaap


On Sat, Mar 11, 2017 at 7:39 PM Jiří Janoušek 
wrote:

Yes, I have plans to port zim to python 3, but can't commit to a
concrete
timeline on this moment.

I might help with the porting to Python 3 & GTK+ 3. What is the best
place to discuss the strategy? Mailing list, bug tracker or Launchpad
blueprints? I prefer the bug tracker.

Best regards,

Jiri Janousek

___
Mailing list: https://launchpad.net/~zim-wiki
Post to : zim-wiki@lists.launchpad.net
Unsubscribe : https://launchpad.net/~zim-wiki
More help   : https://help.launchpad.net/ListHelp

___
Mailing list: https://launchpad.net/~zim-wiki
Post to : zim-wiki@lists.launchpad.net
Unsubscribe : https://launchpad.net/~zim-wiki
More help   : https://help.launchpad.net/ListHelp



___
Mailing list: https://launchpad.net/~zim-wiki
Post to : zim-wiki@lists.launchpad.net
Unsubscribe : https://launchpad.net/~zim-wiki
More help   : h

Re: [Zim-wiki] plans for python3? Github?

[Dimitrij Lisov]

There's already a similar request regarding moving to GitHub:
https://bugs.launchpad.net/zim/+bug/1639439

Ari  schrieb am Mi., 15. März 2017 um 14:39 Uhr:

> Yet another +1 for github. Also willing to collaborate with the gtk3 and
> python3 porting. Not a Dev but some basic skills on both python and gtk,
> and familiar with github.
> Zim is my daily driver for notes, Linux (fedora) and Windows. Willing to
> help move it forward.
>
> On Mar 14, 2017 1:04 PM, "Johannes Kirschner" 
> wrote:
>
> +1 for github. When I was implementing the move-line features I was
> basically spending half a day figuring out how bazaar works. And to fix a
> bug a few weeks later, I basically had to look up everything again.
>
> Johannes
>
> On 03/14/2017 05:03 PM, Dimitrij Lisov wrote:
>
> Alex, I totally agree with you. GitHub is much more appealing and should
> attract more contributers.
>
> Alex Ivkin  schrieb am Di., 14. März 2017 um 16:52 Uhr:
>
> Jaap,
>
> While you are at it, could you consider moving the codebase to GitHub? It
> is so much more convenient to have it there.
>
> Having to deal with bazaar is what prevented me from submitting many more
> patches.
> *Alex*
>
>
> --
> *From:* Jaap Karssenberg
> *Sent:* Tuesday, March 14, 2017 4:22AM
> *To:* Jiří Janoušek, Zim-wiki
> *Subject:* Re: [Zim-wiki] plans for python3?
>
> Hi Jiri,
>
> Would like to take you on on that offer. I will set up a branch to be used
> for porting (I have a preferred starting point, not current trunk).
>
> Strategy wise I believe we need to go to Gtk3 before we can go to Python3,
> so that will be 2 phases.
> For the first step going to Gtk3 I would like to split up the application
> in modules. Trying to get the basic application running first, than port
> additional modules and plugins one-by-one.
>
> Let's simply use a wiki page to track progress and who-does-what. I prefer
> (private) email for quick questions / discussions.
>
> Is this what you had in mind?
>
> Regards,
>
> Jaap
>
>
> On Sat, Mar 11, 2017 at 7:39 PM Jiří Janoušek 
> wrote:
>
> > Yes, I have plans to port zim to python 3, but can't commit to a concrete
> > timeline on this moment.
>
> I might help with the porting to Python 3 & GTK+ 3. What is the best
> place to discuss the strategy? Mailing list, bug tracker or Launchpad
> blueprints? I prefer the bug tracker.
>
> Best regards,
>
> Jiri Janousek
>
> ___
> Mailing list: https://launchpad.net/~zim-wiki
> Post to : zim-wiki@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~zim-wiki
> More help   : https://help.launchpad.net/ListHelp
>
>
>
> ___
> Mailing list: https://launchpad.net/~zim-wiki
> Post to : zim-wiki@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~zim-wiki
> More help   : https://help.launchpad.net/ListHelp
>
>
> ___
> Mailing list: https://launchpad.net/~zim-wiki
> Post to : zim-wiki@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~zim-wiki
> More help   : https://help.launchpad.net/ListHelp
>
>
>
> ___
> Mailing list: https://launchpad.net/~zim-wiki
> Post to : zim-wiki@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~zim-wiki
> More help   : https://help.launchpad.net/ListHelp
>
>
>
> ___
> Mailing list: https://launchpad.net/~zim-wiki
> Post to : zim-wiki@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~zim-wiki
> More help   : https://help.launchpad.net/ListHelp
>
> ___
> Mailing list: https://launchpad.net/~zim-wiki
> Post to : zim-wiki@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~zim-wiki
> More help   : https://help.launchpad.net/ListHelp
>
___
Mailing list: https://launchpad.net/~zim-wiki
Post to : zim-wiki@lists.launchpad.net
Unsubscribe : https://launchpad.net/~zim-wiki
More help   : https://help.launchpad.net/ListHelp

Re: [Zim-wiki] plans for python3?

[Jiří Janoušek]

Hello Jaap,

I would prefer to port to both GTK 3 and Python 3 in one go (2) after
a thorough preparatory phase (1). Here are my thoughts:

(1) The first phase - Forward-compatible Python 2.7

# Goal:

To make the Python 2 codebase as much forward compatible with Python 3
as possible, identify tricky code and (for me) to get familiar with
the codebase.

# Key requirements:

- Zim is stable and fully functional.
- It is still possible to add new features, fix bugs and make releases.
- A working branch (py27?) can be regularly merged to the trunk after
a code review.

# Plan

a) We should study the incompatibilities between Python 2 and 3 (e.g.
[1][2]) and review the whole Zim codebase file by file. If the
incompatibility can be solved with a forward-compatible Python 2.7
code (e.g. `except KeyError as e:` istead of `except KeyError, e:`),
port it immediately. Otherwise mark it with `# py2!` (optionally with
a description).

[1]: http://python-future.org/compatible_idioms.html
[2]: http://python3porting.com/

b) We should use `from __future__ import ...` features such as
print_function, unicode_literals, division and absolute_import.

c) We may run Zim with `python -3` option to enable extra warnings.

d) We should port Zim to the new PyGTK 2.24 APIs (e.g. widget.window →
widget.get_window(), container.child → container.get_child(), etc.) to
make it compatible with PyGTKCompat [3].

[3]: https://wiki.gnome.org/Projects/PyGObject/PyGTKCompat

e) I propose using a Python-2 compatible variant of type hints [4][5].
I use them a lot in my Python 3 + GTK+ 3 project at work and they have
proved to be really useful as the PyCharm IDE supports them quite well
(including the free Community Edition). It can even generate
type-checking stubs for GTK+. I don't know what is your tooling but
the mypy type checker can be used independently. There is no extra
run-time dependency as the typing module is necessary only during the
static type analysis.

[4]: http://mypy.readthedocs.io/en/latest/python2.html
[5]: https://www.python.org/dev/peps/pep-0484/

If you are not fond of the type annotations, we may strip them off
easily after porting (regex "#\s*type:\s+.*$"). However, I believe the
annotations will help me to get familiar with the code and should spot
some (but not all) errors without the need to run Zim again and again.

# Outcome

After this first phase, we will have a fully functional Python 2.7
version of Zim. We may even keep it around as a LTS release for users
who cannot switch to Python 3.

(2) The second phase - Python 3 and GTK 3 port

# Goal

To port Zim to Python 3 and Gtk3 in one go

# Plan

- Decide on a minimal Python 3 and GTK+ 3 version. Python 3.4 is
available in Debian Jessie and Ubuntu 14.04 LTS, Python 3.5 in Debian
Stretch and Ubuntu 16.04 LTS.
- A new branch is created.
- All plugins and non-essential modules are disabled.
- We may try to run Python's 2to3 script. I don't know how useful it
actually is.
- All code marked with # py2! is ported manually.
- PyGTKCompat [3] module is used to get the app running fast and then
GUI is ported flle-by-file to PyGObject GTK+ 3.

Best regards,

Jiri Janousek

On Tue, Mar 14, 2017 at 12:22 PM, Jaap Karssenberg
 wrote:
> Hi Jiri,
>
> Would like to take you on on that offer. I will set up a branch to be used
> for porting (I have a preferred starting point, not current trunk).
>
> Strategy wise I believe we need to go to Gtk3 before we can go to Python3,
> so that will be 2 phases.
> For the first step going to Gtk3 I would like to split up the application in
> modules. Trying to get the basic application running first, than port
> additional modules and plugins one-by-one.
>
> Let's simply use a wiki page to track progress and who-does-what. I prefer
> (private) email for quick questions / discussions.
>
> Is this what you had in mind?
>
> Regards,
>
> Jaap
>
>
> On Sat, Mar 11, 2017 at 7:39 PM Jiří Janoušek 
> wrote:
>>
>> > Yes, I have plans to port zim to python 3, but can't commit to a
>> > concrete
>> > timeline on this moment.
>>
>> I might help with the porting to Python 3 & GTK+ 3. What is the best
>> place to discuss the strategy? Mailing list, bug tracker or Launchpad
>> blueprints? I prefer the bug tracker.
>>
>> Best regards,
>>
>> Jiri Janousek
>>
>> ___
>> Mailing list: https://launchpad.net/~zim-wiki
>> Post to : zim-wiki@lists.launchpad.net
>> Unsubscribe : https://launchpad.net/~zim-wiki
>> More help   : https://help.launchpad.net/ListHelp

___
Mailing list: https://launchpad.net/~zim-wiki
Post to : zim-wiki@lists.launchpad.net
Unsubscribe : https://launchpad.net/~zim-wiki
More help   : https://help.launchpad.net/ListHelp

Re: [Zim-wiki] plans for python3? Github?

[Ari]

Yet another +1 for github. Also willing to collaborate with the gtk3 and
python3 porting. Not a Dev but some basic skills on both python and gtk,
and familiar with github.
Zim is my daily driver for notes, Linux (fedora) and Windows. Willing to
help move it forward.

On Mar 14, 2017 1:04 PM, "Johannes Kirschner" 
wrote:

> +1 for github. When I was implementing the move-line features I was
> basically spending half a day figuring out how bazaar works. And to fix a
> bug a few weeks later, I basically had to look up everything again.
>
> Johannes
>
> On 03/14/2017 05:03 PM, Dimitrij Lisov wrote:
>
> Alex, I totally agree with you. GitHub is much more appealing and should
> attract more contributers.
>
> Alex Ivkin  schrieb am Di., 14. März 2017 um 16:52 Uhr:
>
>> Jaap,
>>
>> While you are at it, could you consider moving the codebase to GitHub? It
>> is so much more convenient to have it there.
>>
>> Having to deal with bazaar is what prevented me from submitting many more
>> patches.
>> *Alex*
>>
>>
>> --
>> *From:* Jaap Karssenberg
>> *Sent:* Tuesday, March 14, 2017 4:22AM
>> *To:* Jiří Janoušek, Zim-wiki
>> *Subject:* Re: [Zim-wiki] plans for python3?
>>
>> Hi Jiri,
>>
>> Would like to take you on on that offer. I will set up a branch to be
>> used for porting (I have a preferred starting point, not current trunk).
>>
>> Strategy wise I believe we need to go to Gtk3 before we can go to
>> Python3, so that will be 2 phases.
>> For the first step going to Gtk3 I would like to split up the application
>> in modules. Trying to get the basic application running first, than port
>> additional modules and plugins one-by-one.
>>
>> Let's simply use a wiki page to track progress and who-does-what. I
>> prefer (private) email for quick questions / discussions.
>>
>> Is this what you had in mind?
>>
>> Regards,
>>
>> Jaap
>>
>>
>> On Sat, Mar 11, 2017 at 7:39 PM Jiří Janoušek 
>> wrote:
>>
>> > Yes, I have plans to port zim to python 3, but can't commit to a
>> concrete
>> > timeline on this moment.
>>
>> I might help with the porting to Python 3 & GTK+ 3. What is the best
>> place to discuss the strategy? Mailing list, bug tracker or Launchpad
>> blueprints? I prefer the bug tracker.
>>
>> Best regards,
>>
>> Jiri Janousek
>>
>> ___
>> Mailing list: https://launchpad.net/~zim-wiki
>> Post to : zim-wiki@lists.launchpad.net
>> Unsubscribe : https://launchpad.net/~zim-wiki
>> More help   : https://help.launchpad.net/ListHelp
>>
>>
>>
>> ___
>> Mailing list: https://launchpad.net/~zim-wiki
>> Post to : zim-wiki@lists.launchpad.net
>> Unsubscribe : https://launchpad.net/~zim-wiki
>> More help   : https://help.launchpad.net/ListHelp
>>
>>
>> ___
>> Mailing list: https://launchpad.net/~zim-wiki
>> Post to : zim-wiki@lists.launchpad.net
>> Unsubscribe : https://launchpad.net/~zim-wiki
>> More help   : https://help.launchpad.net/ListHelp
>>
>
>
> ___
> Mailing list: https://launchpad.net/~zim-wiki
> Post to : zim-wiki@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~zim-wiki
> More help   : https://help.launchpad.net/ListHelp
>
>
>
> ___
> Mailing list: https://launchpad.net/~zim-wiki
> Post to : zim-wiki@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~zim-wiki
> More help   : https://help.launchpad.net/ListHelp
>
>
___
Mailing list: https://launchpad.net/~zim-wiki
Post to : zim-wiki@lists.launchpad.net
Unsubscribe : https://launchpad.net/~zim-wiki
More help   : https://help.launchpad.net/ListHelp

Re: [Zim-wiki] plans for python3? Github?

[Mukli Krisztián]

 

Hi!!! 

+1 for GTK3, +1 for Python3, +1 for Git, +1 for Github 

I'm not insist on any of the mentioned solution, but this way is may
result faster development and more contributors, in my opinion. 
---
MUKLI KRISZTIÁN 

15.03.2017 08:12 időpontban Kiriarat ezt írta: 

> +1 for Git, -1 for Github
> 
> Many Gitlab or Googs instances exists...
> 
> kr
> 
> Le 14/03/2017 à 18:20, Tomasz Muras a écrit : Just to add "me too" - please 
> switch to git.
> 
> Tomek
> 
> On 14 Mar 2017 18:04, "Johannes Kirschner"  <mailto:m...@johannes-kirschner.de>> wrote:
> 
> +1 for github. When I was implementing the move-line features I
> was basically spending half a day figuring out how bazaar works.
> And to fix a bug a few weeks later, I basically had to look up
> everything again.
> 
> Johannes
> 
> On 03/14/2017 05:03 PM, Dimitrij Lisov wrote: Alex, I totally agree with you. 
> GitHub is much more appealing and
> should attract more contributers.
> 
> Alex Ivkin mailto:a...@ivkin.net>> schrieb am
> Di., 14. März 2017 um 16:52 Uhr:
> 
> Jaap,
> 
> While you are at it, could you consider moving the codebase
> to GitHub? It is so much more convenient to have it there.
> 
> Having to deal with bazaar is what prevented me from
> submitting many more patches.
> 
> *Alex*
> 
> --------------------
> *From:* Jaap Karssenberg
> *Sent:* Tuesday, March 14, 2017 4:22AM
> *To:* Jiří Janoušek, Zim-wiki
> *Subject:* Re: [Zim-wiki] plans for python3?
> 
> Hi Jiri,
> 
> Would like to take you on on that offer. I will set up a
> branch to be used for porting (I have a preferred starting
> point, not current trunk).
> 
> Strategy wise I believe we need to go to Gtk3 before we can
> go to Python3, so that will be 2 phases.
> For the first step going to Gtk3 I would like to split up
> the application in modules. Trying to get the basic
> application running first, than port additional modules and
> plugins one-by-one.
> 
> Let's simply use a wiki page to track progress and
> who-does-what. I prefer (private) email for quick questions
> / discussions.
> 
> Is this what you had in mind?
> 
> Regards,
> 
> Jaap
> 
> On Sat, Mar 11, 2017 at 7:39 PM Jiří Janoušek
> mailto:janousek.j...@gmail.com>>
> wrote:
> 
>> Yes, I have plans to port zim to python 3, but can't
> commit to a concrete
>> timeline on this moment.
> 
> I might help with the porting to Python 3 & GTK+ 3. What
> is the best
> place to discuss the strategy? Mailing list, bug tracker
> or Launchpad
> blueprints? I prefer the bug tracker.
> 
> Best regards,
> 
> Jiri Janousek
> 
> ___
> Mailing list: https://launchpad.net/~zim-wiki [1]
> <https://launchpad.net/%7Ezim-wiki [2]>
> Post to : zim-wiki@lists.launchpad.net
> <mailto:zim-wiki@lists.launchpad.net>
> Unsubscribe : https://launchpad.net/~zim-wiki [1]
> <https://launchpad.net/%7Ezim-wiki [2]>
> More help : https://help.launchpad.net/ListHelp [3]
> <https://help.launchpad.net/ListHelp [3]>
> 
> ___
> Mailing list:https://launchpad.net/~zim-wiki [1]
> <https://launchpad.net/%7Ezim-wiki [2]>
> Post to :zim-wiki@lists.launchpad.net
> <mailto:zim-wiki@lists.launchpad.net>
> Unsubscribe :https://launchpad.net/~zim-wiki [1]
> <https://launchpad.net/%7Ezim-wiki [2]>
> More help :https://help.launchpad.net/ListHelp [3]
> <https://help.launchpad.net/ListHelp [3]> 
> ___ Mailing list:
> https://launchpad.net/~zim-wiki [1]
> <https://launchpad.net/%7Ezim-wiki [2]> Post to :
> zim-wiki@lists.launchpad.net
> <mailto:zim-wiki@lists.launchpad.net> Unsubscribe :
> https://launchpad.net/~zim-wiki [1]
> <https://launchpad.net/%7Ezim-wiki [2]> More help :
> https://help.launchpad.net/ListHelp [3]
> <https://help.launchpad.net/ListHelp [3]> 
> ___
> Mailing list:https://launchpad.net/~zim-wiki [1] 
> <https://launchpad.net/%7Ezim-wiki [2]>
> Post to :zim-wiki@lists.launchpad.net <mailto:zim-wiki@lists.launchpad.net>
> Unsubscribe :https://launchpad.net/~zim-wiki [1] 
> <https://launchpad.net/%7Ezim-wiki [2]>
> More help :https://help.launchpad.net/ListHelp [3]
> <https://help.launchpad.net/ListHelp [3]>

 ___ Mailing list:
 https://launchpad.net/~zim-wiki [1]
 <https://launchpad.net/%7Ezim-wiki [2]> Post to :
 zim-wiki@lists.launchpad.net <mailto:zim-wiki@li

Re: [Zim-wiki] plans for python3? Github?

[Kiriarat]

+1 for Git, -1 for Github

Many Gitlab or Googs instances exists…

kr

Le 14/03/2017 à 18:20, Tomasz Muras a écrit :

Just to add "me too" - please switch to git.

Tomek

On 14 Mar 2017 18:04, "Johannes Kirschner" <mailto:m...@johannes-kirschner.de>> wrote:


+1 for github. When I was implementing the move-line features I
was basically spending half a day figuring out how bazaar works.
And to fix a bug a few weeks later, I basically had to look up
everything again.

Johannes

On 03/14/2017 05:03 PM, Dimitrij Lisov wrote:

Alex, I totally agree with you. GitHub is much more appealing and
should attract more contributers.

Alex Ivkin mailto:a...@ivkin.net>> schrieb am
Di., 14. März 2017 um 16:52 Uhr:

Jaap,

While you are at it, could you consider moving the codebase
to GitHub? It is so much more convenient to have it there.

Having to deal with bazaar is what prevented me from
submitting many more patches.

*Alex*



*From:* Jaap Karssenberg
*Sent:* Tuesday, March 14, 2017 4:22AM
*To:* Jiří Janoušek, Zim-wiki
    *Subject:* Re: [Zim-wiki] plans for python3?


Hi Jiri,

Would like to take you on on that offer. I will set up a
branch to be used for porting (I have a preferred starting
point, not current trunk).

Strategy wise I believe we need to go to Gtk3 before we can
go to Python3, so that will be 2 phases.
For the first step going to Gtk3 I would like to split up
the application in modules. Trying to get the basic
application running first, than port additional modules and
plugins one-by-one.

Let's simply use a wiki page to track progress and
who-does-what. I prefer (private) email for quick questions
/ discussions.

Is this what you had in mind?

Regards,

Jaap


On Sat, Mar 11, 2017 at 7:39 PM Jiří Janoušek
mailto:janousek.j...@gmail.com>>
wrote:

> Yes, I have plans to port zim to python 3, but can't
commit to a concrete
> timeline on this moment.

I might help with the porting to Python 3 & GTK+ 3. What
is the best
place to discuss the strategy? Mailing list, bug tracker
or Launchpad
blueprints? I prefer the bug tracker.

Best regards,

Jiri Janousek

___
Mailing list: https://launchpad.net/~zim-wiki
<https://launchpad.net/%7Ezim-wiki>
Post to : zim-wiki@lists.launchpad.net
<mailto:zim-wiki@lists.launchpad.net>
Unsubscribe : https://launchpad.net/~zim-wiki
<https://launchpad.net/%7Ezim-wiki>
More help   : https://help.launchpad.net/ListHelp
<https://help.launchpad.net/ListHelp>



___
Mailing list:https://launchpad.net/~zim-wiki
<https://launchpad.net/%7Ezim-wiki>
Post to :zim-wiki@lists.launchpad.net
<mailto:zim-wiki@lists.launchpad.net>
Unsubscribe :https://launchpad.net/~zim-wiki
<https://launchpad.net/%7Ezim-wiki>
More help   :https://help.launchpad.net/ListHelp
<https://help.launchpad.net/ListHelp>

___ Mailing list:
https://launchpad.net/~zim-wiki
<https://launchpad.net/%7Ezim-wiki> Post to :
zim-wiki@lists.launchpad.net
<mailto:zim-wiki@lists.launchpad.net> Unsubscribe :
https://launchpad.net/~zim-wiki
<https://launchpad.net/%7Ezim-wiki> More help   :
https://help.launchpad.net/ListHelp
<https://help.launchpad.net/ListHelp> 


___
Mailing list:https://launchpad.net/~zim-wiki 
<https://launchpad.net/%7Ezim-wiki>
Post to :zim-wiki@lists.launchpad.net 
<mailto:zim-wiki@lists.launchpad.net>
Unsubscribe :https://launchpad.net/~zim-wiki 
<https://launchpad.net/%7Ezim-wiki>
More help   :https://help.launchpad.net/ListHelp
<https://help.launchpad.net/ListHelp>


___ Mailing list:
https://launchpad.net/~zim-wiki
<https://launchpad.net/%7Ezim-wiki> Post to :
zim-wiki@lists.launchpad.net <mailto:zim-wiki@lists.launchpad.net>
Unsubscribe : https://launchpad.net/~zim-wiki
<https://launchpad.net/%7Ezim-wiki> More help   :
https://help.launchpad.net/ListHelp
<https://help.launchpad.net/ListHelp> 


_

Re: [Zim-wiki] plans for python3? Github?

[Tomasz Muras]

Just to add "me too" - please switch to git.

Tomek

On 14 Mar 2017 18:04, "Johannes Kirschner" 
wrote:

> +1 for github. When I was implementing the move-line features I was
> basically spending half a day figuring out how bazaar works. And to fix a
> bug a few weeks later, I basically had to look up everything again.
>
> Johannes
>
> On 03/14/2017 05:03 PM, Dimitrij Lisov wrote:
>
> Alex, I totally agree with you. GitHub is much more appealing and should
> attract more contributers.
>
> Alex Ivkin  schrieb am Di., 14. März 2017 um 16:52 Uhr:
>
>> Jaap,
>>
>> While you are at it, could you consider moving the codebase to GitHub? It
>> is so much more convenient to have it there.
>>
>> Having to deal with bazaar is what prevented me from submitting many more
>> patches.
>> *Alex*
>>
>>
>> ----------
>> *From:* Jaap Karssenberg
>> *Sent:* Tuesday, March 14, 2017 4:22AM
>> *To:* Jiří Janoušek, Zim-wiki
>> *Subject:* Re: [Zim-wiki] plans for python3?
>>
>> Hi Jiri,
>>
>> Would like to take you on on that offer. I will set up a branch to be
>> used for porting (I have a preferred starting point, not current trunk).
>>
>> Strategy wise I believe we need to go to Gtk3 before we can go to
>> Python3, so that will be 2 phases.
>> For the first step going to Gtk3 I would like to split up the application
>> in modules. Trying to get the basic application running first, than port
>> additional modules and plugins one-by-one.
>>
>> Let's simply use a wiki page to track progress and who-does-what. I
>> prefer (private) email for quick questions / discussions.
>>
>> Is this what you had in mind?
>>
>> Regards,
>>
>> Jaap
>>
>>
>> On Sat, Mar 11, 2017 at 7:39 PM Jiří Janoušek 
>> wrote:
>>
>> > Yes, I have plans to port zim to python 3, but can't commit to a
>> concrete
>> > timeline on this moment.
>>
>> I might help with the porting to Python 3 & GTK+ 3. What is the best
>> place to discuss the strategy? Mailing list, bug tracker or Launchpad
>> blueprints? I prefer the bug tracker.
>>
>> Best regards,
>>
>> Jiri Janousek
>>
>> ___
>> Mailing list: https://launchpad.net/~zim-wiki
>> Post to : zim-wiki@lists.launchpad.net
>> Unsubscribe : https://launchpad.net/~zim-wiki
>> More help   : https://help.launchpad.net/ListHelp
>>
>>
>>
>> ___
>> Mailing list: https://launchpad.net/~zim-wiki
>> Post to : zim-wiki@lists.launchpad.net
>> Unsubscribe : https://launchpad.net/~zim-wiki
>> More help   : https://help.launchpad.net/ListHelp
>>
>>
>> ___
>> Mailing list: https://launchpad.net/~zim-wiki
>> Post to : zim-wiki@lists.launchpad.net
>> Unsubscribe : https://launchpad.net/~zim-wiki
>> More help   : https://help.launchpad.net/ListHelp
>>
>
>
> ___
> Mailing list: https://launchpad.net/~zim-wiki
> Post to : zim-wiki@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~zim-wiki
> More help   : https://help.launchpad.net/ListHelp
>
>
>
> ___
> Mailing list: https://launchpad.net/~zim-wiki
> Post to : zim-wiki@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~zim-wiki
> More help   : https://help.launchpad.net/ListHelp
>
>
___
Mailing list: https://launchpad.net/~zim-wiki
Post to : zim-wiki@lists.launchpad.net
Unsubscribe : https://launchpad.net/~zim-wiki
More help   : https://help.launchpad.net/ListHelp

Re: [Zim-wiki] plans for python3? Github?

[Johannes Kirschner]

+1 for github. When I was implementing the move-line features I was 
basically spending half a day figuring out how bazaar works. And to fix 
a bug a few weeks later, I basically had to look up everything again.


Johannes

On 03/14/2017 05:03 PM, Dimitrij Lisov wrote:
Alex, I totally agree with you. GitHub is much more appealing and 
should attract more contributers.


Alex Ivkin mailto:a...@ivkin.net>> schrieb am Di., 
14. März 2017 um 16:52 Uhr:


Jaap,

While you are at it, could you consider moving the codebase to
GitHub? It is so much more convenient to have it there.

Having to deal with bazaar is what prevented me from submitting
many more patches.

*Alex*



*From:* Jaap Karssenberg
*Sent:* Tuesday, March 14, 2017 4:22AM
*To:* Jiří Janoušek, Zim-wiki
*Subject:* Re: [Zim-wiki] plans for python3?


Hi Jiri,

Would like to take you on on that offer. I will set up a branch
to be used for porting (I have a preferred starting point, not
current trunk).

Strategy wise I believe we need to go to Gtk3 before we can go to
Python3, so that will be 2 phases.
For the first step going to Gtk3 I would like to split up the
application in modules. Trying to get the basic application
running first, than port additional modules and plugins one-by-one.

Let's simply use a wiki page to track progress and who-does-what.
I prefer (private) email for quick questions / discussions.

Is this what you had in mind?

Regards,

Jaap


On Sat, Mar 11, 2017 at 7:39 PM Jiří Janoušek
mailto:janousek.j...@gmail.com>> wrote:

> Yes, I have plans to port zim to python 3, but can't commit
to a concrete
> timeline on this moment.

I might help with the porting to Python 3 & GTK+ 3. What is
the best
place to discuss the strategy? Mailing list, bug tracker or
Launchpad
blueprints? I prefer the bug tracker.

Best regards,

Jiri Janousek

___
Mailing list: https://launchpad.net/~zim-wiki
<https://launchpad.net/%7Ezim-wiki>
Post to : zim-wiki@lists.launchpad.net
<mailto:zim-wiki@lists.launchpad.net>
Unsubscribe : https://launchpad.net/~zim-wiki
<https://launchpad.net/%7Ezim-wiki>
More help   : https://help.launchpad.net/ListHelp



___
Mailing list:https://launchpad.net/~zim-wiki 
<https://launchpad.net/%7Ezim-wiki>
Post to :zim-wiki@lists.launchpad.net 
<mailto:zim-wiki@lists.launchpad.net>
Unsubscribe :https://launchpad.net/~zim-wiki 
<https://launchpad.net/%7Ezim-wiki>
More help   :https://help.launchpad.net/ListHelp


___
Mailing list: https://launchpad.net/~zim-wiki
<https://launchpad.net/%7Ezim-wiki>
Post to : zim-wiki@lists.launchpad.net
<mailto:zim-wiki@lists.launchpad.net>
Unsubscribe : https://launchpad.net/~zim-wiki
<https://launchpad.net/%7Ezim-wiki>
More help   : https://help.launchpad.net/ListHelp



___
Mailing list: https://launchpad.net/~zim-wiki
Post to : zim-wiki@lists.launchpad.net
Unsubscribe : https://launchpad.net/~zim-wiki
More help   : https://help.launchpad.net/ListHelp



___
Mailing list: https://launchpad.net/~zim-wiki
Post to : zim-wiki@lists.launchpad.net
Unsubscribe : https://launchpad.net/~zim-wiki
More help   : https://help.launchpad.net/ListHelp

Re: [Zim-wiki] plans for python3?

[Dimitrij Lisov]

Alex, I totally agree with you. GitHub is much more appealing and should
attract more contributers.

Alex Ivkin  schrieb am Di., 14. März 2017 um 16:52 Uhr:

> Jaap,
>
> While you are at it, could you consider moving the codebase to GitHub? It
> is so much more convenient to have it there.
>
> Having to deal with bazaar is what prevented me from submitting many more
> patches.
> *Alex*
>
>
> --
> *From:* Jaap Karssenberg
> *Sent:* Tuesday, March 14, 2017 4:22AM
> *To:* Jiří Janoušek, Zim-wiki
> *Subject:* Re: [Zim-wiki] plans for python3?
>
> Hi Jiri,
>
> Would like to take you on on that offer. I will set up a branch to be used
> for porting (I have a preferred starting point, not current trunk).
>
> Strategy wise I believe we need to go to Gtk3 before we can go to Python3,
> so that will be 2 phases.
> For the first step going to Gtk3 I would like to split up the application
> in modules. Trying to get the basic application running first, than port
> additional modules and plugins one-by-one.
>
> Let's simply use a wiki page to track progress and who-does-what. I prefer
> (private) email for quick questions / discussions.
>
> Is this what you had in mind?
>
> Regards,
>
> Jaap
>
>
> On Sat, Mar 11, 2017 at 7:39 PM Jiří Janoušek 
> wrote:
>
> > Yes, I have plans to port zim to python 3, but can't commit to a concrete
> > timeline on this moment.
>
> I might help with the porting to Python 3 & GTK+ 3. What is the best
> place to discuss the strategy? Mailing list, bug tracker or Launchpad
> blueprints? I prefer the bug tracker.
>
> Best regards,
>
> Jiri Janousek
>
> ___
> Mailing list: https://launchpad.net/~zim-wiki
> Post to : zim-wiki@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~zim-wiki
> More help   : https://help.launchpad.net/ListHelp
>
>
>
> ___
> Mailing list: https://launchpad.net/~zim-wiki
> Post to : zim-wiki@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~zim-wiki
> More help   : https://help.launchpad.net/ListHelp
>
>
> ___
> Mailing list: https://launchpad.net/~zim-wiki
> Post to : zim-wiki@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~zim-wiki
> More help   : https://help.launchpad.net/ListHelp
>
___
Mailing list: https://launchpad.net/~zim-wiki
Post to : zim-wiki@lists.launchpad.net
Unsubscribe : https://launchpad.net/~zim-wiki
More help   : https://help.launchpad.net/ListHelp

Re: [Zim-wiki] plans for python3?

[Alex Ivkin]

  
  
Jaap,
  While you are at it, could you consider moving the codebase to
GitHub? It is so much more convenient to have it there. 
  
  Having to deal with bazaar is what prevented me from submitting
many more patches.
  
  
  Alex





  From: Jaap Karssenberg
  Sent: Tuesday, March 14, 2017 4:22AM
  To: Jiří Janoušek, Zim-wiki
  Subject: Re: [Zim-wiki] plans for python3?
  


  Hi Jiri,


Would like to take you on on that offer. I will set up a
  branch to be used for porting (I have a preferred starting
  point, not current trunk).


Strategy wise I believe we need to go to Gtk3 before we can
  go to Python3, so that will be 2 phases.
For the first step going to Gtk3 I would like to split up
  the application in modules. Trying to get the basic
  application running first, than port additional modules and
  plugins one-by-one.



Let's simply use a wiki page to track progress and
  who-does-what. I prefer (private) email for quick questions /
  discussions.


Is this what you had in mind?


Regards,


Jaap


  
  
  
On Sat, Mar 11, 2017 at 7:39 PM Jiří Janoušek
  <janousek.j...@gmail.com>
  wrote:

> Yes, I
  have plans to port zim to python 3, but can't commit to a
  concrete
  > timeline on this moment.
  
  I might help with the porting to Python 3 & GTK+ 3. What
  is the best
  place to discuss the strategy? Mailing list, bug tracker or
  Launchpad
  blueprints? I prefer the bug tracker.
  
  Best regards,
  
  Jiri Janousek
  
  ___
  Mailing list: https://launchpad.net/~zim-wiki
  Post to     : zim-wiki@lists.launchpad.net
  Unsubscribe : https://launchpad.net/~zim-wiki
  More help   : https://help.launchpad.net/ListHelp

  
  
  
  
  ___
Mailing list: https://launchpad.net/~zim-wiki
Post to : zim-wiki@lists.launchpad.net
Unsubscribe : https://launchpad.net/~zim-wiki
More help   : https://help.launchpad.net/ListHelp



  


___
Mailing list: https://launchpad.net/~zim-wiki
Post to : zim-wiki@lists.launchpad.net
Unsubscribe : https://launchpad.net/~zim-wiki
More help   : https://help.launchpad.net/ListHelp

Re: [Zim-wiki] plans for python3?

[Jaap Karssenberg]

Hi Jiri,

Would like to take you on on that offer. I will set up a branch to be used
for porting (I have a preferred starting point, not current trunk).

Strategy wise I believe we need to go to Gtk3 before we can go to Python3,
so that will be 2 phases.
For the first step going to Gtk3 I would like to split up the application
in modules. Trying to get the basic application running first, than port
additional modules and plugins one-by-one.

Let's simply use a wiki page to track progress and who-does-what. I prefer
(private) email for quick questions / discussions.

Is this what you had in mind?

Regards,

Jaap


On Sat, Mar 11, 2017 at 7:39 PM Jiří Janoušek 
wrote:

> > Yes, I have plans to port zim to python 3, but can't commit to a concrete
> > timeline on this moment.
>
> I might help with the porting to Python 3 & GTK+ 3. What is the best
> place to discuss the strategy? Mailing list, bug tracker or Launchpad
> blueprints? I prefer the bug tracker.
>
> Best regards,
>
> Jiri Janousek
>
> ___
> Mailing list: https://launchpad.net/~zim-wiki
> Post to : zim-wiki@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~zim-wiki
> More help   : https://help.launchpad.net/ListHelp
>
___
Mailing list: https://launchpad.net/~zim-wiki
Post to : zim-wiki@lists.launchpad.net
Unsubscribe : https://launchpad.net/~zim-wiki
More help   : https://help.launchpad.net/ListHelp

Re: [Zim-wiki] plans for python3?

[Jiří Janoušek]

> Yes, I have plans to port zim to python 3, but can't commit to a concrete
> timeline on this moment.

I might help with the porting to Python 3 & GTK+ 3. What is the best
place to discuss the strategy? Mailing list, bug tracker or Launchpad
blueprints? I prefer the bug tracker.

Best regards,

Jiri Janousek

___
Mailing list: https://launchpad.net/~zim-wiki
Post to : zim-wiki@lists.launchpad.net
Unsubscribe : https://launchpad.net/~zim-wiki
More help   : https://help.launchpad.net/ListHelp

Re: [Zim-wiki] plans for python3?

[Jaap Karssenberg]

Yes, I have plans to port zim to python 3, but can't commit to a concrete
timeline on this moment.

Regards,

Jaap

On Sat, Dec 17, 2016 at 8:57 AM kamaraju kusumanchi <
raju.mailingli...@gmail.com> wrote:

> Are there any plans to move zim code base to python3? Currently I see
> that it depends on python2. FWIW, I am using zim 0.65 on Debian.
>
> thanks
> raju
> --
> Kamaraju S Kusumanchi | http://raju.shoutwiki.com/wiki/Blog
>
> ___
> Mailing list: https://launchpad.net/~zim-wiki
> Post to : zim-wiki@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~zim-wiki
> More help   : https://help.launchpad.net/ListHelp
>
___
Mailing list: https://launchpad.net/~zim-wiki
Post to : zim-wiki@lists.launchpad.net
Unsubscribe : https://launchpad.net/~zim-wiki
More help   : https://help.launchpad.net/ListHelp