[jira] [Commented] (PROTON-2708) New proactor APIs to query event batch for subject
[
https://issues.apache.org/jira/browse/PROTON-2708?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17710370#comment-17710370
]
ASF GitHub Bot commented on PROTON-2708:
astitcher opened a new pull request, #393:
URL: https://github.com/apache/qpid-proton/pull/393
These new APIs are useful for querying the proactor event batch for the
object that is the subject of the batch. The proactor guarantees that the
subject of the batch is never returned in any other batch until this batch is
completed.
> New proactor APIs to query event batch for subject
> --
>
> Key: PROTON-2708
> URL: https://issues.apache.org/jira/browse/PROTON-2708
> Project: Qpid Proton
> Issue Type: Improvement
> Components: proton-c
>Reporter: Andrew Stitcher
>Assignee: Andrew Stitcher
>Priority: Major
>
> The object that a proactor event batch refers can't change during the
> processing of the batch so you shouldn't need to extract the object from
> every individual event of the batch,
> This change introduces an API for each of the possible subjects of an event
> batch:
> {{pn_event_batch_proactor()}}, {{pn_event_batch_listener()}},
> {{pn_event_batch_connection()}}, {{pn_event_batch_raw_connection(),}}
--
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
[GitHub] [qpid-proton] astitcher opened a new pull request, #393: PROTON-2708: Introduce new proactor APIs that query batch
astitcher opened a new pull request, #393: URL: https://github.com/apache/qpid-proton/pull/393 These new APIs are useful for querying the proactor event batch for the object that is the subject of the batch. The proactor guarantees that the subject of the batch is never returned in any other batch until this batch is completed. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Created] (PROTON-2708) New proactor APIs to query event batch for subject
Andrew Stitcher created PROTON-2708:
---
Summary: New proactor APIs to query event batch for subject
Key: PROTON-2708
URL: https://issues.apache.org/jira/browse/PROTON-2708
Project: Qpid Proton
Issue Type: Improvement
Components: proton-c
Reporter: Andrew Stitcher
Assignee: Andrew Stitcher
The object that a proactor event batch refers can't change during the
processing of the batch so you shouldn't need to extract the object from every
individual event of the batch,
This change introduces an API for each of the possible subjects of an event
batch:
{{pn_event_batch_proactor()}}, {{pn_event_batch_listener()}},
{{pn_event_batch_connection()}}, {{pn_event_batch_raw_connection(),}}
--
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] (QPID-8631) [python client] Add minimal python3 support (while keeping python2.7 primary) so that qpid-cpp build and tests work with python3
[ https://issues.apache.org/jira/browse/QPID-8631?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17710335#comment-17710335 ] ASF subversion and git services commented on QPID-8631: --- Commit 127ca4a4082579f93ad38e9a9dc0146def65edb6 in qpid-python's branch refs/heads/main from Jiri Daněk [ https://gitbox.apache.org/repos/asf?p=qpid-python.git;h=127ca4a ] QPID-8631: fix some deprecation warnings by using new `notify_all`, `is_set`, `is_alive`, `daemon` > [python client] Add minimal python3 support (while keeping python2.7 primary) > so that qpid-cpp build and tests work with python3 > > > Key: QPID-8631 > URL: https://issues.apache.org/jira/browse/QPID-8631 > Project: Qpid > Issue Type: New Feature > Components: Python Client >Affects Versions: qpid-python-1.38.0 >Reporter: Jiri Daněk >Assignee: Jiri Daněk >Priority: Major > > The qpid-python project consists of an amqp client implementations for > amqp0-8, amqp0-9, amqp0-10 protocol versions, and of tests for those clients, > and also tests that use the clients to test qpid brokers. > I am interested in compiling qpid-cpp (especially the cpp client) on a recent > Linux that has Python 3. Therefore, if I don't want to skip building tests, I > need qpid-python to work with Python 3. > This is related to QPID-4982, QPID-8413, QPID-8516, QPID-8517 "modernization" > issues. > h3. Plan > Follow https://portingguide.readthedocs.io/en/latest. > Add things gradually, initially add changes that are py2 neutral, then in a > next stage add thing that are py3 required (while keeping it py2 compatible). -- 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] (QPID-8631) [python client] Add minimal python3 support (while keeping python2.7 primary) so that qpid-cpp build and tests work with python3
[ https://issues.apache.org/jira/browse/QPID-8631?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17710334#comment-17710334 ] ASF subversion and git services commented on QPID-8631: --- Commit bf7eec3d294a3ba0990f69d8a37fe9e54285503b in qpid-python's branch refs/heads/main from Jiri Daněk [ https://gitbox.apache.org/repos/asf?p=qpid-python.git;h=bf7eec3 ] QPID-8631: use the `list.sort(key=` parameter > [python client] Add minimal python3 support (while keeping python2.7 primary) > so that qpid-cpp build and tests work with python3 > > > Key: QPID-8631 > URL: https://issues.apache.org/jira/browse/QPID-8631 > Project: Qpid > Issue Type: New Feature > Components: Python Client >Affects Versions: qpid-python-1.38.0 >Reporter: Jiri Daněk >Assignee: Jiri Daněk >Priority: Major > > The qpid-python project consists of an amqp client implementations for > amqp0-8, amqp0-9, amqp0-10 protocol versions, and of tests for those clients, > and also tests that use the clients to test qpid brokers. > I am interested in compiling qpid-cpp (especially the cpp client) on a recent > Linux that has Python 3. Therefore, if I don't want to skip building tests, I > need qpid-python to work with Python 3. > This is related to QPID-4982, QPID-8413, QPID-8516, QPID-8517 "modernization" > issues. > h3. Plan > Follow https://portingguide.readthedocs.io/en/latest. > Add things gradually, initially add changes that are py2 neutral, then in a > next stage add thing that are py3 required (while keeping it py2 compatible). -- 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] (QPID-8631) [python client] Add minimal python3 support (while keeping python2.7 primary) so that qpid-cpp build and tests work with python3
[ https://issues.apache.org/jira/browse/QPID-8631?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17710336#comment-17710336 ] ASF subversion and git services commented on QPID-8631: --- Commit d4d92964fa586c6349edc86100567058d341dbb4 in qpid-python's branch refs/heads/main from Jiri Daněk [ https://gitbox.apache.org/repos/asf?p=qpid-python.git;h=d4d9296 ] QPID-8631: prefer list comprehension syntax over `map()` and `filter()` > [python client] Add minimal python3 support (while keeping python2.7 primary) > so that qpid-cpp build and tests work with python3 > > > Key: QPID-8631 > URL: https://issues.apache.org/jira/browse/QPID-8631 > Project: Qpid > Issue Type: New Feature > Components: Python Client >Affects Versions: qpid-python-1.38.0 >Reporter: Jiri Daněk >Assignee: Jiri Daněk >Priority: Major > > The qpid-python project consists of an amqp client implementations for > amqp0-8, amqp0-9, amqp0-10 protocol versions, and of tests for those clients, > and also tests that use the clients to test qpid brokers. > I am interested in compiling qpid-cpp (especially the cpp client) on a recent > Linux that has Python 3. Therefore, if I don't want to skip building tests, I > need qpid-python to work with Python 3. > This is related to QPID-4982, QPID-8413, QPID-8516, QPID-8517 "modernization" > issues. > h3. Plan > Follow https://portingguide.readthedocs.io/en/latest. > Add things gradually, initially add changes that are py2 neutral, then in a > next stage add thing that are py3 required (while keeping it py2 compatible). -- 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] (QPID-8631) [python client] Add minimal python3 support (while keeping python2.7 primary) so that qpid-cpp build and tests work with python3
[ https://issues.apache.org/jira/browse/QPID-8631?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17710337#comment-17710337 ] ASF subversion and git services commented on QPID-8631: --- Commit 5f4b01e0292e46e862011338b3e5b4858f76833a in qpid-python's branch refs/heads/main from Jiri Daněk [ https://gitbox.apache.org/repos/asf?p=qpid-python.git;h=5f4b01e ] QPID-8631: replace use of `string.joinfields` function > [python client] Add minimal python3 support (while keeping python2.7 primary) > so that qpid-cpp build and tests work with python3 > > > Key: QPID-8631 > URL: https://issues.apache.org/jira/browse/QPID-8631 > Project: Qpid > Issue Type: New Feature > Components: Python Client >Affects Versions: qpid-python-1.38.0 >Reporter: Jiri Daněk >Assignee: Jiri Daněk >Priority: Major > > The qpid-python project consists of an amqp client implementations for > amqp0-8, amqp0-9, amqp0-10 protocol versions, and of tests for those clients, > and also tests that use the clients to test qpid brokers. > I am interested in compiling qpid-cpp (especially the cpp client) on a recent > Linux that has Python 3. Therefore, if I don't want to skip building tests, I > need qpid-python to work with Python 3. > This is related to QPID-4982, QPID-8413, QPID-8516, QPID-8517 "modernization" > issues. > h3. Plan > Follow https://portingguide.readthedocs.io/en/latest. > Add things gradually, initially add changes that are py2 neutral, then in a > next stage add thing that are py3 required (while keeping it py2 compatible). -- 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] (QPID-8631) [python client] Add minimal python3 support (while keeping python2.7 primary) so that qpid-cpp build and tests work with python3
[ https://issues.apache.org/jira/browse/QPID-8631?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17710338#comment-17710338 ] ASF subversion and git services commented on QPID-8631: --- Commit 86bea7c3a9a97cbf71ed7bf5a39a8d53a3015bfb in qpid-python's branch refs/heads/main from Jiri Daněk [ https://gitbox.apache.org/repos/asf?p=qpid-python.git;h=86bea7c ] QPID-8631: remove extraneous semicolons > [python client] Add minimal python3 support (while keeping python2.7 primary) > so that qpid-cpp build and tests work with python3 > > > Key: QPID-8631 > URL: https://issues.apache.org/jira/browse/QPID-8631 > Project: Qpid > Issue Type: New Feature > Components: Python Client >Affects Versions: qpid-python-1.38.0 >Reporter: Jiri Daněk >Assignee: Jiri Daněk >Priority: Major > > The qpid-python project consists of an amqp client implementations for > amqp0-8, amqp0-9, amqp0-10 protocol versions, and of tests for those clients, > and also tests that use the clients to test qpid brokers. > I am interested in compiling qpid-cpp (especially the cpp client) on a recent > Linux that has Python 3. Therefore, if I don't want to skip building tests, I > need qpid-python to work with Python 3. > This is related to QPID-4982, QPID-8413, QPID-8516, QPID-8517 "modernization" > issues. > h3. Plan > Follow https://portingguide.readthedocs.io/en/latest. > Add things gradually, initially add changes that are py2 neutral, then in a > next stage add thing that are py3 required (while keeping it py2 compatible). -- 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] (QPID-8631) [python client] Add minimal python3 support (while keeping python2.7 primary) so that qpid-cpp build and tests work with python3
[ https://issues.apache.org/jira/browse/QPID-8631?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17710333#comment-17710333 ] ASF GitHub Bot commented on QPID-8631: -- jiridanek merged PR #16: URL: https://github.com/apache/qpid-python/pull/16 > [python client] Add minimal python3 support (while keeping python2.7 primary) > so that qpid-cpp build and tests work with python3 > > > Key: QPID-8631 > URL: https://issues.apache.org/jira/browse/QPID-8631 > Project: Qpid > Issue Type: New Feature > Components: Python Client >Affects Versions: qpid-python-1.38.0 >Reporter: Jiri Daněk >Assignee: Jiri Daněk >Priority: Major > > The qpid-python project consists of an amqp client implementations for > amqp0-8, amqp0-9, amqp0-10 protocol versions, and of tests for those clients, > and also tests that use the clients to test qpid brokers. > I am interested in compiling qpid-cpp (especially the cpp client) on a recent > Linux that has Python 3. Therefore, if I don't want to skip building tests, I > need qpid-python to work with Python 3. > This is related to QPID-4982, QPID-8413, QPID-8516, QPID-8517 "modernization" > issues. > h3. Plan > Follow https://portingguide.readthedocs.io/en/latest. > Add things gradually, initially add changes that are py2 neutral, then in a > next stage add thing that are py3 required (while keeping it py2 compatible). -- 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
[GitHub] [qpid-python] jiridanek merged pull request #16: QPID-8631: some more modernizations and compatibility enhancements
jiridanek merged PR #16: URL: https://github.com/apache/qpid-python/pull/16 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-8631) [python client] Add minimal python3 support (while keeping python2.7 primary) so that qpid-cpp build and tests work with python3
[ https://issues.apache.org/jira/browse/QPID-8631?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17710327#comment-17710327 ] ASF subversion and git services commented on QPID-8631: --- Commit 2bc6123f8e80c21c7e765d3deb7528be1b67ff9a in qpid-python's branch refs/heads/main from Jiri Daněk [ https://gitbox.apache.org/repos/asf?p=qpid-python.git;h=2bc6123 ] QPID-8631: `sgmllib.SGMLParser` -> `HTMLParser` > [python client] Add minimal python3 support (while keeping python2.7 primary) > so that qpid-cpp build and tests work with python3 > > > Key: QPID-8631 > URL: https://issues.apache.org/jira/browse/QPID-8631 > Project: Qpid > Issue Type: New Feature > Components: Python Client >Affects Versions: qpid-python-1.38.0 >Reporter: Jiri Daněk >Assignee: Jiri Daněk >Priority: Major > > The qpid-python project consists of an amqp client implementations for > amqp0-8, amqp0-9, amqp0-10 protocol versions, and of tests for those clients, > and also tests that use the clients to test qpid brokers. > I am interested in compiling qpid-cpp (especially the cpp client) on a recent > Linux that has Python 3. Therefore, if I don't want to skip building tests, I > need qpid-python to work with Python 3. > This is related to QPID-4982, QPID-8413, QPID-8516, QPID-8517 "modernization" > issues. > h3. Plan > Follow https://portingguide.readthedocs.io/en/latest. > Add things gradually, initially add changes that are py2 neutral, then in a > next stage add thing that are py3 required (while keeping it py2 compatible). -- 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] (QPID-8631) [python client] Add minimal python3 support (while keeping python2.7 primary) so that qpid-cpp build and tests work with python3
[ https://issues.apache.org/jira/browse/QPID-8631?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17710330#comment-17710330 ] ASF subversion and git services commented on QPID-8631: --- Commit 9651001c6fe0b65e538a96e27df36582b7ccb004 in qpid-python's branch refs/heads/main from Jiri Daněk [ https://gitbox.apache.org/repos/asf?p=qpid-python.git;h=9651001 ] QPID-8631: enable `absolute_import` from `__future__` and fix relative imports ``` python-modernize -wnf libmodernize.fixes.fix_import ``` > [python client] Add minimal python3 support (while keeping python2.7 primary) > so that qpid-cpp build and tests work with python3 > > > Key: QPID-8631 > URL: https://issues.apache.org/jira/browse/QPID-8631 > Project: Qpid > Issue Type: New Feature > Components: Python Client >Affects Versions: qpid-python-1.38.0 >Reporter: Jiri Daněk >Assignee: Jiri Daněk >Priority: Major > > The qpid-python project consists of an amqp client implementations for > amqp0-8, amqp0-9, amqp0-10 protocol versions, and of tests for those clients, > and also tests that use the clients to test qpid brokers. > I am interested in compiling qpid-cpp (especially the cpp client) on a recent > Linux that has Python 3. Therefore, if I don't want to skip building tests, I > need qpid-python to work with Python 3. > This is related to QPID-4982, QPID-8413, QPID-8516, QPID-8517 "modernization" > issues. > h3. Plan > Follow https://portingguide.readthedocs.io/en/latest. > Add things gradually, initially add changes that are py2 neutral, then in a > next stage add thing that are py3 required (while keeping it py2 compatible). -- 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] (QPID-8631) [python client] Add minimal python3 support (while keeping python2.7 primary) so that qpid-cpp build and tests work with python3
[ https://issues.apache.org/jira/browse/QPID-8631?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17710326#comment-17710326 ] ASF subversion and git services commented on QPID-8631: --- Commit 36eec7986b3d1f9145a05ffe569d81e10bc96542 in qpid-python's branch refs/heads/main from Jiri Daněk [ https://gitbox.apache.org/repos/asf?p=qpid-python.git;h=36eec79 ] QPID-8631: `rfc822.unquote` -> `email.utils.unquote` > [python client] Add minimal python3 support (while keeping python2.7 primary) > so that qpid-cpp build and tests work with python3 > > > Key: QPID-8631 > URL: https://issues.apache.org/jira/browse/QPID-8631 > Project: Qpid > Issue Type: New Feature > Components: Python Client >Affects Versions: qpid-python-1.38.0 >Reporter: Jiri Daněk >Assignee: Jiri Daněk >Priority: Major > > The qpid-python project consists of an amqp client implementations for > amqp0-8, amqp0-9, amqp0-10 protocol versions, and of tests for those clients, > and also tests that use the clients to test qpid brokers. > I am interested in compiling qpid-cpp (especially the cpp client) on a recent > Linux that has Python 3. Therefore, if I don't want to skip building tests, I > need qpid-python to work with Python 3. > This is related to QPID-4982, QPID-8413, QPID-8516, QPID-8517 "modernization" > issues. > h3. Plan > Follow https://portingguide.readthedocs.io/en/latest. > Add things gradually, initially add changes that are py2 neutral, then in a > next stage add thing that are py3 required (while keeping it py2 compatible). -- 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] (QPID-8631) [python client] Add minimal python3 support (while keeping python2.7 primary) so that qpid-cpp build and tests work with python3
[ https://issues.apache.org/jira/browse/QPID-8631?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17710328#comment-17710328 ] ASF subversion and git services commented on QPID-8631: --- Commit 045e90408b4d3416e1ae4af893c4b4426d9e98a5 in qpid-python's branch refs/heads/main from Jiri Daněk [ https://gitbox.apache.org/repos/asf?p=qpid-python.git;h=045e904 ] QPID-8631: fallback import for `cStringIO.StringIO` or `io.StringIO` > [python client] Add minimal python3 support (while keeping python2.7 primary) > so that qpid-cpp build and tests work with python3 > > > Key: QPID-8631 > URL: https://issues.apache.org/jira/browse/QPID-8631 > Project: Qpid > Issue Type: New Feature > Components: Python Client >Affects Versions: qpid-python-1.38.0 >Reporter: Jiri Daněk >Assignee: Jiri Daněk >Priority: Major > > The qpid-python project consists of an amqp client implementations for > amqp0-8, amqp0-9, amqp0-10 protocol versions, and of tests for those clients, > and also tests that use the clients to test qpid brokers. > I am interested in compiling qpid-cpp (especially the cpp client) on a recent > Linux that has Python 3. Therefore, if I don't want to skip building tests, I > need qpid-python to work with Python 3. > This is related to QPID-4982, QPID-8413, QPID-8516, QPID-8517 "modernization" > issues. > h3. Plan > Follow https://portingguide.readthedocs.io/en/latest. > Add things gradually, initially add changes that are py2 neutral, then in a > next stage add thing that are py3 required (while keeping it py2 compatible). -- 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] (QPID-8631) [python client] Add minimal python3 support (while keeping python2.7 primary) so that qpid-cpp build and tests work with python3
[ https://issues.apache.org/jira/browse/QPID-8631?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17710324#comment-17710324 ] ASF GitHub Bot commented on QPID-8631: -- jiridanek merged PR #15: URL: https://github.com/apache/qpid-python/pull/15 > [python client] Add minimal python3 support (while keeping python2.7 primary) > so that qpid-cpp build and tests work with python3 > > > Key: QPID-8631 > URL: https://issues.apache.org/jira/browse/QPID-8631 > Project: Qpid > Issue Type: New Feature > Components: Python Client >Affects Versions: qpid-python-1.38.0 >Reporter: Jiri Daněk >Assignee: Jiri Daněk >Priority: Major > > The qpid-python project consists of an amqp client implementations for > amqp0-8, amqp0-9, amqp0-10 protocol versions, and of tests for those clients, > and also tests that use the clients to test qpid brokers. > I am interested in compiling qpid-cpp (especially the cpp client) on a recent > Linux that has Python 3. Therefore, if I don't want to skip building tests, I > need qpid-python to work with Python 3. > This is related to QPID-4982, QPID-8413, QPID-8516, QPID-8517 "modernization" > issues. > h3. Plan > Follow https://portingguide.readthedocs.io/en/latest. > Add things gradually, initially add changes that are py2 neutral, then in a > next stage add thing that are py3 required (while keeping it py2 compatible). -- 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] (QPID-8631) [python client] Add minimal python3 support (while keeping python2.7 primary) so that qpid-cpp build and tests work with python3
[ https://issues.apache.org/jira/browse/QPID-8631?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17710329#comment-17710329 ] ASF subversion and git services commented on QPID-8631: --- Commit 84abc181d2e44760c15178a584aac924b29f0bbc in qpid-python's branch refs/heads/main from Jiri Daněk [ https://gitbox.apache.org/repos/asf?p=qpid-python.git;h=84abc18 ] QPID-8631: fallback import for `cPickle` or `pickle` > [python client] Add minimal python3 support (while keeping python2.7 primary) > so that qpid-cpp build and tests work with python3 > > > Key: QPID-8631 > URL: https://issues.apache.org/jira/browse/QPID-8631 > Project: Qpid > Issue Type: New Feature > Components: Python Client >Affects Versions: qpid-python-1.38.0 >Reporter: Jiri Daněk >Assignee: Jiri Daněk >Priority: Major > > The qpid-python project consists of an amqp client implementations for > amqp0-8, amqp0-9, amqp0-10 protocol versions, and of tests for those clients, > and also tests that use the clients to test qpid brokers. > I am interested in compiling qpid-cpp (especially the cpp client) on a recent > Linux that has Python 3. Therefore, if I don't want to skip building tests, I > need qpid-python to work with Python 3. > This is related to QPID-4982, QPID-8413, QPID-8516, QPID-8517 "modernization" > issues. > h3. Plan > Follow https://portingguide.readthedocs.io/en/latest. > Add things gradually, initially add changes that are py2 neutral, then in a > next stage add thing that are py3 required (while keeping it py2 compatible). -- 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] (QPID-8631) [python client] Add minimal python3 support (while keeping python2.7 primary) so that qpid-cpp build and tests work with python3
[ https://issues.apache.org/jira/browse/QPID-8631?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17710325#comment-17710325 ] ASF subversion and git services commented on QPID-8631: --- Commit c3f3a058350ef3ac66f27ce16f4085eee4c7bb41 in qpid-python's branch refs/heads/main from Jiri Daněk [ https://gitbox.apache.org/repos/asf?p=qpid-python.git;h=c3f3a05 ] QPID-8631: `new.module` -> `types.ModuleType` > [python client] Add minimal python3 support (while keeping python2.7 primary) > so that qpid-cpp build and tests work with python3 > > > Key: QPID-8631 > URL: https://issues.apache.org/jira/browse/QPID-8631 > Project: Qpid > Issue Type: New Feature > Components: Python Client >Affects Versions: qpid-python-1.38.0 >Reporter: Jiri Daněk >Assignee: Jiri Daněk >Priority: Major > > The qpid-python project consists of an amqp client implementations for > amqp0-8, amqp0-9, amqp0-10 protocol versions, and of tests for those clients, > and also tests that use the clients to test qpid brokers. > I am interested in compiling qpid-cpp (especially the cpp client) on a recent > Linux that has Python 3. Therefore, if I don't want to skip building tests, I > need qpid-python to work with Python 3. > This is related to QPID-4982, QPID-8413, QPID-8516, QPID-8517 "modernization" > issues. > h3. Plan > Follow https://portingguide.readthedocs.io/en/latest. > Add things gradually, initially add changes that are py2 neutral, then in a > next stage add thing that are py3 required (while keeping it py2 compatible). -- 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
[GitHub] [qpid-python] jiridanek merged pull request #15: QPID-8631: fix multiple import-related problems and Python 3 deprecations
jiridanek merged PR #15: URL: https://github.com/apache/qpid-python/pull/15 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-8631) [python client] Add minimal python3 support (while keeping python2.7 primary) so that qpid-cpp build and tests work with python3
[ https://issues.apache.org/jira/browse/QPID-8631?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17710316#comment-17710316 ] ASF GitHub Bot commented on QPID-8631: -- jiridanek merged PR #14: URL: https://github.com/apache/qpid-python/pull/14 > [python client] Add minimal python3 support (while keeping python2.7 primary) > so that qpid-cpp build and tests work with python3 > > > Key: QPID-8631 > URL: https://issues.apache.org/jira/browse/QPID-8631 > Project: Qpid > Issue Type: New Feature > Components: Python Client >Affects Versions: qpid-python-1.38.0 >Reporter: Jiri Daněk >Assignee: Jiri Daněk >Priority: Major > > The qpid-python project consists of an amqp client implementations for > amqp0-8, amqp0-9, amqp0-10 protocol versions, and of tests for those clients, > and also tests that use the clients to test qpid brokers. > I am interested in compiling qpid-cpp (especially the cpp client) on a recent > Linux that has Python 3. Therefore, if I don't want to skip building tests, I > need qpid-python to work with Python 3. > This is related to QPID-4982, QPID-8413, QPID-8516, QPID-8517 "modernization" > issues. > h3. Plan > Follow https://portingguide.readthedocs.io/en/latest. > Add things gradually, initially add changes that are py2 neutral, then in a > next stage add thing that are py3 required (while keeping it py2 compatible). -- 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] (QPID-8631) [python client] Add minimal python3 support (while keeping python2.7 primary) so that qpid-cpp build and tests work with python3
[ https://issues.apache.org/jira/browse/QPID-8631?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17710317#comment-17710317 ] ASF subversion and git services commented on QPID-8631: --- Commit d0050c6e3f80133f41e9bbcccaf3a2a7bde0c34b in qpid-python's branch refs/heads/main from Jiri Daněk [ https://gitbox.apache.org/repos/asf?p=qpid-python.git;h=d0050c6 ] QPID-8631: make the `qpid-python-test` script Python 3 compatible (#14) This takes inspiration from the PROTON-490 changes done in the Qpid Proton Python client. > [python client] Add minimal python3 support (while keeping python2.7 primary) > so that qpid-cpp build and tests work with python3 > > > Key: QPID-8631 > URL: https://issues.apache.org/jira/browse/QPID-8631 > Project: Qpid > Issue Type: New Feature > Components: Python Client >Affects Versions: qpid-python-1.38.0 >Reporter: Jiri Daněk >Assignee: Jiri Daněk >Priority: Major > > The qpid-python project consists of an amqp client implementations for > amqp0-8, amqp0-9, amqp0-10 protocol versions, and of tests for those clients, > and also tests that use the clients to test qpid brokers. > I am interested in compiling qpid-cpp (especially the cpp client) on a recent > Linux that has Python 3. Therefore, if I don't want to skip building tests, I > need qpid-python to work with Python 3. > This is related to QPID-4982, QPID-8413, QPID-8516, QPID-8517 "modernization" > issues. > h3. Plan > Follow https://portingguide.readthedocs.io/en/latest. > Add things gradually, initially add changes that are py2 neutral, then in a > next stage add thing that are py3 required (while keeping it py2 compatible). -- 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
[GitHub] [qpid-python] jiridanek merged pull request #14: QPID-8631: make the `qpid-python-test` script Python 3 compatible
jiridanek merged PR #14: URL: https://github.com/apache/qpid-python/pull/14 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-8631) [python client] Add minimal python3 support (while keeping python2.7 primary) so that qpid-cpp build and tests work with python3
[ https://issues.apache.org/jira/browse/QPID-8631?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17710311#comment-17710311 ] ASF GitHub Bot commented on QPID-8631: -- jiridanek opened a new pull request, #14: URL: https://github.com/apache/qpid-python/pull/14 This takes inspiration from the PROTON-490 changes done in the Qpid Proton Python client. > [python client] Add minimal python3 support (while keeping python2.7 primary) > so that qpid-cpp build and tests work with python3 > > > Key: QPID-8631 > URL: https://issues.apache.org/jira/browse/QPID-8631 > Project: Qpid > Issue Type: New Feature > Components: Python Client >Affects Versions: qpid-python-1.38.0 >Reporter: Jiri Daněk >Assignee: Jiri Daněk >Priority: Major > > The qpid-python project consists of an amqp client implementations for > amqp0-8, amqp0-9, amqp0-10 protocol versions, and of tests for those clients, > and also tests that use the clients to test qpid brokers. > I am interested in compiling qpid-cpp (especially the cpp client) on a recent > Linux that has Python 3. Therefore, if I don't want to skip building tests, I > need qpid-python to work with Python 3. > This is related to QPID-4982, QPID-8413, QPID-8516, QPID-8517 "modernization" > issues. > h3. Plan > Follow https://portingguide.readthedocs.io/en/latest. > Add things gradually, initially add changes that are py2 neutral, then in a > next stage add thing that are py3 required (while keeping it py2 compatible). -- 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
[GitHub] [qpid-python] jiridanek opened a new pull request, #14: QPID-8631: make the `qpid-python-test` script Python 3 compatible
jiridanek opened a new pull request, #14: URL: https://github.com/apache/qpid-python/pull/14 This takes inspiration from the PROTON-490 changes done in the Qpid Proton Python client. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-8631) [python client] Add minimal python3 support (while keeping python2.7 primary) so that qpid-cpp build and tests work with python3
[ https://issues.apache.org/jira/browse/QPID-8631?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17710310#comment-17710310 ] ASF subversion and git services commented on QPID-8631: --- Commit 9a457018654d7bcd6e6304d1dbd74c2d52adb715 in qpid-python's branch refs/heads/main from Jiri Daněk [ https://gitbox.apache.org/repos/asf?p=qpid-python.git;h=9a45701 ] QPID-8631: use the `in` operator for collection membership checks (#13) ``` python-modernize -wnf fissix.fixes.fix_has_key ``` > [python client] Add minimal python3 support (while keeping python2.7 primary) > so that qpid-cpp build and tests work with python3 > > > Key: QPID-8631 > URL: https://issues.apache.org/jira/browse/QPID-8631 > Project: Qpid > Issue Type: New Feature > Components: Python Client >Affects Versions: qpid-python-1.38.0 >Reporter: Jiri Daněk >Assignee: Jiri Daněk >Priority: Major > > The qpid-python project consists of an amqp client implementations for > amqp0-8, amqp0-9, amqp0-10 protocol versions, and of tests for those clients, > and also tests that use the clients to test qpid brokers. > I am interested in compiling qpid-cpp (especially the cpp client) on a recent > Linux that has Python 3. Therefore, if I don't want to skip building tests, I > need qpid-python to work with Python 3. > This is related to QPID-4982, QPID-8413, QPID-8516, QPID-8517 "modernization" > issues. > h3. Plan > Follow https://portingguide.readthedocs.io/en/latest. > Add things gradually, initially add changes that are py2 neutral, then in a > next stage add thing that are py3 required (while keeping it py2 compatible). -- 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] (QPID-8631) [python client] Add minimal python3 support (while keeping python2.7 primary) so that qpid-cpp build and tests work with python3
[ https://issues.apache.org/jira/browse/QPID-8631?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17710309#comment-17710309 ] ASF GitHub Bot commented on QPID-8631: -- jiridanek merged PR #13: URL: https://github.com/apache/qpid-python/pull/13 > [python client] Add minimal python3 support (while keeping python2.7 primary) > so that qpid-cpp build and tests work with python3 > > > Key: QPID-8631 > URL: https://issues.apache.org/jira/browse/QPID-8631 > Project: Qpid > Issue Type: New Feature > Components: Python Client >Affects Versions: qpid-python-1.38.0 >Reporter: Jiri Daněk >Assignee: Jiri Daněk >Priority: Major > > The qpid-python project consists of an amqp client implementations for > amqp0-8, amqp0-9, amqp0-10 protocol versions, and of tests for those clients, > and also tests that use the clients to test qpid brokers. > I am interested in compiling qpid-cpp (especially the cpp client) on a recent > Linux that has Python 3. Therefore, if I don't want to skip building tests, I > need qpid-python to work with Python 3. > This is related to QPID-4982, QPID-8413, QPID-8516, QPID-8517 "modernization" > issues. > h3. Plan > Follow https://portingguide.readthedocs.io/en/latest. > Add things gradually, initially add changes that are py2 neutral, then in a > next stage add thing that are py3 required (while keeping it py2 compatible). -- 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
[GitHub] [qpid-python] jiridanek merged pull request #13: QPID-8631: use the `in` operator for collection membership checks
jiridanek merged PR #13: URL: https://github.com/apache/qpid-python/pull/13 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-8631) [python client] Add minimal python3 support (while keeping python2.7 primary) so that qpid-cpp build and tests work with python3
[ https://issues.apache.org/jira/browse/QPID-8631?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17710305#comment-17710305 ] ASF GitHub Bot commented on QPID-8631: -- jiridanek opened a new pull request, #13: URL: https://github.com/apache/qpid-python/pull/13 ``` python-modernize -wnf fissix.fixes.fix_has_key ``` > [python client] Add minimal python3 support (while keeping python2.7 primary) > so that qpid-cpp build and tests work with python3 > > > Key: QPID-8631 > URL: https://issues.apache.org/jira/browse/QPID-8631 > Project: Qpid > Issue Type: New Feature > Components: Python Client >Affects Versions: qpid-python-1.38.0 >Reporter: Jiri Daněk >Assignee: Jiri Daněk >Priority: Major > > The qpid-python project consists of an amqp client implementations for > amqp0-8, amqp0-9, amqp0-10 protocol versions, and of tests for those clients, > and also tests that use the clients to test qpid brokers. > I am interested in compiling qpid-cpp (especially the cpp client) on a recent > Linux that has Python 3. Therefore, if I don't want to skip building tests, I > need qpid-python to work with Python 3. > This is related to QPID-4982, QPID-8413, QPID-8516, QPID-8517 "modernization" > issues. > h3. Plan > Follow https://portingguide.readthedocs.io/en/latest. > Add things gradually, initially add changes that are py2 neutral, then in a > next stage add thing that are py3 required (while keeping it py2 compatible). -- 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
[GitHub] [qpid-python] jiridanek opened a new pull request, #13: QPID-8631: use the `in` operator for collection membership checks
jiridanek opened a new pull request, #13: URL: https://github.com/apache/qpid-python/pull/13 ``` python-modernize -wnf fissix.fixes.fix_has_key ``` -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-8631) [python client] Add minimal python3 support (while keeping python2.7 primary) so that qpid-cpp build and tests work with python3
[ https://issues.apache.org/jira/browse/QPID-8631?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17710303#comment-17710303 ] ASF subversion and git services commented on QPID-8631: --- Commit f22f5adb21a0b65f88512399845ffb0e42c688bd in qpid-python's branch refs/heads/main from Jiri Daněk [ https://gitbox.apache.org/repos/asf?p=qpid-python.git;h=f22f5ad ] QPID-8631: remove use of `iteritems` and `xrange` (#12) These are somewhat helpful in Python 2, but they are not available in Python 3. > [python client] Add minimal python3 support (while keeping python2.7 primary) > so that qpid-cpp build and tests work with python3 > > > Key: QPID-8631 > URL: https://issues.apache.org/jira/browse/QPID-8631 > Project: Qpid > Issue Type: New Feature > Components: Python Client >Affects Versions: qpid-python-1.38.0 >Reporter: Jiri Daněk >Assignee: Jiri Daněk >Priority: Major > > The qpid-python project consists of an amqp client implementations for > amqp0-8, amqp0-9, amqp0-10 protocol versions, and of tests for those clients, > and also tests that use the clients to test qpid brokers. > I am interested in compiling qpid-cpp (especially the cpp client) on a recent > Linux that has Python 3. Therefore, if I don't want to skip building tests, I > need qpid-python to work with Python 3. > This is related to QPID-4982, QPID-8413, QPID-8516, QPID-8517 "modernization" > issues. > h3. Plan > Follow https://portingguide.readthedocs.io/en/latest. > Add things gradually, initially add changes that are py2 neutral, then in a > next stage add thing that are py3 required (while keeping it py2 compatible). -- 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] (QPID-8631) [python client] Add minimal python3 support (while keeping python2.7 primary) so that qpid-cpp build and tests work with python3
[ https://issues.apache.org/jira/browse/QPID-8631?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17710302#comment-17710302 ] ASF GitHub Bot commented on QPID-8631: -- jiridanek merged PR #12: URL: https://github.com/apache/qpid-python/pull/12 > [python client] Add minimal python3 support (while keeping python2.7 primary) > so that qpid-cpp build and tests work with python3 > > > Key: QPID-8631 > URL: https://issues.apache.org/jira/browse/QPID-8631 > Project: Qpid > Issue Type: New Feature > Components: Python Client >Affects Versions: qpid-python-1.38.0 >Reporter: Jiri Daněk >Assignee: Jiri Daněk >Priority: Major > > The qpid-python project consists of an amqp client implementations for > amqp0-8, amqp0-9, amqp0-10 protocol versions, and of tests for those clients, > and also tests that use the clients to test qpid brokers. > I am interested in compiling qpid-cpp (especially the cpp client) on a recent > Linux that has Python 3. Therefore, if I don't want to skip building tests, I > need qpid-python to work with Python 3. > This is related to QPID-4982, QPID-8413, QPID-8516, QPID-8517 "modernization" > issues. > h3. Plan > Follow https://portingguide.readthedocs.io/en/latest. > Add things gradually, initially add changes that are py2 neutral, then in a > next stage add thing that are py3 required (while keeping it py2 compatible). -- 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
[GitHub] [qpid-python] jiridanek merged pull request #12: QPID-8631: remove use of `iteritems` and `xrange`
jiridanek merged PR #12: URL: https://github.com/apache/qpid-python/pull/12 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-8631) [python client] Add minimal python3 support (while keeping python2.7 primary) so that qpid-cpp build and tests work with python3
[ https://issues.apache.org/jira/browse/QPID-8631?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17710299#comment-17710299 ] ASF GitHub Bot commented on QPID-8631: -- jiridanek opened a new pull request, #12: URL: https://github.com/apache/qpid-python/pull/12 These are somewhat helpful in Python 2, but they are not available in Python 3. > [python client] Add minimal python3 support (while keeping python2.7 primary) > so that qpid-cpp build and tests work with python3 > > > Key: QPID-8631 > URL: https://issues.apache.org/jira/browse/QPID-8631 > Project: Qpid > Issue Type: New Feature > Components: Python Client >Affects Versions: qpid-python-1.38.0 >Reporter: Jiri Daněk >Assignee: Jiri Daněk >Priority: Major > > The qpid-python project consists of an amqp client implementations for > amqp0-8, amqp0-9, amqp0-10 protocol versions, and of tests for those clients, > and also tests that use the clients to test qpid brokers. > I am interested in compiling qpid-cpp (especially the cpp client) on a recent > Linux that has Python 3. Therefore, if I don't want to skip building tests, I > need qpid-python to work with Python 3. > This is related to QPID-4982, QPID-8413, QPID-8516, QPID-8517 "modernization" > issues. > h3. Plan > Follow https://portingguide.readthedocs.io/en/latest. > Add things gradually, initially add changes that are py2 neutral, then in a > next stage add thing that are py3 required (while keeping it py2 compatible). -- 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
[GitHub] [qpid-python] jiridanek opened a new pull request, #12: QPID-8631: remove use of `iteritems` and `xrange`
jiridanek opened a new pull request, #12: URL: https://github.com/apache/qpid-python/pull/12 These are somewhat helpful in Python 2, but they are not available in Python 3. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-8631) [python client] Add minimal python3 support (while keeping python2.7 primary) so that qpid-cpp build and tests work with python3
[ https://issues.apache.org/jira/browse/QPID-8631?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17710297#comment-17710297 ] ASF subversion and git services commented on QPID-8631: --- Commit f84a72f0c1f592642d713a6891c3afdaf22ef99e in qpid-python's branch refs/heads/main from Jiri Daněk [ https://gitbox.apache.org/repos/asf?p=qpid-python.git;h=f84a72f ] QPID-8631: modernize `print` statement uses to the `print()` function form (#11) This is the result of running ``` python-modernize -wnf libmodernize.fixes.fix_print ``` > [python client] Add minimal python3 support (while keeping python2.7 primary) > so that qpid-cpp build and tests work with python3 > > > Key: QPID-8631 > URL: https://issues.apache.org/jira/browse/QPID-8631 > Project: Qpid > Issue Type: New Feature > Components: Python Client >Affects Versions: qpid-python-1.38.0 >Reporter: Jiri Daněk >Assignee: Jiri Daněk >Priority: Major > > The qpid-python project consists of an amqp client implementations for > amqp0-8, amqp0-9, amqp0-10 protocol versions, and of tests for those clients, > and also tests that use the clients to test qpid brokers. > I am interested in compiling qpid-cpp (especially the cpp client) on a recent > Linux that has Python 3. Therefore, if I don't want to skip building tests, I > need qpid-python to work with Python 3. > This is related to QPID-4982, QPID-8413, QPID-8516, QPID-8517 "modernization" > issues. > h3. Plan > Follow https://portingguide.readthedocs.io/en/latest. > Add things gradually, initially add changes that are py2 neutral, then in a > next stage add thing that are py3 required (while keeping it py2 compatible). -- 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] (QPID-8631) [python client] Add minimal python3 support (while keeping python2.7 primary) so that qpid-cpp build and tests work with python3
[ https://issues.apache.org/jira/browse/QPID-8631?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17710296#comment-17710296 ] ASF GitHub Bot commented on QPID-8631: -- jiridanek merged PR #11: URL: https://github.com/apache/qpid-python/pull/11 > [python client] Add minimal python3 support (while keeping python2.7 primary) > so that qpid-cpp build and tests work with python3 > > > Key: QPID-8631 > URL: https://issues.apache.org/jira/browse/QPID-8631 > Project: Qpid > Issue Type: New Feature > Components: Python Client >Affects Versions: qpid-python-1.38.0 >Reporter: Jiri Daněk >Assignee: Jiri Daněk >Priority: Major > > The qpid-python project consists of an amqp client implementations for > amqp0-8, amqp0-9, amqp0-10 protocol versions, and of tests for those clients, > and also tests that use the clients to test qpid brokers. > I am interested in compiling qpid-cpp (especially the cpp client) on a recent > Linux that has Python 3. Therefore, if I don't want to skip building tests, I > need qpid-python to work with Python 3. > This is related to QPID-4982, QPID-8413, QPID-8516, QPID-8517 "modernization" > issues. > h3. Plan > Follow https://portingguide.readthedocs.io/en/latest. > Add things gradually, initially add changes that are py2 neutral, then in a > next stage add thing that are py3 required (while keeping it py2 compatible). -- 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
[GitHub] [qpid-python] jiridanek merged pull request #11: QPID-8631: modernize `print` statement uses to the `print()` function form
jiridanek merged PR #11: URL: https://github.com/apache/qpid-python/pull/11 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-8631) [python client] Add minimal python3 support (while keeping python2.7 primary) so that qpid-cpp build and tests work with python3
[ https://issues.apache.org/jira/browse/QPID-8631?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17710293#comment-17710293 ] ASF GitHub Bot commented on QPID-8631: -- jiridanek opened a new pull request, #11: URL: https://github.com/apache/qpid-python/pull/11 This is the result of running ``` python-modernize -wnf libmodernize.fixes.fix_print ``` > [python client] Add minimal python3 support (while keeping python2.7 primary) > so that qpid-cpp build and tests work with python3 > > > Key: QPID-8631 > URL: https://issues.apache.org/jira/browse/QPID-8631 > Project: Qpid > Issue Type: New Feature > Components: Python Client >Affects Versions: qpid-python-1.38.0 >Reporter: Jiri Daněk >Assignee: Jiri Daněk >Priority: Major > > The qpid-python project consists of an amqp client implementations for > amqp0-8, amqp0-9, amqp0-10 protocol versions, and of tests for those clients, > and also tests that use the clients to test qpid brokers. > I am interested in compiling qpid-cpp (especially the cpp client) on a recent > Linux that has Python 3. Therefore, if I don't want to skip building tests, I > need qpid-python to work with Python 3. > This is related to QPID-4982, QPID-8413, QPID-8516, QPID-8517 "modernization" > issues. > h3. Plan > Follow https://portingguide.readthedocs.io/en/latest. > Add things gradually, initially add changes that are py2 neutral, then in a > next stage add thing that are py3 required (while keeping it py2 compatible). -- 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
[GitHub] [qpid-python] jiridanek opened a new pull request, #11: QPID-8631: modernize `print` statement uses to the `print()` function form
jiridanek opened a new pull request, #11: URL: https://github.com/apache/qpid-python/pull/11 This is the result of running ``` python-modernize -wnf libmodernize.fixes.fix_print ``` -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-8631) [python client] Add minimal python3 support (while keeping python2.7 primary) so that qpid-cpp build and tests work with python3
[ https://issues.apache.org/jira/browse/QPID-8631?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17710292#comment-17710292 ] ASF subversion and git services commented on QPID-8631: --- Commit ee50491f65b8ae90f296874a87a6180ff7a984f1 in qpid-python's branch refs/heads/main from Jiri Daněk [ https://gitbox.apache.org/repos/asf?p=qpid-python.git;h=ee50491 ] QPID-8631: remove the `L` literal suffix from `long`s (#10) This suffix is meaningless in Python 2.2+ and it is forbidden in Python 3. See https://peps.python.org/pep-0237/ for details. > [python client] Add minimal python3 support (while keeping python2.7 primary) > so that qpid-cpp build and tests work with python3 > > > Key: QPID-8631 > URL: https://issues.apache.org/jira/browse/QPID-8631 > Project: Qpid > Issue Type: New Feature > Components: Python Client >Affects Versions: qpid-python-1.38.0 >Reporter: Jiri Daněk >Assignee: Jiri Daněk >Priority: Major > > The qpid-python project consists of an amqp client implementations for > amqp0-8, amqp0-9, amqp0-10 protocol versions, and of tests for those clients, > and also tests that use the clients to test qpid brokers. > I am interested in compiling qpid-cpp (especially the cpp client) on a recent > Linux that has Python 3. Therefore, if I don't want to skip building tests, I > need qpid-python to work with Python 3. > This is related to QPID-4982, QPID-8413, QPID-8516, QPID-8517 "modernization" > issues. > h3. Plan > Follow https://portingguide.readthedocs.io/en/latest. > Add things gradually, initially add changes that are py2 neutral, then in a > next stage add thing that are py3 required (while keeping it py2 compatible). -- 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] (QPID-8631) [python client] Add minimal python3 support (while keeping python2.7 primary) so that qpid-cpp build and tests work with python3
[ https://issues.apache.org/jira/browse/QPID-8631?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17710291#comment-17710291 ] ASF GitHub Bot commented on QPID-8631: -- jiridanek merged PR #10: URL: https://github.com/apache/qpid-python/pull/10 > [python client] Add minimal python3 support (while keeping python2.7 primary) > so that qpid-cpp build and tests work with python3 > > > Key: QPID-8631 > URL: https://issues.apache.org/jira/browse/QPID-8631 > Project: Qpid > Issue Type: New Feature > Components: Python Client >Affects Versions: qpid-python-1.38.0 >Reporter: Jiri Daněk >Assignee: Jiri Daněk >Priority: Major > > The qpid-python project consists of an amqp client implementations for > amqp0-8, amqp0-9, amqp0-10 protocol versions, and of tests for those clients, > and also tests that use the clients to test qpid brokers. > I am interested in compiling qpid-cpp (especially the cpp client) on a recent > Linux that has Python 3. Therefore, if I don't want to skip building tests, I > need qpid-python to work with Python 3. > This is related to QPID-4982, QPID-8413, QPID-8516, QPID-8517 "modernization" > issues. > h3. Plan > Follow https://portingguide.readthedocs.io/en/latest. > Add things gradually, initially add changes that are py2 neutral, then in a > next stage add thing that are py3 required (while keeping it py2 compatible). -- 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
[GitHub] [qpid-python] jiridanek merged pull request #10: QPID-8631: remove the `L` literal suffix from `long`s
jiridanek merged PR #10: URL: https://github.com/apache/qpid-python/pull/10 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-8631) [python client] Add minimal python3 support (while keeping python2.7 primary) so that qpid-cpp build and tests work with python3
[ https://issues.apache.org/jira/browse/QPID-8631?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17710289#comment-17710289 ] ASF GitHub Bot commented on QPID-8631: -- jiridanek opened a new pull request, #10: URL: https://github.com/apache/qpid-python/pull/10 This suffix is meaningless in Python 2.2+ and it is forbidden in Python 3. See https://peps.python.org/pep-0237/ for details. > [python client] Add minimal python3 support (while keeping python2.7 primary) > so that qpid-cpp build and tests work with python3 > > > Key: QPID-8631 > URL: https://issues.apache.org/jira/browse/QPID-8631 > Project: Qpid > Issue Type: New Feature > Components: Python Client >Affects Versions: qpid-python-1.38.0 >Reporter: Jiri Daněk >Assignee: Jiri Daněk >Priority: Major > > The qpid-python project consists of an amqp client implementations for > amqp0-8, amqp0-9, amqp0-10 protocol versions, and of tests for those clients, > and also tests that use the clients to test qpid brokers. > I am interested in compiling qpid-cpp (especially the cpp client) on a recent > Linux that has Python 3. Therefore, if I don't want to skip building tests, I > need qpid-python to work with Python 3. > This is related to QPID-4982, QPID-8413, QPID-8516, QPID-8517 "modernization" > issues. > h3. Plan > Follow https://portingguide.readthedocs.io/en/latest. > Add things gradually, initially add changes that are py2 neutral, then in a > next stage add thing that are py3 required (while keeping it py2 compatible). -- 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
[GitHub] [qpid-python] jiridanek opened a new pull request, #10: QPID-8631: remove the L literal suffix from longs
jiridanek opened a new pull request, #10: URL: https://github.com/apache/qpid-python/pull/10 This suffix is meaningless in Python 2.2+ and it is forbidden in Python 3. See https://peps.python.org/pep-0237/ for details. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-8631) [python client] Add minimal python3 support (while keeping python2.7 primary) so that qpid-cpp build and tests work with python3
[ https://issues.apache.org/jira/browse/QPID-8631?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17710288#comment-17710288 ] ASF subversion and git services commented on QPID-8631: --- Commit 37463700f806ed70561ba9a0d143278599b145c8 in qpid-python's branch refs/heads/main from Jiri Daněk [ https://gitbox.apache.org/repos/asf?p=qpid-python.git;h=3746370 ] QPID-8631: modernize the `try: except as:` blocks and `raise`s (#9) > [python client] Add minimal python3 support (while keeping python2.7 primary) > so that qpid-cpp build and tests work with python3 > > > Key: QPID-8631 > URL: https://issues.apache.org/jira/browse/QPID-8631 > Project: Qpid > Issue Type: New Feature > Components: Python Client >Affects Versions: qpid-python-1.38.0 >Reporter: Jiri Daněk >Assignee: Jiri Daněk >Priority: Major > > The qpid-python project consists of an amqp client implementations for > amqp0-8, amqp0-9, amqp0-10 protocol versions, and of tests for those clients, > and also tests that use the clients to test qpid brokers. > I am interested in compiling qpid-cpp (especially the cpp client) on a recent > Linux that has Python 3. Therefore, if I don't want to skip building tests, I > need qpid-python to work with Python 3. > This is related to QPID-4982, QPID-8413, QPID-8516, QPID-8517 "modernization" > issues. > h3. Plan > Follow https://portingguide.readthedocs.io/en/latest. > Add things gradually, initially add changes that are py2 neutral, then in a > next stage add thing that are py3 required (while keeping it py2 compatible). -- 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] (QPID-8631) [python client] Add minimal python3 support (while keeping python2.7 primary) so that qpid-cpp build and tests work with python3
[ https://issues.apache.org/jira/browse/QPID-8631?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17710287#comment-17710287 ] ASF GitHub Bot commented on QPID-8631: -- jiridanek merged PR #9: URL: https://github.com/apache/qpid-python/pull/9 > [python client] Add minimal python3 support (while keeping python2.7 primary) > so that qpid-cpp build and tests work with python3 > > > Key: QPID-8631 > URL: https://issues.apache.org/jira/browse/QPID-8631 > Project: Qpid > Issue Type: New Feature > Components: Python Client >Affects Versions: qpid-python-1.38.0 >Reporter: Jiri Daněk >Assignee: Jiri Daněk >Priority: Major > > The qpid-python project consists of an amqp client implementations for > amqp0-8, amqp0-9, amqp0-10 protocol versions, and of tests for those clients, > and also tests that use the clients to test qpid brokers. > I am interested in compiling qpid-cpp (especially the cpp client) on a recent > Linux that has Python 3. Therefore, if I don't want to skip building tests, I > need qpid-python to work with Python 3. > This is related to QPID-4982, QPID-8413, QPID-8516, QPID-8517 "modernization" > issues. > h3. Plan > Follow https://portingguide.readthedocs.io/en/latest. > Add things gradually, initially add changes that are py2 neutral, then in a > next stage add thing that are py3 required (while keeping it py2 compatible). -- 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
[GitHub] [qpid-python] jiridanek merged pull request #9: QPID-8631: modernize the `try: except as:` blocks and `raise`s
jiridanek merged PR #9: URL: https://github.com/apache/qpid-python/pull/9 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-7072) Qpid.concurrency should not be using exec
[ https://issues.apache.org/jira/browse/QPID-7072?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17710271#comment-17710271 ] ASF GitHub Bot commented on QPID-7072: -- jiridanek merged PR #8: URL: https://github.com/apache/qpid-python/pull/8 > Qpid.concurrency should not be using exec > - > > Key: QPID-7072 > URL: https://issues.apache.org/jira/browse/QPID-7072 > Project: Qpid > Issue Type: Task > Components: Python Client >Affects Versions: 0.32 >Reporter: Brian Bouterse >Assignee: Jiri Daněk >Priority: Major > Fix For: qpid-python-1.38.0 > > > There doesn't seem to be a good reason for the usage of exec in the link > below. It should be replaced with something that doesn't use exec(). > https://github.com/apache/qpid/blob/4da5242913b3bb6c2fc478bc18fe8dc13fa74833/qpid/python/qpid/concurrency.py#L22-L39 -- 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] (QPID-7072) Qpid.concurrency should not be using exec
[ https://issues.apache.org/jira/browse/QPID-7072?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17710272#comment-17710272 ] ASF subversion and git services commented on QPID-7072: --- Commit 8cbd8ee4521afb5d571b585e9eacaa57e847558b in qpid-python's branch refs/heads/main from Jiri Daněk [ https://gitbox.apache.org/repos/asf?p=qpid-python.git;h=8cbd8ee ] QPID-7072: modernize the syntax of exec, before later hopefully replacing it (#8) > Qpid.concurrency should not be using exec > - > > Key: QPID-7072 > URL: https://issues.apache.org/jira/browse/QPID-7072 > Project: Qpid > Issue Type: Task > Components: Python Client >Affects Versions: 0.32 >Reporter: Brian Bouterse >Assignee: Jiri Daněk >Priority: Major > Fix For: qpid-python-1.38.0 > > > There doesn't seem to be a good reason for the usage of exec in the link > below. It should be replaced with something that doesn't use exec(). > https://github.com/apache/qpid/blob/4da5242913b3bb6c2fc478bc18fe8dc13fa74833/qpid/python/qpid/concurrency.py#L22-L39 -- 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
[GitHub] [qpid-python] jiridanek merged pull request #8: QPID-7072: modernize the syntax of exec, before later hopefully replacing it
jiridanek merged PR #8: URL: https://github.com/apache/qpid-python/pull/8 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-7072) Qpid.concurrency should not be using exec
[ https://issues.apache.org/jira/browse/QPID-7072?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17710268#comment-17710268 ] Jiri Daněk commented on QPID-7072: -- Another reason for redoing this is that the inspect module was reorganized in Python 3 and the functions it uses now are no longer available there. > Qpid.concurrency should not be using exec > - > > Key: QPID-7072 > URL: https://issues.apache.org/jira/browse/QPID-7072 > Project: Qpid > Issue Type: Task > Components: Python Client >Affects Versions: 0.32 >Reporter: Brian Bouterse >Assignee: Jiri Daněk >Priority: Major > Fix For: qpid-python-1.38.0 > > > There doesn't seem to be a good reason for the usage of exec in the link > below. It should be replaced with something that doesn't use exec(). > https://github.com/apache/qpid/blob/4da5242913b3bb6c2fc478bc18fe8dc13fa74833/qpid/python/qpid/concurrency.py#L22-L39 -- 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] [Assigned] (QPID-7072) Qpid.concurrency should not be using exec
[ https://issues.apache.org/jira/browse/QPID-7072?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jiri Daněk reassigned QPID-7072: Assignee: Jiri Daněk > Qpid.concurrency should not be using exec > - > > Key: QPID-7072 > URL: https://issues.apache.org/jira/browse/QPID-7072 > Project: Qpid > Issue Type: Task > Components: Python Client >Affects Versions: 0.32 >Reporter: Brian Bouterse >Assignee: Jiri Daněk >Priority: Major > > There doesn't seem to be a good reason for the usage of exec in the link > below. It should be replaced with something that doesn't use exec(). > https://github.com/apache/qpid/blob/4da5242913b3bb6c2fc478bc18fe8dc13fa74833/qpid/python/qpid/concurrency.py#L22-L39 -- 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] [Updated] (QPID-7072) Qpid.concurrency should not be using exec
[ https://issues.apache.org/jira/browse/QPID-7072?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jiri Daněk updated QPID-7072: - Fix Version/s: qpid-python-1.38.0 > Qpid.concurrency should not be using exec > - > > Key: QPID-7072 > URL: https://issues.apache.org/jira/browse/QPID-7072 > Project: Qpid > Issue Type: Task > Components: Python Client >Affects Versions: 0.32 >Reporter: Brian Bouterse >Assignee: Jiri Daněk >Priority: Major > Fix For: qpid-python-1.38.0 > > > There doesn't seem to be a good reason for the usage of exec in the link > below. It should be replaced with something that doesn't use exec(). > https://github.com/apache/qpid/blob/4da5242913b3bb6c2fc478bc18fe8dc13fa74833/qpid/python/qpid/concurrency.py#L22-L39 -- 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] [Resolved] (QPID-8632) [python client] Circular imports in mllib and qpid.connection, qpid.delegates
[
https://issues.apache.org/jira/browse/QPID-8632?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jiri Daněk resolved QPID-8632.
--
Fix Version/s: qpid-python-1.38.0
Assignee: Jiri Daněk
Resolution: Fixed
> [python client] Circular imports in mllib and qpid.connection, qpid.delegates
> -
>
> Key: QPID-8632
> URL: https://issues.apache.org/jira/browse/QPID-8632
> Project: Qpid
> Issue Type: Bug
> Components: Python Client
>Affects Versions: qpid-python-1.38.0
>Reporter: Jiri Daněk
>Assignee: Jiri Daněk
>Priority: Blocker
> Fix For: qpid-python-1.38.0
>
>
> Circular imports in Python actually do work, and break only when one makes a
> change that trips this potential minefield. One such change is Python 2/3
> compatibility.
> What triggers the problem is the situation when two modules import each
> other, _and_ the other module needs to be evaluated for the first import
> (when evaluating the first module) to complete. See
> https://stackoverflow.com/questions/744373/what-happens-when-using-mutual-or-circular-cyclic-imports
> for discussion and examples.
> Picking solution that is compatible with Python 2 as well as Python 3 in the
> future (QPID-8631) is tricky.
> {noformat}
> Traceback (most recent call last):
> File "./qpid-python-test", line 29, in
> from qpid.harness import Skipped
> File "/home/runner/work/qpid-python/qpid-python/qpid/__init__.py", line 20,
> in
> from . import connection
> File "/home/runner/work/qpid-python/qpid-python/qpid/connection.py", line
> 29, in
> from . import delegates
> File "/home/runner/work/qpid-python/qpid-python/qpid/delegates.py", line
> 21, in
> from . import connection, session
> ImportError: cannot import name connection
> {noformat}
> {noformat}
> Traceback (most recent call last):
> File "./qpid-python-test", line 30, in
> from qpid.harness import Skipped
> File "/home/runner/work/qpid-python/qpid-python/qpid/__init__.py", line 21,
> in
> from . import connection
> File "/home/runner/work/qpid-python/qpid-python/qpid/connection.py", line
> 21, in
> from . import datatypes, session
> File "/home/runner/work/qpid-python/qpid-python/qpid/session.py", line 22,
> in
> from .generator import command_invoker
> File "/home/runner/work/qpid-python/qpid-python/qpid/generator.py", line
> 23, in
> from .ops import *
> File "/home/runner/work/qpid-python/qpid-python/qpid/ops.py", line 21, in
>
> import os, mllib, sys
> File "/home/runner/work/qpid-python/qpid-python/mllib/__init__.py", line
> 27, in
> from . import dom, transforms, parsers
> File "/home/runner/work/qpid-python/qpid-python/mllib/dom.py", line 34, in
>
> from . import transforms
> File "/home/runner/work/qpid-python/qpid-python/mllib/transforms.py", line
> 25, in
> from . import dom
> ImportError: cannot import name dom
> {noformat}
--
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] [Created] (QPID-8633) [qpid python] Add .gitignore
Jiri Daněk created QPID-8633:
Summary: [qpid python] Add .gitignore
Key: QPID-8633
URL: https://issues.apache.org/jira/browse/QPID-8633
Project: Qpid
Issue Type: Task
Components: Python Client
Affects Versions: qpid-python-1.38.0
Reporter: Jiri Daněk
Assignee: Jiri Daněk
{noformat}
# Default ignored files
/shelf/
/workspace.xml
# Editor-based HTTP Client requests
/httpRequests/
# Datasource local storage ignored files
/dataSources/
/dataSources.local.xml
{noformat}
--
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] (QPID-8632) [python client] Circular imports in mllib and qpid.connection, qpid.delegates
[
https://issues.apache.org/jira/browse/QPID-8632?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17710211#comment-17710211
]
ASF subversion and git services commented on QPID-8632:
---
Commit f28a657a1a9201cd628b5225a131751beffb2cd7 in qpid-python's branch
refs/heads/main from Jiri Daněk
[ https://gitbox.apache.org/repos/asf?p=qpid-python.git;h=f28a657 ]
QPID-8632: use absolute, full imports when dealing with circular imports (#7)
This patch leaves the circular import in place, but changes the importing code
to make it overall safer.
> [python client] Circular imports in mllib and qpid.connection, qpid.delegates
> -
>
> Key: QPID-8632
> URL: https://issues.apache.org/jira/browse/QPID-8632
> Project: Qpid
> Issue Type: Bug
> Components: Python Client
>Affects Versions: qpid-python-1.38.0
>Reporter: Jiri Daněk
>Priority: Blocker
>
> Circular imports in Python actually do work, and break only when one makes a
> change that trips this potential minefield. One such change is Python 2/3
> compatibility.
> What triggers the problem is the situation when two modules import each
> other, _and_ the other module needs to be evaluated for the first import
> (when evaluating the first module) to complete. See
> https://stackoverflow.com/questions/744373/what-happens-when-using-mutual-or-circular-cyclic-imports
> for discussion and examples.
> Picking solution that is compatible with Python 2 as well as Python 3 in the
> future (QPID-8631) is tricky.
> {noformat}
> Traceback (most recent call last):
> File "./qpid-python-test", line 29, in
> from qpid.harness import Skipped
> File "/home/runner/work/qpid-python/qpid-python/qpid/__init__.py", line 20,
> in
> from . import connection
> File "/home/runner/work/qpid-python/qpid-python/qpid/connection.py", line
> 29, in
> from . import delegates
> File "/home/runner/work/qpid-python/qpid-python/qpid/delegates.py", line
> 21, in
> from . import connection, session
> ImportError: cannot import name connection
> {noformat}
> {noformat}
> Traceback (most recent call last):
> File "./qpid-python-test", line 30, in
> from qpid.harness import Skipped
> File "/home/runner/work/qpid-python/qpid-python/qpid/__init__.py", line 21,
> in
> from . import connection
> File "/home/runner/work/qpid-python/qpid-python/qpid/connection.py", line
> 21, in
> from . import datatypes, session
> File "/home/runner/work/qpid-python/qpid-python/qpid/session.py", line 22,
> in
> from .generator import command_invoker
> File "/home/runner/work/qpid-python/qpid-python/qpid/generator.py", line
> 23, in
> from .ops import *
> File "/home/runner/work/qpid-python/qpid-python/qpid/ops.py", line 21, in
>
> import os, mllib, sys
> File "/home/runner/work/qpid-python/qpid-python/mllib/__init__.py", line
> 27, in
> from . import dom, transforms, parsers
> File "/home/runner/work/qpid-python/qpid-python/mllib/dom.py", line 34, in
>
> from . import transforms
> File "/home/runner/work/qpid-python/qpid-python/mllib/transforms.py", line
> 25, in
> from . import dom
> ImportError: cannot import name dom
> {noformat}
--
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] (QPID-8632) [python client] Circular imports in mllib and qpid.connection, qpid.delegates
[
https://issues.apache.org/jira/browse/QPID-8632?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17710210#comment-17710210
]
ASF GitHub Bot commented on QPID-8632:
--
jiridanek merged PR #7:
URL: https://github.com/apache/qpid-python/pull/7
> [python client] Circular imports in mllib and qpid.connection, qpid.delegates
> -
>
> Key: QPID-8632
> URL: https://issues.apache.org/jira/browse/QPID-8632
> Project: Qpid
> Issue Type: Bug
> Components: Python Client
>Affects Versions: qpid-python-1.38.0
>Reporter: Jiri Daněk
>Priority: Blocker
>
> Circular imports in Python actually do work, and break only when one makes a
> change that trips this potential minefield. One such change is Python 2/3
> compatibility.
> What triggers the problem is the situation when two modules import each
> other, _and_ the other module needs to be evaluated for the first import
> (when evaluating the first module) to complete. See
> https://stackoverflow.com/questions/744373/what-happens-when-using-mutual-or-circular-cyclic-imports
> for discussion and examples.
> Picking solution that is compatible with Python 2 as well as Python 3 in the
> future (QPID-8631) is tricky.
> {noformat}
> Traceback (most recent call last):
> File "./qpid-python-test", line 29, in
> from qpid.harness import Skipped
> File "/home/runner/work/qpid-python/qpid-python/qpid/__init__.py", line 20,
> in
> from . import connection
> File "/home/runner/work/qpid-python/qpid-python/qpid/connection.py", line
> 29, in
> from . import delegates
> File "/home/runner/work/qpid-python/qpid-python/qpid/delegates.py", line
> 21, in
> from . import connection, session
> ImportError: cannot import name connection
> {noformat}
> {noformat}
> Traceback (most recent call last):
> File "./qpid-python-test", line 30, in
> from qpid.harness import Skipped
> File "/home/runner/work/qpid-python/qpid-python/qpid/__init__.py", line 21,
> in
> from . import connection
> File "/home/runner/work/qpid-python/qpid-python/qpid/connection.py", line
> 21, in
> from . import datatypes, session
> File "/home/runner/work/qpid-python/qpid-python/qpid/session.py", line 22,
> in
> from .generator import command_invoker
> File "/home/runner/work/qpid-python/qpid-python/qpid/generator.py", line
> 23, in
> from .ops import *
> File "/home/runner/work/qpid-python/qpid-python/qpid/ops.py", line 21, in
>
> import os, mllib, sys
> File "/home/runner/work/qpid-python/qpid-python/mllib/__init__.py", line
> 27, in
> from . import dom, transforms, parsers
> File "/home/runner/work/qpid-python/qpid-python/mllib/dom.py", line 34, in
>
> from . import transforms
> File "/home/runner/work/qpid-python/qpid-python/mllib/transforms.py", line
> 25, in
> from . import dom
> ImportError: cannot import name dom
> {noformat}
--
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
[GitHub] [qpid-python] jiridanek merged pull request #7: QPID-8632: use absolute, full imports when dealing with circular imports
jiridanek merged PR #7: URL: https://github.com/apache/qpid-python/pull/7 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-8632) [python client] Circular imports in mllib and qpid.connection, qpid.delegates
[
https://issues.apache.org/jira/browse/QPID-8632?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17710203#comment-17710203
]
ASF GitHub Bot commented on QPID-8632:
--
jiridanek commented on PR #7:
URL: https://github.com/apache/qpid-python/pull/7#issuecomment-1501989364
Trying this also with qpid-j, for extra credits
https://github.com/apache/qpid-python/actions/runs/4658983151/jobs/8245311044
> [python client] Circular imports in mllib and qpid.connection, qpid.delegates
> -
>
> Key: QPID-8632
> URL: https://issues.apache.org/jira/browse/QPID-8632
> Project: Qpid
> Issue Type: Bug
> Components: Python Client
>Affects Versions: qpid-python-1.38.0
>Reporter: Jiri Daněk
>Priority: Blocker
>
> Circular imports in Python actually do work, and break only when one makes a
> change that trips this potential minefield. One such change is Python 2/3
> compatibility.
> What triggers the problem is the situation when two modules import each
> other, _and_ the other module needs to be evaluated for the first import
> (when evaluating the first module) to complete. See
> https://stackoverflow.com/questions/744373/what-happens-when-using-mutual-or-circular-cyclic-imports
> for discussion and examples.
> Picking solution that is compatible with Python 2 as well as Python 3 in the
> future (QPID-8631) is tricky.
> {noformat}
> Traceback (most recent call last):
> File "./qpid-python-test", line 29, in
> from qpid.harness import Skipped
> File "/home/runner/work/qpid-python/qpid-python/qpid/__init__.py", line 20,
> in
> from . import connection
> File "/home/runner/work/qpid-python/qpid-python/qpid/connection.py", line
> 29, in
> from . import delegates
> File "/home/runner/work/qpid-python/qpid-python/qpid/delegates.py", line
> 21, in
> from . import connection, session
> ImportError: cannot import name connection
> {noformat}
> {noformat}
> Traceback (most recent call last):
> File "./qpid-python-test", line 30, in
> from qpid.harness import Skipped
> File "/home/runner/work/qpid-python/qpid-python/qpid/__init__.py", line 21,
> in
> from . import connection
> File "/home/runner/work/qpid-python/qpid-python/qpid/connection.py", line
> 21, in
> from . import datatypes, session
> File "/home/runner/work/qpid-python/qpid-python/qpid/session.py", line 22,
> in
> from .generator import command_invoker
> File "/home/runner/work/qpid-python/qpid-python/qpid/generator.py", line
> 23, in
> from .ops import *
> File "/home/runner/work/qpid-python/qpid-python/qpid/ops.py", line 21, in
>
> import os, mllib, sys
> File "/home/runner/work/qpid-python/qpid-python/mllib/__init__.py", line
> 27, in
> from . import dom, transforms, parsers
> File "/home/runner/work/qpid-python/qpid-python/mllib/dom.py", line 34, in
>
> from . import transforms
> File "/home/runner/work/qpid-python/qpid-python/mllib/transforms.py", line
> 25, in
> from . import dom
> ImportError: cannot import name dom
> {noformat}
--
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
[GitHub] [qpid-python] jiridanek commented on pull request #7: QPID-8632: use absolute, full imports when dealing with circular imports
jiridanek commented on PR #7: URL: https://github.com/apache/qpid-python/pull/7#issuecomment-1501989364 Trying this also with qpid-j, for extra credits https://github.com/apache/qpid-python/actions/runs/4658983151/jobs/8245311044 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-8632) [python client] Circular imports in mllib and qpid.connection, qpid.delegates
[
https://issues.apache.org/jira/browse/QPID-8632?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17710194#comment-17710194
]
ASF GitHub Bot commented on QPID-8632:
--
jiridanek opened a new pull request, #7:
URL: https://github.com/apache/qpid-python/pull/7
This patch leaves the circular import in place, but changes the importing
code to make it overall safer.
> [python client] Circular imports in mllib and qpid.connection, qpid.delegates
> -
>
> Key: QPID-8632
> URL: https://issues.apache.org/jira/browse/QPID-8632
> Project: Qpid
> Issue Type: Bug
> Components: Python Client
>Affects Versions: qpid-python-1.38.0
>Reporter: Jiri Daněk
>Priority: Blocker
>
> Circular imports in Python actually do work, and break only when one makes a
> change that trips this potential minefield. One such change is Python 2/3
> compatibility.
> What triggers the problem is the situation when two modules import each
> other, _and_ the other module needs to be evaluated for the first import
> (when evaluating the first module) to complete. See
> https://stackoverflow.com/questions/744373/what-happens-when-using-mutual-or-circular-cyclic-imports
> for discussion and examples.
> Picking solution that is compatible with Python 2 as well as Python 3 in the
> future (QPID-8631) is tricky.
> {noformat}
> Traceback (most recent call last):
> File "./qpid-python-test", line 29, in
> from qpid.harness import Skipped
> File "/home/runner/work/qpid-python/qpid-python/qpid/__init__.py", line 20,
> in
> from . import connection
> File "/home/runner/work/qpid-python/qpid-python/qpid/connection.py", line
> 29, in
> from . import delegates
> File "/home/runner/work/qpid-python/qpid-python/qpid/delegates.py", line
> 21, in
> from . import connection, session
> ImportError: cannot import name connection
> {noformat}
> {noformat}
> Traceback (most recent call last):
> File "./qpid-python-test", line 30, in
> from qpid.harness import Skipped
> File "/home/runner/work/qpid-python/qpid-python/qpid/__init__.py", line 21,
> in
> from . import connection
> File "/home/runner/work/qpid-python/qpid-python/qpid/connection.py", line
> 21, in
> from . import datatypes, session
> File "/home/runner/work/qpid-python/qpid-python/qpid/session.py", line 22,
> in
> from .generator import command_invoker
> File "/home/runner/work/qpid-python/qpid-python/qpid/generator.py", line
> 23, in
> from .ops import *
> File "/home/runner/work/qpid-python/qpid-python/qpid/ops.py", line 21, in
>
> import os, mllib, sys
> File "/home/runner/work/qpid-python/qpid-python/mllib/__init__.py", line
> 27, in
> from . import dom, transforms, parsers
> File "/home/runner/work/qpid-python/qpid-python/mllib/dom.py", line 34, in
>
> from . import transforms
> File "/home/runner/work/qpid-python/qpid-python/mllib/transforms.py", line
> 25, in
> from . import dom
> ImportError: cannot import name dom
> {noformat}
--
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
[GitHub] [qpid-python] jiridanek opened a new pull request, #7: QPID-8632: use absolute, full imports when dealing with circular imports
jiridanek opened a new pull request, #7: URL: https://github.com/apache/qpid-python/pull/7 This patch leaves the circular import in place, but changes the importing code to make it overall safer. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Resolved] (PROTON-2703) [protonj2] Update Netty to latest release
[ https://issues.apache.org/jira/browse/PROTON-2703?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy A. Bish resolved PROTON-2703. - Resolution: Fixed > [protonj2] Update Netty to latest release > - > > Key: PROTON-2703 > URL: https://issues.apache.org/jira/browse/PROTON-2703 > Project: Qpid Proton > Issue Type: Task > Components: protonj2 >Affects Versions: protonj2-1.0.0-M13 >Reporter: Timothy A. Bish >Assignee: Timothy A. Bish >Priority: Major > Fix For: protonj2-1.0.0-M14 > > > Update netty dependencies to the latest release version -- 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] [Resolved] (PROTON-2698) [protonj2] Add some additional APIs to the AMQP test peer
[ https://issues.apache.org/jira/browse/PROTON-2698?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothy A. Bish resolved PROTON-2698. - Resolution: Fixed > [protonj2] Add some additional APIs to the AMQP test peer > -- > > Key: PROTON-2698 > URL: https://issues.apache.org/jira/browse/PROTON-2698 > Project: Qpid Proton > Issue Type: Improvement > Components: protonj2 >Affects Versions: protonj2-1.0.0-M13 >Reporter: Timothy A. Bish >Assignee: Timothy A. Bish >Priority: Minor > Fix For: protonj2-1.0.0-M14 > > > Add some additional convenience APIs to the script API in the AMQP test peer > such as allowing the expectations for SASL connections to specify test > specific mechanism lists. -- 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] [Created] (QPID-8632) [python client] Circular imports in mllib and qpid.connection, qpid.delegates
Jiri Daněk created QPID-8632:
Summary: [python client] Circular imports in mllib and
qpid.connection, qpid.delegates
Key: QPID-8632
URL: https://issues.apache.org/jira/browse/QPID-8632
Project: Qpid
Issue Type: Bug
Components: Python Client
Affects Versions: qpid-python-1.38.0
Reporter: Jiri Daněk
Circular imports in Python actually do work, and break only when one makes a
change that trips this potential minefield. One such change is Python 2/3
compatibility.
What triggers the problem is the situation when two modules import each other,
_and_ the other module needs to be evaluated for the first import (when
evaluating the first module) to complete. See
https://stackoverflow.com/questions/744373/what-happens-when-using-mutual-or-circular-cyclic-imports
for discussion and examples.
Picking solution that is compatible with Python 2 as well as Python 3 in the
future (QPID-8631) is tricky.
{noformat}
Traceback (most recent call last):
File "./qpid-python-test", line 29, in
from qpid.harness import Skipped
File "/home/runner/work/qpid-python/qpid-python/qpid/__init__.py", line 20,
in
from . import connection
File "/home/runner/work/qpid-python/qpid-python/qpid/connection.py", line 29,
in
from . import delegates
File "/home/runner/work/qpid-python/qpid-python/qpid/delegates.py", line 21,
in
from . import connection, session
ImportError: cannot import name connection
{noformat}
{noformat}
Traceback (most recent call last):
File "./qpid-python-test", line 30, in
from qpid.harness import Skipped
File "/home/runner/work/qpid-python/qpid-python/qpid/__init__.py", line 21,
in
from . import connection
File "/home/runner/work/qpid-python/qpid-python/qpid/connection.py", line 21,
in
from . import datatypes, session
File "/home/runner/work/qpid-python/qpid-python/qpid/session.py", line 22, in
from .generator import command_invoker
File "/home/runner/work/qpid-python/qpid-python/qpid/generator.py", line 23,
in
from .ops import *
File "/home/runner/work/qpid-python/qpid-python/qpid/ops.py", line 21, in
import os, mllib, sys
File "/home/runner/work/qpid-python/qpid-python/mllib/__init__.py", line 27,
in
from . import dom, transforms, parsers
File "/home/runner/work/qpid-python/qpid-python/mllib/dom.py", line 34, in
from . import transforms
File "/home/runner/work/qpid-python/qpid-python/mllib/transforms.py", line
25, in
from . import dom
ImportError: cannot import name dom
{noformat}
--
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] [Updated] (QPID-8631) [python client] Add minimal python3 support (while keeping python2.7 primary) so that qpid-cpp build and tests work with python3
[ https://issues.apache.org/jira/browse/QPID-8631?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jiri Daněk updated QPID-8631: - Description: The qpid-python project consists of an amqp client implementations for amqp0-8, amqp0-9, amqp0-10 protocol versions, and of tests for those clients, and also tests that use the clients to test qpid brokers. I am interested in compiling qpid-cpp (especially the cpp client) on a recent Linux that has Python 3. Therefore, if I don't want to skip building tests, I need qpid-python to work with Python 3. This is related to QPID-4982, QPID-8413, QPID-8516, QPID-8517 "modernization" issues. h3. Plan Follow https://portingguide.readthedocs.io/en/latest. Add things gradually, initially add changes that are py2 neutral, then in a next stage add thing that are py3 required (while keeping it py2 compatible). was: The qpid-python project consists of an amqp client implementations for amqp0-8, amqp0-9, amqp0-10 protocol versions, and of tests for those clients, and also tests that use the clients to test qpid brokers. I am interested in compiling qpid-cpp (especially the cpp client) on a recent Linux that has Python 3. Therefore, if I don't want to skip building tests, I need qpid-python to work with Python 3. This is related to QPID-4982, QPID-8413, QPID-8516, QPID-8517 "modernization" issues. > [python client] Add minimal python3 support (while keeping python2.7 primary) > so that qpid-cpp build and tests work with python3 > > > Key: QPID-8631 > URL: https://issues.apache.org/jira/browse/QPID-8631 > Project: Qpid > Issue Type: New Feature > Components: Python Client >Affects Versions: qpid-python-1.38.0 >Reporter: Jiri Daněk >Assignee: Jiri Daněk >Priority: Major > > The qpid-python project consists of an amqp client implementations for > amqp0-8, amqp0-9, amqp0-10 protocol versions, and of tests for those clients, > and also tests that use the clients to test qpid brokers. > I am interested in compiling qpid-cpp (especially the cpp client) on a recent > Linux that has Python 3. Therefore, if I don't want to skip building tests, I > need qpid-python to work with Python 3. > This is related to QPID-4982, QPID-8413, QPID-8516, QPID-8517 "modernization" > issues. > h3. Plan > Follow https://portingguide.readthedocs.io/en/latest. > Add things gradually, initially add changes that are py2 neutral, then in a > next stage add thing that are py3 required (while keeping it py2 compatible). -- 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
