Re: [opensuse-factory] making a cohesive python LATEST available
FYI I experimented with a python:stable in my home project
(home:jenewton:python:stable). I get a build error on libatlas3
coming from devel:languages:python3, which I've linked the project to,
along with devel:languages:python:Factory. libatlas3 is linked to
from the Factory project, but that package isn't there anymore. I
have many inherited packages but it seems like there's no packages
available this experimental python:stable repository - is this normal
when using linked projects? Here's the meta conf:
<project name="home:jenewton:python:stable">
<title>Python Stable</title>
<description>Latest Python stable packages</description>
<link project="devel:languages:python:Factory"/>
<link project="devel:languages:python3"/>
<person userid="jenewton" role="maintainer"/>
<repository name="openSUSE_Leap_42.1">
<path project="openSUSE:Leap:42.1" repository="standard"/>
<arch>x86_64</arch>
</repository>
</project>
TLDR: Is Factory libatlas3 is broken?
-Jason
On Sun, Jun 26, 2016 at 11:03 PM, Jason Newton
adding some explicit maintainers to those projects (pulled from OBS
pages). Sorry for the repost - toggled off plain text.
I noticed devel:languages:python3 and it seems to depend on
devel:languages:python:Factory which I guess in theory provides the
mentioned functionality but I don't think this is clean enough. In
particular I don't have expectation Factory repositories of any sort
as a stable branch.
So - can the maintainers of these projects create a stable cohesive
variety? If you want to internally link the python package from
Factory, be my guest - but the expectation is something like latest
for the kernel or Qt (due to all the dependency packages). Offering
the latest stable build of python with all related (and c-based)
packages is important to any distribution/windows IMHO.
If I've missed something here, please let me know - I only stumbled
onto the python3 side project by accident - I didn't see it written
anywhere.
-Jason
On Fri, Jun 24, 2016 at 3:41 AM, Dave Plater
wrote: On 24/06/2016 02:58, Jason Newton wrote:
Hi,
I noticed a great reason to use python 3.5 today - PEP 465 - A
dedicated infix operator for matrix multiplication. This takes a
great deal of pain out of numeric programming with python and this is
the first series having it.
But I was surprised to see there seems no way short of tumbleweed /
devel:languages:python:Factory to use it. Is it such a beast to allow
devel:languages:python to support it? Like with KDE, can we have a
devel:languages:python:latest fork that rebuilds all things for 3.5?
Keep in mind 3.5 series has been available since last September with
the last release in start of December!
-Jason
+1 I need python 3.5 in Leap:42.2 for a blender update, blender since 2.77 no longer builds against python 3.4
Dave P
--
To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org
To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
-- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Hi Jason, sorry it took me so long to response. I'm deep in Hackweek not following outside world much. I found confusing that you miss python 3.5 in Tumbleweed. I'm running Tumbleweed and yet: $ python3 -V Python 3.5.1 # LANG=C zypper se -s --match-exact python3 Loading repository data... Reading installed packages... S | Name | Type | Version | Arch | Repository --+---------+---------+-----------+--------+----------- i | python3 | package | 3.5.1-3.4 | x86_64 | repo-oss v | python3 | package | 3.5.1-3.4 | i586 | repo-oss Regarding the d:l:python3:latest, if you're concerned about the python version used, we already use the highest version in distribution, if you are concerned that the set of packages is smaller in d:l:p3 than in d:l:p, there is unfortunate current state and Jan Matejek is working on build changes so in future there should be both Python 2.* and Python 3.* modules be built from the same source package within the same project (at least that is how I understand the plan). In the meantime you can submit the packages you miss and do the changes manually. I can't say much about cohesivness of the build but I guess it should be fine and I'd focus on problems if you meet one. The best solution is as always put everything into openSUSE:Factory and build it together. Regarding your libatlas3 problem: * package has disabled build in science * is failing in Education * is missing in openSUSE:Factory so, to fix it you need to fix in Education or science and submit it to openSUSE:Factory to solve your problem. I hope I covered all those topics and it helps you a bit. Best regards, S_W On Wed, Jun 29, 2016 at 11:58:08PM -0400, Jason Newton wrote:
FYI I experimented with a python:stable in my home project (home:jenewton:python:stable). I get a build error on libatlas3 coming from devel:languages:python3, which I've linked the project to, along with devel:languages:python:Factory. libatlas3 is linked to from the Factory project, but that package isn't there anymore. I have many inherited packages but it seems like there's no packages available this experimental python:stable repository - is this normal when using linked projects? Here's the meta conf:
<project name="home:jenewton:python:stable"> <title>Python Stable</title> <description>Latest Python stable packages</description> <link project="devel:languages:python:Factory"/> <link project="devel:languages:python3"/> <person userid="jenewton" role="maintainer"/> <repository name="openSUSE_Leap_42.1"> <path project="openSUSE:Leap:42.1" repository="standard"/> <arch>x86_64</arch> </repository> </project>
TLDR: Is Factory libatlas3 is broken?
-Jason
On Sun, Jun 26, 2016 at 11:03 PM, Jason Newton
wrote: adding some explicit maintainers to those projects (pulled from OBS
pages). Sorry for the repost - toggled off plain text.
I noticed devel:languages:python3 and it seems to depend on
devel:languages:python:Factory which I guess in theory provides the
mentioned functionality but I don't think this is clean enough. In
particular I don't have expectation Factory repositories of any sort
as a stable branch.
So - can the maintainers of these projects create a stable cohesive
variety? If you want to internally link the python package from
Factory, be my guest - but the expectation is something like latest
for the kernel or Qt (due to all the dependency packages). Offering
the latest stable build of python with all related (and c-based)
packages is important to any distribution/windows IMHO.
If I've missed something here, please let me know - I only stumbled
onto the python3 side project by accident - I didn't see it written
anywhere.
-Jason
On Fri, Jun 24, 2016 at 3:41 AM, Dave Plater
wrote: On 24/06/2016 02:58, Jason Newton wrote:
Hi,
I noticed a great reason to use python 3.5 today - PEP 465 - A
dedicated infix operator for matrix multiplication. This takes a
great deal of pain out of numeric programming with python and this is
the first series having it.
But I was surprised to see there seems no way short of tumbleweed /
devel:languages:python:Factory to use it. Is it such a beast to allow
devel:languages:python to support it? Like with KDE, can we have a
devel:languages:python:latest fork that rebuilds all things for 3.5?
Keep in mind 3.5 series has been available since last September with
the last release in start of December!
-Jason
+1 I need python 3.5 in Leap:42.2 for a blender update, blender since 2.77 no longer builds against python 3.4
Dave P
--
To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org
To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
-- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Hi Jason, sorry it took me so long to response. I'm deep in Hackweek not following outside world much. I found confusing that you miss python 3.5 in Tumbleweed. I'm running Tumbleweed and yet: $ python3 -V Python 3.5.1 # LANG=C zypper se -s --match-exact python3 Loading repository data... Reading installed packages... S | Name | Type | Version | Arch | Repository --+---------+---------+-----------+--------+----------- i | python3 | package | 3.5.1-3.4 | x86_64 | repo-oss v | python3 | package | 3.5.1-3.4 | i586 | repo-oss Regarding the d:l:python3:latest, if you're concerned about the python version used, we already use the highest version in distribution, if you are concerned that the set of packages is smaller in d:l:p3 than in d:l:p, there is unfortunate current state and Jan Matejek is working on build changes so in future there should be both Python 2.* and Python 3.* modules be built from the same source package within the same project (at least that is how I understand the plan). In the meantime you can submit the packages you miss and do the changes manually. I can't say much about cohesivness of the build but I guess it should be fine and I'd focus on problems if you meet one. The best solution is as always put everything into openSUSE:Factory and build it together. Regarding your libatlas3 problem: * package has disabled build in science * is failing in Education * is missing in openSUSE:Factory so, to fix it you need to fix in Education or science and submit it to openSUSE:Factory to solve your problem. I hope I covered all those topics and it helps you a bit. Best regards, S_W On Wed, Jun 29, 2016 at 11:58:08PM -0400, Jason Newton wrote:
FYI I experimented with a python:stable in my home project (home:jenewton:python:stable). I get a build error on libatlas3 coming from devel:languages:python3, which I've linked the project to, along with devel:languages:python:Factory. libatlas3 is linked to from the Factory project, but that package isn't there anymore. I have many inherited packages but it seems like there's no packages available this experimental python:stable repository - is this normal when using linked projects? Here's the meta conf:
<project name="home:jenewton:python:stable"> <title>Python Stable</title> <description>Latest Python stable packages</description> <link project="devel:languages:python:Factory"/> <link project="devel:languages:python3"/> <person userid="jenewton" role="maintainer"/> <repository name="openSUSE_Leap_42.1"> <path project="openSUSE:Leap:42.1" repository="standard"/> <arch>x86_64</arch> </repository> </project>
TLDR: Is Factory libatlas3 is broken?
-Jason
On Sun, Jun 26, 2016 at 11:03 PM, Jason Newton
wrote: adding some explicit maintainers to those projects (pulled from OBS
pages). Sorry for the repost - toggled off plain text.
I noticed devel:languages:python3 and it seems to depend on
devel:languages:python:Factory which I guess in theory provides the
mentioned functionality but I don't think this is clean enough. In
particular I don't have expectation Factory repositories of any sort
as a stable branch.
So - can the maintainers of these projects create a stable cohesive
variety? If you want to internally link the python package from
Factory, be my guest - but the expectation is something like latest
for the kernel or Qt (due to all the dependency packages). Offering
the latest stable build of python with all related (and c-based)
packages is important to any distribution/windows IMHO.
If I've missed something here, please let me know - I only stumbled
onto the python3 side project by accident - I didn't see it written
anywhere.
-Jason
On Fri, Jun 24, 2016 at 3:41 AM, Dave Plater
wrote: On 24/06/2016 02:58, Jason Newton wrote:
Hi,
I noticed a great reason to use python 3.5 today - PEP 465 - A
dedicated infix operator for matrix multiplication. This takes a
great deal of pain out of numeric programming with python and this is
the first series having it.
But I was surprised to see there seems no way short of tumbleweed /
devel:languages:python:Factory to use it. Is it such a beast to allow
devel:languages:python to support it? Like with KDE, can we have a
devel:languages:python:latest fork that rebuilds all things for 3.5?
Keep in mind 3.5 series has been available since last September with
the last release in start of December!
-Jason
+1 I need python 3.5 in Leap:42.2 for a blender update, blender since 2.77 no longer builds against python 3.4
Dave P
--
To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org
To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
-- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Hi Tomáš,
I just wanted to quickly mention that I don't want tumbleweed for this
purpose - I would like it to be available for the non rolling-release
distribution.
-Jason
On Thu, Jun 30, 2016 at 4:25 AM, Tomáš Čech
Hi Jason,
sorry it took me so long to response. I'm deep in Hackweek not following outside world much.
I found confusing that you miss python 3.5 in Tumbleweed. I'm running Tumbleweed and yet:
$ python3 -V Python 3.5.1
# LANG=C zypper se -s --match-exact python3 Loading repository data... Reading installed packages...
S | Name | Type | Version | Arch | Repository --+---------+---------+-----------+--------+----------- i | python3 | package | 3.5.1-3.4 | x86_64 | repo-oss v | python3 | package | 3.5.1-3.4 | i586 | repo-oss
Regarding the d:l:python3:latest, if you're concerned about the python version used, we already use the highest version in distribution, if you are concerned that the set of packages is smaller in d:l:p3 than in d:l:p, there is unfortunate current state and Jan Matejek is working on build changes so in future there should be both Python 2.* and Python 3.* modules be built from the same source package within the same project (at least that is how I understand the plan). In the meantime you can submit the packages you miss and do the changes manually.
I can't say much about cohesivness of the build but I guess it should be fine and I'd focus on problems if you meet one. The best solution is as always put everything into openSUSE:Factory and build it together.
Regarding your libatlas3 problem:
* package has disabled build in science * is failing in Education * is missing in openSUSE:Factory
so, to fix it you need to fix in Education or science and submit it to openSUSE:Factory to solve your problem.
I hope I covered all those topics and it helps you a bit.
Best regards,
S_W
On Wed, Jun 29, 2016 at 11:58:08PM -0400, Jason Newton wrote:
FYI I experimented with a python:stable in my home project (home:jenewton:python:stable). I get a build error on libatlas3 coming from devel:languages:python3, which I've linked the project to, along with devel:languages:python:Factory. libatlas3 is linked to from the Factory project, but that package isn't there anymore. I have many inherited packages but it seems like there's no packages available this experimental python:stable repository - is this normal when using linked projects? Here's the meta conf:
<project name="home:jenewton:python:stable"> <title>Python Stable</title> <description>Latest Python stable packages</description> <link project="devel:languages:python:Factory"/> <link project="devel:languages:python3"/> <person userid="jenewton" role="maintainer"/> <repository name="openSUSE_Leap_42.1"> <path project="openSUSE:Leap:42.1" repository="standard"/> <arch>x86_64</arch> </repository> </project>
TLDR: Is Factory libatlas3 is broken?
-Jason
On Sun, Jun 26, 2016 at 11:03 PM, Jason Newton
wrote: adding some explicit maintainers to those projects (pulled from OBS
pages). Sorry for the repost - toggled off plain text.
I noticed devel:languages:python3 and it seems to depend on
devel:languages:python:Factory which I guess in theory provides the
mentioned functionality but I don't think this is clean enough. In
particular I don't have expectation Factory repositories of any sort
as a stable branch.
So - can the maintainers of these projects create a stable cohesive
variety? If you want to internally link the python package from
Factory, be my guest - but the expectation is something like latest
for the kernel or Qt (due to all the dependency packages). Offering
the latest stable build of python with all related (and c-based)
packages is important to any distribution/windows IMHO.
If I've missed something here, please let me know - I only stumbled
onto the python3 side project by accident - I didn't see it written
anywhere.
-Jason
On Fri, Jun 24, 2016 at 3:41 AM, Dave Plater
wrote: On 24/06/2016 02:58, Jason Newton wrote:
Hi,
I noticed a great reason to use python 3.5 today - PEP 465 - A
dedicated infix operator for matrix multiplication. This takes a
great deal of pain out of numeric programming with python and this is
the first series having it.
But I was surprised to see there seems no way short of tumbleweed /
devel:languages:python:Factory to use it. Is it such a beast to allow
devel:languages:python to support it? Like with KDE, can we have a
devel:languages:python:latest fork that rebuilds all things for 3.5?
Keep in mind 3.5 series has been available since last September with
the last release in start of December!
-Jason
+1 I need python 3.5 in Leap:42.2 for a blender update, blender since 2.77 no longer builds against python 3.4
Dave P
--
To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org
To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
-- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
-- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
participants (3)
-
Jason Newton
-
Tomáš Čech
-
Tomáš Čech