[opensuse-factory] devel:languages:python diet reduction
Hello all, We will have to split a bit the d:l:py due to its monstrous size (2700 packages) where we are unable to verify the stack actually kinda works before Tumbleweed integration. We will split it based on common purpose and use d:l:py as base: devel:languages:python:django devel:languages:python:azure devel:languages:python:aws ... If you happen to have some packages or interest in python modules and think of some connection between couple of them please drop me an email for subproject creation and I will happily create it for you and set it up for TW integration. As a bit additional tweak I would move all of the non-Tumbleweed integrated stuff in to different project. At this moment it is full of various linked packages and things that were only added to develprj without being submitted to Tumbleweed. This prompted people to add this project on their released openSUSE versions (leading to quite interestingly broken systems if they do zypper dup with vendor change)... The change will be done by creating special project d:l:py:misc that would have building enabled but publishing disabled. This will hopefully motivate people to properly integrate the packages while not losing all the work that was done on them so far. Cheers Tom [1] https://build.opensuse.org/project/show/devel:languages:python
On Thursday 2018-04-19 12:59, Tomas Chvatal wrote:
We will split it based on common purpose and use d:l:py as base:
devel:languages:python:django devel:languages:python:azure devel:languages:python:aws ...
Maybe is it possible to reduce the nesting and just give it a "utilities:azure" kind of location? -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Jan Engelhardt píše v Čt 19. 04. 2018 v 13:01 +0200:
On Thursday 2018-04-19 12:59, Tomas Chvatal wrote:
We will split it based on common purpose and use d:l:py as base:
devel:languages:python:django devel:languages:python:azure devel:languages:python:aws ...
Maybe is it possible to reduce the nesting and just give it a "utilities:azure" kind of location?
I don't mind, it is up to azure people :) Simply goal is to trim d:l:py. Where it goes should be up to the current maintainers of that stack part -> With this cascade they should retain their permissions without any additional work. Tom
On Thursday, 19 April 2018 20:29:30 ACST, Tomas Chvatal wrote:
Hello all,
We will have to split a bit the d:l:py due to its monstrous size (2700 packages) where we are unable to verify the stack actually kinda works before Tumbleweed integration.
We will split it based on common purpose and use d:l:py as base:
devel:languages:python:django devel:languages:python:azure devel:languages:python:aws ...
If you happen to have some packages or interest in python modules and think of some connection between couple of them please drop me an email for subproject creation and I will happily create it for you and set it up for TW integration.
As a bit additional tweak I would move all of the non-Tumbleweed integrated stuff in to different project. At this moment it is full of various linked packages and things that were only added to develprj without being submitted to Tumbleweed. This prompted people to add this project on their released openSUSE versions (leading to quite interestingly broken systems if they do zypper dup with vendor change)...
The change will be done by creating special project d:l:py:misc that would have building enabled but publishing disabled. This will hopefully motivate people to properly integrate the packages while not losing all the work that was done on them so far.
Cheers
Tom
[1] https://build.opensuse.org/project/show/devel:languages:python
Along with this change I think it would be worth updating the the python packaging guidelines to suggest that applications be they cli or desktop not also providing core libraries should go into the appropriate devel project whether its X11:common, networking etc. unless there is a good reason to keep them in d:l:p (for existing apps this maybe a slow gradual change). -- Simon Lees (Simotek) http://simotek.net Emergency Update Team keybase.io/simotek SUSE Linux Adelaide Australia, UTC+10:30 GPG Fingerprint: 5B87 DB9D 88DC F606 E489 CEC5 0922 C246 02F0 014B -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Simon Lees píše v Pá 20. 04. 2018 v 11:12 +0930:
On Thursday, 19 April 2018 20:29:30 ACST, Tomas Chvatal wrote:
Hello all,
We will have to split a bit the d:l:py due to its monstrous size (2700 packages) where we are unable to verify the stack actually kinda works before Tumbleweed integration.
We will split it based on common purpose and use d:l:py as base:
devel:languages:python:django devel:languages:python:azure devel:languages:python:aws ...
If you happen to have some packages or interest in python modules and think of some connection between couple of them please drop me an email for subproject creation and I will happily create it for you and set it up for TW integration.
As a bit additional tweak I would move all of the non-Tumbleweed integrated stuff in to different project. At this moment it is full of various linked packages and things that were only added to develprj without being submitted to Tumbleweed. This prompted people to add this project on their released openSUSE versions (leading to quite interestingly broken systems if they do zypper dup with vendor change)...
The change will be done by creating special project d:l:py:misc that would have building enabled but publishing disabled. This will hopefully motivate people to properly integrate the packages while not losing all the work that was done on them so far.
Cheers
Tom
[1] https://build.opensuse.org/project/show/devel:languages:python
Along with this change I think it would be worth updating the the python packaging guidelines to suggest that applications be they cli or desktop not also providing core libraries should go into the appropriate devel project whether its X11:common, networking etc. unless there is a good reason to keep them in d:l:p (for existing apps this maybe a slow gradual change).
Feel free to update the wiki, basically core points are: * use singlespec * cli stuff should be python3 only unless really required * If not needed to be for both py2 and py3 whole package should be py3 only Cheers Tom
Hi, On 19.04.2018 12:59, Tomas Chvatal wrote:
Hello all,
We will have to split a bit the d:l:py due to its monstrous size (2700 packages) where we are unable to verify the stack actually kinda works before Tumbleweed integration.
We will split it based on common purpose and use d:l:py as base:
devel:languages:python:django devel:languages:python:azure devel:languages:python:aws
can you enable the same repos for the subprojects as in devel:languages:python please? Cheers, Tom -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 Thomas Bechtold píše v Út 24. 04. 2018 v 16:57 +0200:
Hi,
On 19.04.2018 12:59, Tomas Chvatal wrote:
Hello all,
We will have to split a bit the d:l:py due to its monstrous size (2700 packages) where we are unable to verify the stack actually kinda works before Tumbleweed integration.
We will split it based on common purpose and use d:l:py as base:
devel:languages:python:django devel:languages:python:azure devel:languages:python:aws
can you enable the same repos for the subprojects as in devel:languages:python please?
That will be of course up for the subproject maintainers, but of course by default I don't see any reason why not. Tom -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQIcBAEBCgAGBQJa30fTAAoJEOSiRoyO7jvoXi0P/3iiC83y8MGI7LFVahuiPG6/ vp803tqT7ov8gzum948nj0gkTZb0DEfixyzmQOsBsyo8keeq86oFx5AZRQ/EHoek LrbPHZoY9rBaMs3zvW3Rg0Esv8IGj0SVhtyIx4fehhrwd6pl78zhJ+vojSkzYRv8 MBjuEShUTdtfqyrqhazszhlbBrNWGHz7MtPP66v/BE/WJddFdI64d+DjffDjB35o UFNNneZasLa745SaWlWroCoRGcDVLU35fb7JjwlMSrFmCV1audIAHOwqKR6tkQjd 6mdxVIvqWM/kFDbE6w/En2+VqQRtoqOCa+Lam0viCE7a8C2c8ZSCahK/D+EM5sK6 HgLK2e3ojpC8Ke3LCXB4QextNMWX8PMO0ADF+MnQYK6NBi56Vo6X04PnizDXd5m8 chGHOHPWpWas07C8KPntBCcftfdlIi6WnbZlpHnzUkrFbgw/W8rFZ9dAC8DGMFK+ 6V5MDXZFTBmuxpcmkllOqkhWJL52uURxxxd0gYyhqdG6+30p4w5dKCEktHfMBGgW R4T4LHMkxhifJb0+X0tX+Z6Mzlkc0HMxTRMC2JrBu8a/gp3SQPruR2TIgyTnHJfB F7cKkFxXSVHx8ZxAIL1I9qYpt9TPqquKhvPwFG4VvmCo/FMObgYabyrd1kL49stN TLrFpMru2uYXWLEiEwqp =8uDD -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Hi Tom, On 24.04.2018 17:05, Tomas Chvatal wrote:
Thomas Bechtold píše v Út 24. 04. 2018 v 16:57 +0200:
Hi,
On 19.04.2018 12:59, Tomas Chvatal wrote:
Hello all,
We will have to split a bit the d:l:py due to its monstrous size (2700 packages) where we are unable to verify the stack actually kinda works before Tumbleweed integration.
We will split it based on common purpose and use d:l:py as base:
devel:languages:python:django devel:languages:python:azure devel:languages:python:aws
can you enable the same repos for the subprojects as in devel:languages:python please?
That will be of course up for the subproject maintainers, but of course by default I don't see any reason why not.
So the the maintainers changed while switching to subprojects? I would assume that the maintainers of devel:languages:python are also the maintainers for the subprojects. No? Best, Tom -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On mardi, 24 avril 2018 17.23:08 h CEST Thomas Bechtold wrote:
Hi Tom,
On 24.04.2018 17:05, Tomas Chvatal wrote:
Thomas Bechtold píše v Út 24. 04. 2018 v 16:57 +0200:
Hi,
On 19.04.2018 12:59, Tomas Chvatal wrote:
Hello all,
We will have to split a bit the d:l:py due to its monstrous size (2700 packages) where we are unable to verify the stack actually kinda works before Tumbleweed integration.
We will split it based on common purpose and use d:l:py as base:
devel:languages:python:django devel:languages:python:azure devel:languages:python:aws
can you enable the same repos for the subprojects as in devel:languages:python please?
That will be of course up for the subproject maintainers, but of course by default I don't see any reason why not.
So the the maintainers changed while switching to subprojects? I would assume that the maintainers of devel:languages:python are also the maintainers for the subprojects. No?
Best,
Tom
Why do you want such ideal things, even maintainers status have change in d:l:p from time to time .... blues :-) -- Bruno Friedmann Ioda-Net Sàrl www.ioda-net.ch Bareos Partner, openSUSE Member, fsfe fellowship GPG KEY : D5C9B751C4653227 irc: tigerfoot -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 Thomas Bechtold píše v Út 24. 04. 2018 v 17:23 +0200:
That will be of course up for the subproject maintainers, but of course by default I don't see any reason why not. So the the maintainers changed while switching to subprojects? I would assume that the maintainers of devel:languages:python are also the maintainers for the subprojects. No?
Yes it is inherited, but I mean it in a way where there will be specified maintainer ie. for the azure that knows way more than me about the subject, thus I won't personaly have to "bother" doing anything in that part of the subproject, thus it will be his decision. But you are really right that inheritance means that everyone with d:l:py access can change/accept anything as needed. Tom PS: this is copy of the mail I sent to Thomas directly as my mail client failed me :) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQIcBAEBCgAGBQJa31E5AAoJEOSiRoyO7jvox7sP/jXwJRmVv8JgWFq04FWyj8vY 8VTbSzSljUra/kYxtwhEKBzR3aCgYX/N/WbShKTcjkp5OPY1c/ljQi6f0gD++ifq 8r7BerRHQCnMFzgrMLQd12AMIrsQuoD7Y9rCPokkJPLqNz2a+ku600ylXyBkKZVI Iciqt4B3jh0Yypjm472LL2CVXRNB753Z5Zxyn0kxaS14vVre3gLPBVb/I/q1dv3g mi0ZPGXhrAZr3RbUgc145GX+xH5k5wtCK0hanOJD1N5wE6MmxIQruguawqEAV8jI xfCx565AAAZkYBip1HtOPac1/5CD26wDSPExnlPPaOz9ZokzNl0ABO4fhqQ8C1C2 R4yT0jYHKSnvzrex337k5V7yvxXwZn0xUob2dL/RjGK6DTfvMwN2OJFw0ZV7zN/D +AidCOHtM1OfYpQESxCam29OeIHKUHX1UEcSpe3bPHjhVtFE5HGzp96WCCRqDUyJ gl3/n1DaInMg1RQV0hy4sCw9eppzzOhwuIr19HlHigzEMOXnfZM2XYyByhjzIYT4 I2F0mS92L8xxTAF/mVHtJacxR/jEb9zDLRn1xLHH/DZzhEov97PtbMPPyPaSzgyA Io5KDtpQbfy+J4QqCw+yM7VwNecx6mSiaJyAPsOZyGaCE+GDBSQsroTvLVcTSEvG 9E9nQ1qTOeDihVNArbMi =K6w1 -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 Hi all, We are progressing a bit with dlpy so I thought about giving you status report :) For now all the non-integrated packages were moved to devel:languages:python:misc. In order to resurrect anything just branch it and submit to devel:languages:python (or the respective subprj, see bellow). dlpy still contains some non-integrated packages that popped up over weekend, but simply put from now on everything that resides there shall be commited to Tumbleweed and be on distro and also it must be succeeding its build :) (for now there are some unresolvables and fails, that is to be addressed). There are already some shiny subprojects :django - eh obvious :aws - amazon web services tools There will be more shiny subprojects in following weeks: azure - MS Azure flask - all the flask stuff pytest - all the pytest modules jupyter - all the jupyter stuff zope - well wonder about this one but zope project is rewritting stuff to py3... If anyone wants to join and help to get all of the above complete please feel free to :) Cheers Tom -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQIcBAEBCgAGBQJa6Cc3AAoJEOSiRoyO7jvoHNoQAJ7V8l9Dm/eiDB9bzmc7KVl5 KjQNYc+r9kQNd0n21yUPr0RVYeRqQs1osYp8jo5ZcFvndfZQ1OFzlOy2lb/brdtv 9VnP+aQFH/NBQRsvjJNGc1+jYv0fjznTu/nEVppynUrYK7cXM0153v7a3m9uJsrZ cKCYJZRDjC6euCXhTdGO26EpB28fR+Ef64SvHR77AlRepks2Fbp/JI8jGze5AAVD 77r8xes+zVY4nMyKv5sTqt5Ha4ZnGk9O0Q2aFape+gmbaXUAtmhLBDvECts7/WgK gqjXFs/4kK5mhL8pJo5DhwlLLm8CJuobOCczD4UEVNX1O4Va8Kq2u+/fn8KSgL+3 fdj/LB8ti8EGRBV1e3rkbCnRvFHuRBVl71r/DhpUSoz4zYMQOseZr+0BbgKMoqMY GLPxYoS+kNoy0ki3psfvJt36bE1HQnfU191iUaSWockx2Slp40hw6gBFD66O8Jmn rn7rCl1zk8UyUPXsFgHIgjw0rs9B4McDUvcte+2SVFy0DsX/Dh1ZW+RF8GS2Hp2d ml+Fu0a01aY5TMFgDLt6yQOlU4ODEKCmEdfNsiMD0Z8UmCOVKhN/iectH6nitRrU b73PIOxMa+QvIlFhfbLvlTK4Lr6qeuTLAU3c9U2ZaFiGAJ+QhZpMRiVgYf5a/lJi 4Eb5mn8jtfq5VDjPYrTY =YouX -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Hi Tomas,
There will be more shiny subprojects in following weeks: pytest - all the pytest modules
I'm missing the reason for splitting out the pytest modules. First of all it is only 31 packages (so not a large amount) and now we fight with cyclic dependencies (:pytest needs dlp: to build, but also dlp packages need :pytest to build for older distributions). What was the compelling reason to create this separation? While re-reading this mail thread it didn't become obvious to me. Thanks, Dirk -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
participants (6)
-
Bruno Friedmann -
Dirk Müller -
Jan Engelhardt -
Simon Lees -
Thomas Bechtold -
Tomas Chvatal