On 16 April 2015 at 23:03, Robbie Gemmell wrote:
> On 16 April 2015 at 20:38, Ken Giusti wrote:
>> And within moments, I hit my first Really Big Problem:
>>
>> Jython
>>
>> Yep, turns out Jython can't parse 'futurized' python code. Especially
>> dislikes the
>>
>> except , ---> except a
On 16 April 2015 at 20:38, Ken Giusti wrote:
> And within moments, I hit my first Really Big Problem:
>
> Jython
>
> Yep, turns out Jython can't parse 'futurized' python code. Especially
> dislikes the
>
> except , ---> except as
>
> change. Which isn't very helpful, since the 'as' var
(Apologies for top post, on iPhone)
#4 keep all the unittest source as python2 code for testing python2 and
jython, but also run 2to3 over it at build time to automatically produce a
version in python3 syntax?
> On 16 Apr 2015, at 20:40, Ken Giusti wrote:
>
> And within moments, I hit my first
On Thu, 2015-04-16 at 15:38 -0400, Ken Giusti wrote:
> And within moments, I hit my first Really Big Problem:
>
> Jython
>
> Yep, turns out Jython can't parse 'futurized' python code. Especially
> dislikes the
>
> except , ---> except as
>
> change. Which isn't very helpful, since t
[
https://issues.apache.org/jira/browse/PROTON-334?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14498580#comment-14498580
]
ASF GitHub Bot commented on PROTON-334:
---
Github user astitcher commented on the pull
Github user astitcher commented on the pull request:
https://github.com/apache/qpid-proton/pull/17#issuecomment-93824913
@dnwe I think I copied that CMake code directly from qpid. I'll look at
doing something like you suggested - the CMake output does look clunky.
---
If your project
And within moments, I hit my first Really Big Problem:
Jython
Yep, turns out Jython can't parse 'futurized' python code. Especially dislikes
the
except , ---> except as
change. Which isn't very helpful, since the 'as' variant is the only syntax
supported by Python 3 (that comma-syn
[
https://issues.apache.org/jira/browse/PROTON-850?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gordon Sim updated PROTON-850:
--
Comment: was deleted
(was: Actually, this is not really a bug as described. The local state *is*
closed
On Thu, 2015-04-16 at 09:54 -0400, Ken Giusti wrote:
> Hi all,
>
> I'm building on the work done by Dominic and Mickael to get all the proton
> python bits to work under both python2 and python3. See [1].
>
> I think this will entail a lot of little changes to the python sources and
> the uni
[
https://issues.apache.org/jira/browse/PROTON-850?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14498365#comment-14498365
]
Gordon Sim edited comment on PROTON-850 at 4/16/15 5:43 PM:
Th
[
https://issues.apache.org/jira/browse/PROTON-850?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gordon Sim updated PROTON-850:
--
Attachment: PROTON_850.py
This is an example using the plain reactor api, that follows the same pattern
[
https://issues.apache.org/jira/browse/PROTON-850?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gordon Sim updated PROTON-850:
--
Component/s: python-binding
Description:
If a link is closed, and a new link with the same name is c
Hi all,
I'm building on the work done by Dominic and Mickael to get all the proton
python bits to work under both python2 and python3. See [1].
I think this will entail a lot of little changes to the python sources and the
unit tests. Rather than check in a single huge patch, I'm going to b
[
https://issues.apache.org/jira/browse/PROTON-850?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14497805#comment-14497805
]
Robbie Gemmell commented on PROTON-850:
---
I have spent some time investigating a rela
Robbie Gemmell created PROTON-853:
-
Summary: [proton-j] the transport emitted a new link attach for a
link in the process of being detached
Key: PROTON-853
URL: https://issues.apache.org/jira/browse/PROTON-853
[
https://issues.apache.org/jira/browse/PROTON-334?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14497717#comment-14497717
]
ASF GitHub Bot commented on PROTON-334:
---
Github user dnwe commented on the pull requ
Github user dnwe commented on the pull request:
https://github.com/apache/qpid-proton/pull/17#issuecomment-93675959
@astitcher minor issue, unrelated to the feature itself, but the CMake
build doesn't currently report which sasl implementation is being used. I just
see:
```
--
[
https://issues.apache.org/jira/browse/PROTON-852?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tomasz Nowicki updated PROTON-852:
--
Attachment: proton-c-GETADDRINFO.patch
> Implement pn_getaddrinfo,pn_getprotobyname for platform
Tomasz Nowicki created PROTON-852:
-
Summary: Implement pn_getaddrinfo,pn_getprotobyname for platforms
that not support getaddrinfo(),getprotobyname()
Key: PROTON-852
URL: https://issues.apache.org/jira/browse/PRO
[
https://issues.apache.org/jira/browse/PROTON-851?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tomasz Nowicki updated PROTON-851:
--
Attachment: proton-c-UUID.patch
> Implement pn_i_genuuid for platforms that not support uuid_gen
Tomasz Nowicki created PROTON-851:
-
Summary: Implement pn_i_genuuid for platforms that not support
uuid_generate
Key: PROTON-851
URL: https://issues.apache.org/jira/browse/PROTON-851
Project: Qpid Pro
21 matches
Mail list logo
