[jira] [Commented] (PROTON-2816) The current python pkg build can only build a package with a bundled proton core
[ https://issues.apache.org/jira/browse/PROTON-2816?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17839144#comment-17839144 ] ASF GitHub Bot commented on PROTON-2816: asfgit merged PR #426: URL: https://github.com/apache/qpid-proton/pull/426 > The current python pkg build can only build a package with a bundled proton > core > > > Key: PROTON-2816 > URL: https://issues.apache.org/jira/browse/PROTON-2816 > Project: Qpid Proton > Issue Type: Bug > Components: python-binding >Affects Versions: proton-c-0.38.0 >Reporter: Andrew Stitcher >Assignee: Andrew Stitcher >Priority: Major > Fix For: proton-c-0.40.0 > > > This is an issue for 2 scenarios: > - Producing python packages for distributions that should depend on the > system installed proton core library > - Debugging the C code (either library or adaptation layer code) when running > from python. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (PROTON-2816) The current python pkg build can only build a package with a bundled proton core
[ https://issues.apache.org/jira/browse/PROTON-2816?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17839142#comment-17839142 ] ASF subversion and git services commented on PROTON-2816: - Commit a2e9eb63444bbda70f8870e28d5ef93b68c0bbe5 in qpid-proton's branch refs/heads/main from Andrew Stitcher [ https://gitbox.apache.org/repos/asf?p=qpid-proton.git;h=a2e9eb634 ] PROTON-2816/PROTON-2817: Support building python extension with unbundled proton There are 3 cases: * Bundled proton library - this should be the default and is what you should use with pip etc. * System proton library - this is what you should use in a distro package. * Use the in tree library built earlier in the build process - this is what you usually want for developer debugging, and should be the version actually tested by the in tree tests. This change also add control of the ability to package and test in isolated virtual python environments. Using these is the default, but under some circumstances you do not want the build process to construct a virtual environment by pulling packages from the internet. So we now have an option to turn this behaviour off and rely on the hosts python environment. > The current python pkg build can only build a package with a bundled proton > core > > > Key: PROTON-2816 > URL: https://issues.apache.org/jira/browse/PROTON-2816 > Project: Qpid Proton > Issue Type: Bug > Components: python-binding >Affects Versions: proton-c-0.38.0 >Reporter: Andrew Stitcher >Assignee: Andrew Stitcher >Priority: Major > Fix For: proton-c-0.40.0 > > > This is an issue for 2 scenarios: > - Producing python packages for distributions that should depend on the > system installed proton core library > - Debugging the C code (either library or adaptation layer code) when running > from python. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (PROTON-2816) The current python pkg build can only build a package with a bundled proton core
[ https://issues.apache.org/jira/browse/PROTON-2816?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17839132#comment-17839132 ] ASF GitHub Bot commented on PROTON-2816: astitcher opened a new pull request, #426: URL: https://github.com/apache/qpid-proton/pull/426 …dled proton There are 3 cases: * Bundled proton library - this should be the default and is what you should use with pip etc. * System proton library - this is what you should use in a distro package. * Use the in tree library built earlier in the build process - this is what you usually want for developer debugging, and should be the version actually tested by the in tree tests. This change also add control of the ability to package and test in isolated virtual python environments. Using these is the default, but under some circumstances you do not want the build process to construct a virtual environment by pulling packages from the internet. So we now have an option to turn this behaviour off and rely on the hosts python environment. > The current python pkg build can only build a package with a bundled proton > core > > > Key: PROTON-2816 > URL: https://issues.apache.org/jira/browse/PROTON-2816 > Project: Qpid Proton > Issue Type: Bug > Components: python-binding >Affects Versions: proton-c-0.38.0 >Reporter: Andrew Stitcher >Assignee: Andrew Stitcher >Priority: Major > Fix For: proton-c-0.40.0 > > > This is an issue for 2 scenarios: > - Producing python packages for distributions that should depend on the > system installed proton core library > - Debugging the C code (either library or adaptation layer code) when running > from python. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
