[MacPorts] #46932: py-stfio @0.14.1: update 0.14.2
#46932: py-stfio @0.14.1: update 0.14.2 ---------------------------------+-------------------------------- Reporter: christsc@… | Owner: macports-tickets@… Type: update | Status: new Priority: Normal | Milestone: Component: ports | Version: Keywords: haspatch maintainer | Port: py-stfio ---------------------------------+-------------------------------- * Fixes some errors during event detection -- Ticket URL: <https://trac.macports.org/ticket/46932> MacPorts <https://www.macports.org/> Ports system for OS X
#46932: py-stfio @0.14.1: update 0.14.2 -------------------------+--------------------------------- Reporter: christsc@… | Owner: macports-tickets@… Type: update | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: haspatch maintainer Port: py-stfio | -------------------------+--------------------------------- Comment (by christsc@…): See related ticket #46933 -- Ticket URL: <https://trac.macports.org/ticket/46932#comment:1> MacPorts <https://www.macports.org/> Ports system for OS X
#46932: py-stfio @0.14.1: update 0.14.2 -------------------------+--------------------------------- Reporter: christsc@… | Owner: macports-tickets@… Type: update | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: haspatch maintainer Port: py-stfio | -------------------------+--------------------------------- Comment (by mojca@…): Unrelated: is there a reason for keeping support for Python 2.6 and 3.3 or could it go to the graveyard (= users would be automatically upgraded from `py26-stfio` to `py27-stfio` for example)? -- Ticket URL: <https://trac.macports.org/ticket/46932#comment:3> MacPorts <https://www.macports.org/> Ports system for OS X
#46932: py-stfio @0.14.1: update 0.14.2 -------------------------+--------------------------------- Reporter: christsc@… | Owner: macports-tickets@… Type: update | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: haspatch maintainer Port: py-stfio | -------------------------+--------------------------------- Comment (by christsc@…): Replying to [comment:3 mojca@…]:
Unrelated: is there a reason for keeping support for Python 2.6 and 3.3 or could it go to the graveyard (= users would be automatically upgraded from `py26-stfio` to `py27-stfio` for example)?
I can drop py26 and py33 support in v0.14.5. For this we'd need libbiosig to be updated. See #47029. -- Ticket URL: <https://trac.macports.org/ticket/46932#comment:5> MacPorts <https://www.macports.org/> Ports system for OS X
#46932: py-stfio @0.14.1: update 0.14.2 -------------------------+--------------------------------- Reporter: christsc@… | Owner: macports-tickets@… Type: update | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: haspatch maintainer Port: py-stfio | -------------------------+--------------------------------- Comment (by mojca@…): How exactly is dropping `py26-stfio` and `py33-stfio` related to version 0.14.5 and/or libbiosig? -- Ticket URL: <https://trac.macports.org/ticket/46932#comment:6> MacPorts <https://www.macports.org/> Ports system for OS X
#46932: py-stfio @0.14.1: update 0.14.2 -------------------------+--------------------------------- Reporter: christsc@… | Owner: macports-tickets@… Type: update | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: haspatch maintainer Port: py-stfio | -------------------------+--------------------------------- Comment (by christsc@…): Replying to [comment:6 mojca@…]:
How exactly is dropping `py26-stfio` and `py33-stfio` related to version 0.14.5 and/or libbiosig?
Since you ask for an "exact" description, here's the long story: We could release a revision of the existing Portfile for v0.14.1 that drops support for py26 and py33. In that case we don't need to wait for v0.14.5. However, it might be more efficient to drop support when we update to v0.14.5 of py-stfio and stimfit, which will shortly be released, because we would only have to update the Portfiles once. In v0.14.5 I'd like to re-activate biosig as the default file reading backend. It was temporarily disabled in v0.14.2 (which was never released on MacPorts) because there were some serious bugs in biosig. These bugs were fixed in biosig 1.6.3. In addition, stimfit v0.14.5 can now deal better with errors from biosig. -- Ticket URL: <https://trac.macports.org/ticket/46932#comment:7> MacPorts <https://www.macports.org/> Ports system for OS X
#46932: py-stfio @0.14.1: update 0.14.2 -------------------------+--------------------------------- Reporter: christsc@… | Owner: macports-tickets@… Type: update | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: haspatch maintainer Port: py-stfio | -------------------------+--------------------------------- Comment (by petr@…): To my understand the proposal is to skip the update to 0.14.2 and to update directly to 0.14.5 along with dropping py26, py33. It is unrelated, but the proposal is to the later only with the update. -- Ticket URL: <https://trac.macports.org/ticket/46932#comment:8> MacPorts <https://www.macports.org/> Ports system for OS X
#46932: py-stfio @0.14.1: update 0.14.2 -------------------------+--------------------------------- Reporter: christsc@… | Owner: macports-tickets@… Type: update | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: haspatch maintainer Port: py-stfio | -------------------------+--------------------------------- Comment (by christsc@…): Replying to [comment:8 petr@…]:
To my understand the proposal is to skip the update to 0.14.2 and to update directly to 0.14.5 along with dropping py26, py33. It is unrelated, but the proposal is to the later only with the update.
Yes, that would be my suggestion. -- Ticket URL: <https://trac.macports.org/ticket/46932#comment:9> MacPorts <https://www.macports.org/> Ports system for OS X
#46932: py-stfio @0.14.1: update 0.14.2 -------------------------+--------------------------------- Reporter: christsc@… | Owner: macports-tickets@… Type: update | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: haspatch maintainer Port: py-stfio | -------------------------+--------------------------------- Comment (by mojca@…): One more question (for the future). Do you need support for Phoenix / do you plan to try wxWidgets on Python 3? I have a port `py- wxpython-3.0-phoeni` in my user dir, but if there is enough demand, we could add it to the official list of ports. -- Ticket URL: <https://trac.macports.org/ticket/46932#comment:10> MacPorts <https://www.macports.org/> Ports system for OS X
#46932: py-stfio @0.14.1: update 0.14.2 -------------------------+--------------------------------- Reporter: christsc@… | Owner: macports-tickets@… Type: update | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: haspatch maintainer Port: py-stfio | -------------------------+--------------------------------- Comment (by christsc@…): Replying to [comment:10 mojca@…]:
One more question (for the future). Do you need support for Phoenix / do you plan to try wxWidgets on Python 3? I have a port `py- wxpython-3.0-phoeni` in my user dir, but if there is enough demand, we could add it to the official list of ports.
Yes, I'm planning to move to Python 3. The main issue is that the parts of the wxPython API that are required to embed a Python shell and access a running wxWidgets C++ application ([https://github.com/wxWidgets/wxPython/blob/master/samples/embedded/embedded.... see the embedded sample]) have not been ported to phoenix yet. -- Ticket URL: <https://trac.macports.org/ticket/46932#comment:11> MacPorts <https://www.macports.org/> Ports system for OS X
#46932: py-stfio @0.14.1: update 0.14.2 -------------------------+--------------------------------- Reporter: christsc@… | Owner: macports-tickets@… Type: update | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: haspatch maintainer Port: py-stfio | -------------------------+--------------------------------- Comment (by christsc@…): Should I open a new ticket for v0.14.5 (probably going to be v0.14.6) of py-stfio and stimfit or update the patches instead? -- Ticket URL: <https://trac.macports.org/ticket/46932#comment:12> MacPorts <https://www.macports.org/> Ports system for OS X
#46932: py-stfio @0.14.1: update 0.14.2 -------------------------+--------------------------------- Reporter: christsc@… | Owner: macports-tickets@… Type: update | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: haspatch maintainer Port: py-stfio | -------------------------+--------------------------------- Comment (by christsc@…): Updated patch attached (v0.14.5, py26 and py33 support dropped) -- Ticket URL: <https://trac.macports.org/ticket/46932#comment:13> MacPorts <https://www.macports.org/> Ports system for OS X
#46932: py-stfio @0.14.1: update 0.14.2 -------------------------+--------------------------------- Reporter: christsc@… | Owner: macports-tickets@… Type: update | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: fixed | Keywords: haspatch maintainer Port: py-stfio | -------------------------+--------------------------------- Changes (by mojca@…): * status: new => closed * resolution: => fixed Comment: Committed in r133542. -- Ticket URL: <https://trac.macports.org/ticket/46932#comment:14> MacPorts <https://www.macports.org/> Ports system for OS X
participants (1)
-
MacPorts