Hi Joseph,
On Thu, 13 Dec 2012 14:53:04 +0800
Joseph Wang joequ...@gmail.com wrote:
Looking over this page:
https://wiki.mageia.org/en/Python_policy
* python-pyp2rpm is undergoing review right now. Once it's in
cauldron, I'd like to
point to that package as something that packagers you
Le 13/12/2012 09:00, Shlomi Fish a écrit :
* Also for grouping. I'd like to add a rule that Development/Python
is intended for packages
which provide general development libraries for python, and if the
library fits into an obvious
other category (i.e. python routines for cosmology
Hi,
Le 13/12/2012 09:00, Shlomi Fish a écrit :
Hi Joseph,
On Thu, 13 Dec 2012 14:53:04 +0800
Joseph Wangjoequ...@gmail.com wrote:
[...]
* I'd like to add a rule (which is followed by current packages) that
the prefix py should
generally be removed from a package name. For example pyopencl
On Thursday 13. December 2012 15.24, Claire REVILLET wrote:
I disagree on that point: software and libraries names are choose by the
developers.
Who are we to change them ?
Adding python- at the beginning of the package name for our own
organization is one thing, changing the name is
Le 13/12/2012 15:24, Claire REVILLET a écrit :
Hi,
Le 13/12/2012 09:00, Shlomi Fish a écrit :
Hi Joseph,
On Thu, 13 Dec 2012 14:53:04 +0800
Joseph Wangjoequ...@gmail.com wrote:
[...]
* I'd like to add a rule (which is followed by current packages) that
the prefix py should
generally be
Le 13/12/2012 15:43, Guillaume Rousse a écrit :
Le 13/12/2012 15:24, Claire REVILLET a écrit :
Hi,
Le 13/12/2012 09:00, Shlomi Fish a écrit :
Hi Joseph,
On Thu, 13 Dec 2012 14:53:04 +0800
Joseph Wangjoequ...@gmail.com wrote:
[...]
* I'd like to add a rule (which is followed by current
Claire REVILLET a écrit :
Hi,
Le 13/12/2012 09:00, Shlomi Fish a écrit :
Hi Joseph,
On Thu, 13 Dec 2012 14:53:04 +0800
Joseph Wangjoequ...@gmail.com wrote:
[...]
* I'd like to add a rule (which is followed by current packages) that
the prefix py should
generally be removed from a
On Thu, 13 Dec 2012 14:53:04 +0800
Joseph Wang joequ...@gmail.com wrote:
Looking over this page:
https://wiki.mageia.org/en/Python_policy
* python-pyp2rpm is undergoing review right now. Once it's in
cauldron, I'd like to
point to that package as something that packagers you should use
On 13/12/12 06:53, Joseph Wang wrote:
Looking over this page:
https://wiki.mageia.org/en/Python_policy
* I'd like to add a rule (which is followed by current packages) that
the prefix py should
generally be removed from a package name. For example pyopencl should be called
python-opencl.
2011/7/16 Michael Scherer m...@zarb.org:
Either 2 rpms with the same source, or 1 rpm that generate 2 sub rpms.
I would rather use 2 separate rpms, as this seems to be easier.
I see, so really treating python2 and python 3 as 2 differents languages
why not, that will increase the number of
Le mercredi 13 juillet 2011 à 09:51 +0200, philippe makowski a écrit :
2011/7/13 Michael scherer m...@zarb.org:
I would be in favor of treating python2 and python 3 as 2 differents
languages.
The rational is that :
- we cannot garantee to have support for both
- we will likely have
2011/7/13 Michael scherer m...@zarb.org:
I would be in favor of treating python2 and python 3 as 2 differents
languages.
The rational is that :
- we cannot garantee to have support for both
- we will likely have some module who would be updated only on
python 3 sooner or later
- we will
philippe makowski a écrit :
2011/7/13 Michael schererm...@zarb.org:
I would be in favor of treating python2 and python 3 as 2 differents languages.
The rational is that :
- we cannot garantee to have support for both
- we will likely have some module who would be updated only on
python 3
philippe makowski a écrit :
Hi,
remember this first draft (http://mageia.org/wiki/doku.php?id=python_policy)
that is still a draft
now we have also Python3 so we really need to write our policy
I see mainly two majors points :
1/ pyc, pyo management
2/ having Python2 and Python3
about 1/ :
2011/1/19 Michael scherer m...@zarb.org:
Because that would 1) requires a patch to rpm that we do not have or
2) patch all python packages to had %ghost on all *.pyc, and do a
compilation of
*pyc ( the 2nd part is easy, the first one is slightly harder to automate )
3) do not care about
On Wed, 19 Jan 2011 08:25:23 +0100
Michael scherer m...@zarb.org wrote:
I'm not sure about twice the work: you don't need to track twice the
software releases (except for the interpreter itself), or twice the
upstream patches, etc.
Well, if we handle this like 2 separates languages,
On Tue, Jan 18, 2011 at 08:51:26PM +0100, Antoine Pitrou wrote:
On Mon, 17 Jan 2011 09:21:56 +0100
Michael scherer m...@zarb.org wrote:
There is also the issue on bytecompilation (
https://qa.mandriva.com/show_bug.cgi?id=50484 ).
I have exposed there the various problem, and apart
On Wed, 19 Jan 2011 00:55:40 +0100
Michael scherer m...@zarb.org wrote:
The solution of generating bytecode at install time looks fine. I am
not an RPM specialist though, but if you have non-RPM specific questions
feel free to ask them, I'd be glad to answer.
Well, that's not satisfying
On Wed, Jan 19, 2011 at 02:07:18AM +0100, Antoine Pitrou wrote:
On Wed, 19 Jan 2011 00:55:40 +0100
Michael scherer m...@zarb.org wrote:
The solution of generating bytecode at install time looks fine. I am
not an RPM specialist though, but if you have non-RPM specific questions
feel
On Sun, Jan 16, 2011 at 06:15:52PM +0100, philippe makowski wrote:
Hi,
I though that I can find more time to work on this week end, but
unfortunately it was not the case.
The Mandriva doc is really not a good starter
(http://wiki.mandriva.com/en/Python_packaging_policy)
That's just a
2011/1/17 Michael scherer m...@zarb.org:
On Sun, Jan 16, 2011 at 06:15:52PM +0100, philippe makowski wrote:
Hi,
I though that I can find more time to work on this week end, but
unfortunately it was not the case.
The Mandriva doc is really not a good starter
Le lundi 17 janvier 2011 à 21:03 +0100, philippe makowski a écrit :
2011/1/17 Michael scherer m...@zarb.org:
On Sun, Jan 16, 2011 at 06:15:52PM +0100, philippe makowski wrote:
Hi,
I though that I can find more time to work on this week end, but
unfortunately it was not the case.
The
2011/1/18 Michael Scherer m...@zarb.org:
We can merge part of their policy , I am not against it, I just think we
should not adopt everything :)
Fine
So I'll try to
23 matches
Mail list logo
