Python 3.x support help

[paolo-oliveri]

Hello,
I am using a slightly edited (from me) version of pykml that I hope works both with Python 2.7 and Python 3.x. If you want, we can help one each other to check if it's fully functional and then update the package.
Sincerely,
Paolo Oliveri

[ecelis]

Hell @paolo-oliveri will you put your moded version in github? That way other can benefit and the project owner could review your code and erhaps merge.

[paolo-oliveri]

Hello! I thought that we could create a branch of your project in order to check and test it before merging, what do you think about it?
Sincerely,
Paolo Oliveri

[ecelis]

Hello @paolo-oliveri it is not my project, I am using it myself I was looking for a version with support for python 3 when I found your open issue. Since then I also stumbled with this fork that supports both python 2.7 and python 3.5 up to a certain point which is fine for my needs.

[paolo-oliveri]

Hello, Many apologies, I was so busy and insane that I exchanged you with the maintainer. LOL! I personally think that it is nonsense if one guy is a package maintainer and nobody can contact him/her to at least have some information. My target is to submit an update of this package (that I personally use with both Python 2.7.x and 3.x) to PIP so anyone should be able to install and use it. Do you know how can I do this, or what people I have to contact to let me help? Sincerely, Paolo Oliveri Da: Ernesto Celis <notifications@github.com> Risposta: shabble/pykml <reply@reply.github.com> Data: giovedì 19 aprile 2018 17:47 A: shabble/pykml <pykml@noreply.github.com> Cc: paolo-oliveri <paul@oliveri.info>, Mention <mention@noreply.github.com> Oggetto: Re: [shabble/pykml] Python 3.x support help (#5) Hello @paolo-oliveri it is not my project, I am using it myself I was looking for a version with support for python 3 when I found your open issue. Since then I also stumbled with this fork that supports both python 2.7 and python 3.5 up to a certain point which is fine for my needs. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or mute the thread.