#39695 closed update (wontfix)
py26-pymvpa: update to current version
| Reported by: | jmroot (Joshua Root) | Owned by: | petrrr |
|---|---|---|---|
| Priority: | Normal | Milestone: | |
| Component: | ports | Version: | |
| Keywords: | Cc: | ||
| Port: | py26-pymvpa |
Description
Looks like you could decide to either go with the latest 2.2.0 or stick with the 0.4 series with 0.4.8.
The port should also be migrated to the unified python portgroup.
Change History (9)
comment:1 Changed 10 years ago by mf2k (Frank Schima)
| Owner: | changed from jameskyle@… to macports-tickets@… |
|---|
comment:2 Changed 10 years ago by jmroot (Joshua Root)
| Owner: | changed from macports-tickets@… to stromnov@… |
|---|
There is now a py-pymvpa portfile using the new portgroup, but py26-pymvpa still exists as a separate portfile using the python26 portgroup. Please unify them.
comment:3 Changed 10 years ago by stromnov (Andrey Stromnov)
It's rather complex task to incorporate old py26-pymvpa into existing unified py-pymvpa. Also, latest pymvpa officially supports only 2.7+ and there are no guarantee that it will work with python26.
comment:4 Changed 10 years ago by jmroot (Joshua Root)
The installation page says it should work with 2.6. But you can delete the py26 port if you’d prefer. The one thing it can’t do is keep using a soon to be removed portgroup.
comment:6 Changed 10 years ago by petrrr
The py26-pymvpa was removed in r128668, due to the deprecation of older Python versions.
comment:7 Changed 10 years ago by petrrr
| Owner: | changed from stromnov@… to petr@… |
|---|---|
| Status: | new → assigned |
comment:8 Changed 10 years ago by petrrr
| Resolution: | → wontfix |
|---|---|
| Status: | assigned → closed |
jameskyle has retired. See #44641.