Re: [DISCUSS] Rename Fields -> Tags?

Sorry, I thought the name change would change the API, thus a major release. From: Christofer Dutz Reply: dev@plc4x.apache.org Date: November 10, 2022 at 08:15:55 To: dev@plc4x.apache.org Subject: Re: [DISCUSS] Rename Fields -> Tags? Hi Otto, I guess we should probably release at

Re: [DISCUSS] Rename Fields -> Tags?

if we had already had one before From: Otto Fowler Reply: Otto Fowler Date: November 11, 2022 at 15:10:06 To: dev@plc4x.apache.org , Christofer Dutz Subject: Re: [DISCUSS] Rename Fields -> Tags? Sorry, I thought the name change would change the API, thus a major release. From:

Re: [PLC4PY] Required setup for building?

Hi Chris, I'm not sure much has changed since last time, can you send me the output you're seeing? Ben On Fri, Nov 11, 2022 at 4:07 AM Christofer Dutz wrote: > Hi all, > > some time ago I added some checks to the prerequisite check to ensure I’m > able to build PLC4PY before even trying. For

Re: [PLC4PY] Required setup for building?

[INFO] --- exec-maven-plugin:3.1.0:exec (python-test) @ plc4py --- = test session starts == platform darwin -- Python 3.9.12, pytest-7.2.0, pluggy-1.0.0 -- /Users/christoferdutz/Projects/Apache/PLC4X/plc4x/sandbox/plc4py/venv/bin/python3

Re: [PLC4PY] Required setup for building?

Hi, Yeah it looks like we'll have to work on support for Python version < 3.10. It should be an easy fix to use the Union operator for type hints instead of the Pipe symbol. Ben On Fri, Nov 11, 2022 at 4:50 AM Christofer Dutz wrote: > [INFO] --- exec-maven-plugin:3.1.0:exec (python-test) @

Re: [PLC4PY] Required setup for building?

Just pushed a change, I've also removed the manual tests On Fri, Nov 11, 2022 at 4:55 AM Ben Hutcheson wrote: > Hi, > > Yeah it looks like we'll have to work on support for Python version < > 3.10. It should be an easy fix to use the Union operator for type hints > instead of the Pipe symbol. >

Re: [PLC4PY] Required setup for building?

Oh … if it’s just that, I can simply add that to the prerequisite check. That currently checks, if python is at least 3.7.0, I can bump that to 3.10.0 … however it seems that 3.9 is simpler to setup (As I didn’t explicitly select a version and that one was installed). So if the benefit of 3.10+

Re: [PLC4PY] Required setup for building?

No, just leave the prerequisite check, 3.7 is still a reasonable starting point (Although by the time Plc4Py actually gets useable it probably won't be) On Fri, Nov 11, 2022 at 5:03 AM Christofer Dutz wrote: > Oh … > > if it’s just that, I can simply add that to the prerequisite check. > That

Re: [PLC4PY] Required setup for building?

yes leave it at 3.7. They are currently improving a lot - 3.10 was a major shift and 3.11 has lot of neat improvements concerning error handling. See also: Built-in Exceptions — Python 3.11.0 documentation and Python 3.11 Preview: Even Better

[PLC4PY] Required setup for building?

Hi all, some time ago I added some checks to the prerequisite check to ensure I’m able to build PLC4PY before even trying. For some time now this has been failing on my side, so I guess there are some changes there. Could someone please help me adjust the prerequisite check to work for PLC4Py

[PLC4GO] S7: reading WORD array

Hi all, First of all, thank you so much for all the effort which went into the project so far. It is a very promising project to break open the industrial arena for a lot of use-cases. I’ve used the hello_world_plc4go_read.go example as a template to communicate with an S7-314-2 PN/DP

[GitHub] [plc4x] sruehl closed pull request #563: build(deps): bump maven-shade-plugin from 3.2.4 to 3.4.1

sruehl closed pull request #563: build(deps): bump maven-shade-plugin from 3.2.4 to 3.4.1 URL: https://github.com/apache/plc4x/pull/563 -- 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

[GitHub] [plc4x] dependabot[bot] commented on pull request #563: build(deps): bump maven-shade-plugin from 3.2.4 to 3.4.1

dependabot[bot] commented on PR #563: URL: https://github.com/apache/plc4x/pull/563#issuecomment-1311978135 OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me

[GitHub] [plc4x] sruehl merged pull request #579: build(deps): bump kotlin.version from 1.7.20 to 1.7.21

sruehl merged PR #579: URL: https://github.com/apache/plc4x/pull/579 -- 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...@plc4x.apache.org

[GitHub] [plc4x] sruehl merged pull request #651: build(deps): bump golang.org/x/tools from 0.2.0 to 0.3.0 in /plc4go

sruehl merged PR #651: URL: https://github.com/apache/plc4x/pull/651 -- 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...@plc4x.apache.org

[GitHub] [plc4x] sruehl merged pull request #650: build(deps): bump netty-bom from 4.1.84.Final to 4.1.85.Final

sruehl merged PR #650: URL: https://github.com/apache/plc4x/pull/650 -- 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...@plc4x.apache.org