avro-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Pedro Larroy <pedro.larroy.li...@gmail.com>
Subject Re: [jira] [Commented] (AVRO-1382) Support for python3
Date Thu, 12 Dec 2013 15:23:13 GMT
There were just some strings replaced by ant, and I prefer to have the
python module more standalone, on the other side still we need to then put
the avro version somewhere, which so far is an ant replacement string in
the released versions.

Pedro.


On Thu, Dec 12, 2013 at 12:18 AM, Doug Cutting (JIRA) <jira@apache.org>wrote:

>
>     [
> https://issues.apache.org/jira/browse/AVRO-1382?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13845820#comment-13845820]
>
> Doug Cutting commented on AVRO-1382:
> ------------------------------------
>
> Ant is not required.
>
> All that releases require is that the top-level build.sh script works.  In
> particular, that './build.sh dist' puts binary release artifacts in the
> top-level dist/ directory, that 'test' runs unit tests, and 'clean' removes
> files generated by the other commands.
>
> If ant is replaced with some other build tool then the top-level build.sh
> should be updated to invoke the new tool rather than ant.  Some languages
> implement a lang/*/build.sh script that invokes a language-specific build
> tool and then copies source code archive files up to ../../dist.
>
> Also, if the build tools change then the top-level BUILD.txt file should
> be updated.
>
>
>
> > Support for python3
> > -------------------
> >
> >                 Key: AVRO-1382
> >                 URL: https://issues.apache.org/jira/browse/AVRO-1382
> >             Project: Avro
> >          Issue Type: Bug
> >          Components: python
> >    Affects Versions: 1.7.5
> >            Reporter: Christophe Taton
> >         Attachments: AVRO-1382.20131203-001922.diff
> >
> >
> > Hi,
> > I'd need to use Avro from Python3, which would require essentially the
> following changes, which I am happy to contribute:
> >  - rewrite except statements according to new syntax
> >  - rewrite print statements according to new syntax
> >  - basestring becomes str
> >  - update some imports (StringIO becomes io.StringIO, httplib becomes
> http.client)
> > This would apparently require branching the python code to maintain a
> version for python2 and a separate version for python3.
> > Any thoughts on how to approach this?
> > Thanks!
>
>
>
> --
> This message was sent by Atlassian JIRA
> (v6.1.4#6159)
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message