[jira] [Closed] (PROTON-630) [python] Add a setup.py for installing the python bindings via PyPi
[ https://issues.apache.org/jira/browse/PROTON-630?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rafael H. Schloming closed PROTON-630. -- Resolution: Fixed On second thought instead of reopening this 0.8 JIRA I've created a new JIRA for 0.9: PROTON-756 > [python] Add a setup.py for installing the python bindings via PyPi > --- > > Key: PROTON-630 > URL: https://issues.apache.org/jira/browse/PROTON-630 > Project: Qpid Proton > Issue Type: New Feature > Components: python-binding >Affects Versions: 0.7 >Reporter: Ken Giusti >Assignee: Ken Giusti > Fix For: 0.8 > > > Include a setup.py that can be used to upload/download the python bindings > from PyPi. > Rational: This feature would allow our python bindings to properly integrate > with python virtual environments such as virtualenv. virtualenv allows a > developer to override the python packages installed on their system. > virtualenv works with pip to fetch python packages from repositories such as > PyPi, allowing a developer to create a custom python environment that can be > used for developing and testing python applications. > Since we currently lack an easy method for providing the python bindings via > PyPi, virtual environments cannot include proton python bindings, as the > site-packages installed on the 'real' system are not available in the virtual > environment by default. > However, system libraries, such as libproton, *are* able to be referenced by > the virtual environment by default. Given that, this new setup.py should > only need to install the python files that live under site-packages. > Specifically, only the proton.py, cproton.py, and the _cproton.so files need > to be provided. The setup.py should be written to actually include the > swig-generated C source, and build _cproton.so from it as part of the install > into the target environment. > Since only the python-specific files are provided, and the swig-generated C > code must be built on the target machine, the setup.py will assume that the > developer has already installed the proton libraries and header files on the > target machine. To be clear: this feature will still *require* proton to be > installed on the developer's machine - it merely allows the python bindings > to then be installed into a virtual python site-packages via pip/PyPi. > See https://virtualenv.pypa.io/en/latest/index.html for more details > regarding virtual environments. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (PROTON-756) add a new/simpler setup.py for python bindings
[ https://issues.apache.org/jira/browse/PROTON-756?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14221945#comment-14221945 ] Rafael H. Schloming commented on PROTON-756: See comments on PROTON-630. > add a new/simpler setup.py for python bindings > -- > > Key: PROTON-756 > URL: https://issues.apache.org/jira/browse/PROTON-756 > Project: Qpid Proton > Issue Type: Bug > Components: python-binding >Reporter: Rafael H. Schloming >Assignee: Ken Giusti > Fix For: 0.9 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (PROTON-756) add a new/simpler setup.py for python bindings
Rafael H. Schloming created PROTON-756: -- Summary: add a new/simpler setup.py for python bindings Key: PROTON-756 URL: https://issues.apache.org/jira/browse/PROTON-756 Project: Qpid Proton Issue Type: Bug Components: python-binding Reporter: Rafael H. Schloming Assignee: Ken Giusti Fix For: 0.9 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Reopened] (PROTON-630) [python] Add a setup.py for installing the python bindings via PyPi
[ https://issues.apache.org/jira/browse/PROTON-630?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rafael H. Schloming reopened PROTON-630: I've rolled back this change because it somewhat complicated the renaming/refactoring of the proton.py module into a package hierarchy. Also as I was looking into what it would take to get it working again I noticed that distutils is actually capable of invoking swig and generating the C wrapper source code on its own. I think all you need to do is define your extension to include cproton.i in the source rather than trying to pregenerate and bundle in the swig source code. I believe doing this would radically simplify a number of issues and possibly allow for a fairly vanilla setup.py that could be written outside of cmake as opposed to being generated by and intimately entangled with the cmake build. > [python] Add a setup.py for installing the python bindings via PyPi > --- > > Key: PROTON-630 > URL: https://issues.apache.org/jira/browse/PROTON-630 > Project: Qpid Proton > Issue Type: New Feature > Components: python-binding >Affects Versions: 0.7 >Reporter: Ken Giusti >Assignee: Ken Giusti > Fix For: 0.8 > > > Include a setup.py that can be used to upload/download the python bindings > from PyPi. > Rational: This feature would allow our python bindings to properly integrate > with python virtual environments such as virtualenv. virtualenv allows a > developer to override the python packages installed on their system. > virtualenv works with pip to fetch python packages from repositories such as > PyPi, allowing a developer to create a custom python environment that can be > used for developing and testing python applications. > Since we currently lack an easy method for providing the python bindings via > PyPi, virtual environments cannot include proton python bindings, as the > site-packages installed on the 'real' system are not available in the virtual > environment by default. > However, system libraries, such as libproton, *are* able to be referenced by > the virtual environment by default. Given that, this new setup.py should > only need to install the python files that live under site-packages. > Specifically, only the proton.py, cproton.py, and the _cproton.so files need > to be provided. The setup.py should be written to actually include the > swig-generated C source, and build _cproton.so from it as part of the install > into the target environment. > Since only the python-specific files are provided, and the swig-generated C > code must be built on the target machine, the setup.py will assume that the > developer has already installed the proton libraries and header files on the > target machine. To be clear: this feature will still *require* proton to be > installed on the developer's machine - it merely allows the python bindings > to then be installed into a virtual python site-packages via pip/PyPi. > See https://virtualenv.pypa.io/en/latest/index.html for more details > regarding virtual environments. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (PROTON-755) Update Ruby unit tests to use Minitest
[ https://issues.apache.org/jira/browse/PROTON-755?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14221910#comment-14221910 ] ASF subversion and git services commented on PROTON-755: Commit 2276c09715683ace9e761a6d5aab5b74add3b7b9 in qpid-proton's branch refs/heads/master from Rafael Schloming [ https://git-wip-us.apache.org/repos/asf?p=qpid-proton.git;h=2276c09 ] Revert "PROTON-755: Update Ruby smoke tests to use Minitest" This reverts commit 1d3a13863117cfca5aef56244b20773760428796. > Update Ruby unit tests to use Minitest > -- > > Key: PROTON-755 > URL: https://issues.apache.org/jira/browse/PROTON-755 > Project: Qpid Proton > Issue Type: Bug > Components: ruby-binding >Reporter: Darryl L. Pierce >Assignee: Darryl L. Pierce > Fix For: 0.9 > > > The old Test::Unit module names have been collapsed down to Minitest. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (PROTON-630) [python] Add a setup.py for installing the python bindings via PyPi
[ https://issues.apache.org/jira/browse/PROTON-630?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14221911#comment-14221911 ] ASF subversion and git services commented on PROTON-630: Commit f5cbab5eafeae5bf9e713db1c897c77b2022bfdc in qpid-proton's branch refs/heads/master from Rafael Schloming [ https://git-wip-us.apache.org/repos/asf?p=qpid-proton.git;h=f5cbab5 ] Revert "PROTON-630: add setup.py for python bindings" This reverts commit 4252758bd3772470bd255d034d3abea157429504. > [python] Add a setup.py for installing the python bindings via PyPi > --- > > Key: PROTON-630 > URL: https://issues.apache.org/jira/browse/PROTON-630 > Project: Qpid Proton > Issue Type: New Feature > Components: python-binding >Affects Versions: 0.7 >Reporter: Ken Giusti >Assignee: Ken Giusti > Fix For: 0.8 > > > Include a setup.py that can be used to upload/download the python bindings > from PyPi. > Rational: This feature would allow our python bindings to properly integrate > with python virtual environments such as virtualenv. virtualenv allows a > developer to override the python packages installed on their system. > virtualenv works with pip to fetch python packages from repositories such as > PyPi, allowing a developer to create a custom python environment that can be > used for developing and testing python applications. > Since we currently lack an easy method for providing the python bindings via > PyPi, virtual environments cannot include proton python bindings, as the > site-packages installed on the 'real' system are not available in the virtual > environment by default. > However, system libraries, such as libproton, *are* able to be referenced by > the virtual environment by default. Given that, this new setup.py should > only need to install the python files that live under site-packages. > Specifically, only the proton.py, cproton.py, and the _cproton.so files need > to be provided. The setup.py should be written to actually include the > swig-generated C source, and build _cproton.so from it as part of the install > into the target environment. > Since only the python-specific files are provided, and the swig-generated C > code must be built on the target machine, the setup.py will assume that the > developer has already installed the proton libraries and header files on the > target machine. To be clear: this feature will still *require* proton to be > installed on the developer's machine - it merely allows the python bindings > to then be installed into a virtual python site-packages via pip/PyPi. > See https://virtualenv.pypa.io/en/latest/index.html for more details > regarding virtual environments. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (PROTON-755) Update Ruby unit tests to use Minitest
[ https://issues.apache.org/jira/browse/PROTON-755?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14221905#comment-14221905 ] Rafael H. Schloming commented on PROTON-755: Oh, and I do have minitest installed: rpm -q rubygem-minitest rubygem-minitest-4.7.0-2.fc20.noarch > Update Ruby unit tests to use Minitest > -- > > Key: PROTON-755 > URL: https://issues.apache.org/jira/browse/PROTON-755 > Project: Qpid Proton > Issue Type: Bug > Components: ruby-binding >Reporter: Darryl L. Pierce >Assignee: Darryl L. Pierce > Fix For: 0.9 > > > The old Test::Unit module names have been collapsed down to Minitest. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Reopened] (PROTON-755) Update Ruby unit tests to use Minitest
[ https://issues.apache.org/jira/browse/PROTON-755?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rafael H. Schloming reopened PROTON-755: This breaks the build for me, I get this: /usr/share/gems/gems/minitest-4.7.0/lib/minitest/unit.rb:19:in `const_missing': uninitialized constant MiniTest::Test (NameError) from /home/rhs/proton/tests/ruby/proton_tests/interop.rb:15:in `' from /usr/share/rubygems/rubygems/core_ext/kernel_require.rb:55:in `require' from /usr/share/rubygems/rubygems/core_ext/kernel_require.rb:55:in `require' from /home/rhs/proton/tests/ruby/proton-test:4:in `' > Update Ruby unit tests to use Minitest > -- > > Key: PROTON-755 > URL: https://issues.apache.org/jira/browse/PROTON-755 > Project: Qpid Proton > Issue Type: Bug > Components: ruby-binding >Reporter: Darryl L. Pierce >Assignee: Darryl L. Pierce > Fix For: 0.9 > > > The old Test::Unit module names have been collapsed down to Minitest. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
