What do you/the packaging macros do when a pypi name is taken by two
different packages? (For instance, how setuptools and distribute used the
same name)
-Toshio
On Fri, Jun 11, 2021, 6:24 AM Petr Viktorin wrote:
> I've proposed the new guidelines as a Fedora change:
> https://fedoraproject.or
On Wed, Apr 14, 2021 at 5:18 AM Miro Hrončok wrote:
>
> Hello Pythonistas.
>
> I'd like to be able to automatically handle Python "namespace" packages from
> our
> packaging macros.
>
> The problem:
>
> Several Python packages share a "namespace", let's take an artificial example
> with food.spam
On Mon, Apr 1, 2019 at 7:40 PM Orion Poplawski wrote:
> I've noticed a few times now where a python package unexpectedly
> produces an egg-info file instead of a directory. This is particularly
> troubling in light of rpm's inability to replace a directory with a file:
>
> https://fedoraproject.
On Sat, Jun 30, 2018, 5:59 AM Miro Hrončok wrote:
> During the 3.7 boostrapping of the interstitial sequence of Python 3
> packages, I have noticed it includes a lot of packages that are only
> intended as Python 3 stdlib backports for older Pythons.
>
In general, I think this is a good effort h
On Fri, Mar 23, 2018, 9:50 AM Petr Viktorin wrote:
> On 03/23/18 16:43, Toshio Kuratomi wrote:
> >
> >
> > On Fri, Mar 23, 2018, 8:13 AM Petr Viktorin > <mailto:pvikt...@redhat.com>> wrote:
> >
> > On 03/23/18 15:15, Toshio Kuratomi wrote:
> &
On Fri, Mar 23, 2018, 8:13 AM Petr Viktorin wrote:
> On 03/23/18 15:15, Toshio Kuratomi wrote:
> > Something that occurred to me last night, rather than a conditional on
> > Fedora version, is there a macro that we could provide to mean python2
> > is available in this Fedo
Something that occurred to me last night, rather than a conditional on
Fedora version, is there a macro that we could provide to mean python2 is
available in this Fedora version? That way packagers wanting to support
their packages on the versions of python that the platform ships can
conditionali
On Sat, Nov 18, 2017 at 5:28 AM, Nick Coghlan wrote:
>
> Ah, OK - this makes sense.
>
> Framing it in terms of the required input file, the two most suitable
> names would be:
>
> * "pyproject.toml compatible spec files"
> * "setup.py only spec files"
>
> I'd suggest keeping the current wheel-cent
On Thu, Nov 16, 2017 at 8:43 PM, Nick Coghlan wrote:
> On 17 November 2017 at 11:55, Toshio Kuratomi wrote:
>>
>> On Thu, Nov 16, 2017 at 5:37 PM, Nick Coghlan wrote:
>> > So the two possible approaches are:
>> >
>> > * traditional sdist: "set
On Thu, Nov 16, 2017 at 5:37 PM, Nick Coghlan wrote:
> On 17 November 2017 at 01:51, Toshio Kuratomi wrote:
>>
>> On Nov 16, 2017 4:59 AM, "Nick Coghlan" wrote:
>
>
>>
>> Rather than emphasising the absence of setup.py, I'd emphasise the use of
&
On Nov 16, 2017 4:59 AM, "Nick Coghlan" wrote:
On 16 November 2017 at 22:33, Miro Hrončok wrote:
> Adding the link makes sense to me. Adding all the macros definition to the
> wiki does not make sense to me, but form different reasons. I think that
> having %py3_build_egg and %py3_install_egg t
I think it is better if the build system sets LANG=C.UTF-8, not the
python specific macros.
On Thu, Jun 1, 2017 at 8:56 AM, Miro Hrončok wrote:
> Hi Pythonistas.
>
> Regarding our Python 3 C.UTF-8 locale coercing [1], aka PEP 538 [2].
>
> As you probably know, we build RPM packages with the C loc
jinx ;-)
On Thu, Dec 15, 2016 at 4:38 AM, Nick Coghlan wrote:
> On 15 December 2016 at 21:17, Toshio Kuratomi wrote:
>> My one concern is precisely this variety. For instance, if I get a
>> report that my application is raising a UnicodeError on RHEL7 when run
>> under c
On Wed, Dec 14, 2016 at 10:40 PM, Nick Coghlan wrote:
> I opened an issue and attached a patch at
> https://bugzilla.redhat.com/show_bug.cgi?id=1404918
>
> I also cross-linked it with the most recent upstream issue at
> http://bugs.python.org/issue28180
>
Comments on the patch:
* In: http://bugs
On Mon, Dec 12, 2016 at 1:39 AM, Nick Coghlan wrote:
> I don't anticipate any major concerns with downstream redistributors
> adding this behaviour, as the main thing that makes us nervous about
> globally changing the default upstream is the sheer variety of Linux
> distros out there, and the fa
On Sun, Dec 11, 2016 at 3:24 AM, Thomas Spura wrote:
>
> To change the default encoding for python was proposed a while ago [1], but
> was finally dropped again, as upstream didn't agree to this change. Did
> anything changed here from upstream python?
>
> Best,
>Thomas
>
> [1] https://fedora
On Dec 1, 2016 6:58 AM, "Petr Viktorin" wrote:
>
> On 12/01/2016 02:42 PM, Neal Gompa wrote:
>>
>> On Thu, Dec 1, 2016 at 8:36 AM, Igor Gnatenko
wrote:
>>>
>>> On Wed, Nov 30, 2016 at 2:53 PM, Tomas Orsava
wrote:
On 11/30/2016 02:44 PM, Neal Gompa wrote:
>
>
> On Wed, Nov 3
On Feb 22, 2016 6:15 PM, "Nick Coghlan" wrote:
>
> On 22 February 2016 at 18:25, Robert Kuska wrote:
>>
>>
>>
>> - Original Message -
>> > From: "Martin Bukatovic"
>> > To: python-devel@lists.fedoraproject.org
>> > Sent: Monday, February 22, 2016 12:04:56 AM
>> > Subject: my project's py
On Tue, Jan 05, 2016 at 08:07:22PM -0700, Orion Poplawski wrote:
> So, I've started packaging up a bunch of python3 only packages for EPEL7 for
> packages that were already in RHEL7. I've started by packaging the latest
> version of the modules:
>
> python34-py.noarch 1.4.30-2.el7
On Sun, Dec 20, 2015 at 01:29:10PM -0500, Ben Rosser wrote:
>
> What's the right thing to do here? Replace pdfminer? Ship
> python3-pdfminer-six,
> have it provide python3-pdfminer, and keep using the original package for
> Python 2? Do nothing, and wait and see what happens upstream?
>
It's a t
On Wed, Nov 18, 2015 at 5:27 AM, Neal Gompa wrote:
> On Wed, Nov 18, 2015 at 2:48 AM, Nick Coghlan wrote:
>> I'd been thinking using "pip install" instead of "setup.py install" in
>> the build macros would be sufficient, but I now realise that isn't the
>> case - if a project uses flit (for examp
On Nov 17, 2015 8:18 AM, "Neal Gompa" wrote:
>
> I see the problem you are describing, but how do you solve it currently?
>
Currently we use manually specified dependencies with package names here.
So when python2.6-foo is built, the packager specifies a dependency on
python2.6-setuptools.
> That
On Nov 17, 2015 6:47 AM, "Neal Gompa" wrote:
>
> On Tue, Nov 17, 2015 at 9:44 AM, Toshio Kuratomi
wrote:
> > One thing I would change, though: instead of python2dist(name) use
> > python2.7dist(name). A module built for python 2.7 won't be able to
import
>
On Nov 17, 2015 6:06 AM, "Nick Coghlan" wrote:
>
> On 17 November 2015 at 23:25, Neal Gompa wrote:
> > As for naming, I'm all ears for a better name, because if the "egg"
> > name is going away, I'd rather it not continue to say that.
>
> My suggestions would be either:
>
> python2dist(name)/
On Apr 15, 2015 2:57 AM, "Robert Kuska" wrote:
> pip is not a application, even though it is not used via import statement
both python3 and python2
> versions provides different functionality (python-pip installs python2
packages and python3-pip
> installs python3 packages), therefore it is a *mo
On Feb 25, 2015 3:14 PM, "Nick Coghlan" wrote:
> For those not following along with the FPC ticket, Toshio and Tomspur
> have a nice write-up of the options at
> https://etherpad.mozilla.org/2Uqk0ikCll
>
> I came back to this question myself due to a couple of different
> ideas, discussed in http
On Wed, Jan 28, 2015 at 11:59:01AM -0500, Bohuslav Kabrda wrote:
> - Original Message -
> > On Tue, Jan 27, 2015 at 06:26:26AM -0500, Bohuslav Kabrda wrote:
> > >
> > > Current state:
> > > - Up until F21, maintainers were encouraged to build applications with
> > > Python 2, but weren't d
On Tue, Jan 27, 2015 at 10:50:07PM +1000, Nick Coghlan wrote:
> >
> > %if 0%{?fedora}
> > %global default_python python3
> > %else
> > %global default_python python
> > %endif
>
> I'm wary of this proposed solution mostly due to the fact that in the
> middle of last year, the Beaker team had to go
On Tue, Jan 27, 2015 at 06:26:26AM -0500, Bohuslav Kabrda wrote:
>
> Current state:
> - Up until F21, maintainers were encouraged to build applications with Python
> 2, but weren't discouraged from building with Python 3.
Note -- this isn't quite right. If an application could run with either
p
On Thu, Dec 04, 2014 at 11:18:58PM +1000, Nick Coghlan wrote:
>
> I think these are good reasons to default to using the dash if its
> Fedora adding it. The guideline could be something like "For Python
> executables, also provide symlinks with a '-X' and '-X.Y' suffix,
> unless upstream already p
On Thu, Dec 04, 2014 at 08:10:39AM -0500, Bohuslav Kabrda wrote:
> >
> > * sphinx-build-v0.9
> > * sphinx-build-2-v0.9
> > * sphinx-build-2.7-v0.9
> > * sphinx-build-3-v0.9
> > * sphinx-build-3.7-v0.9
>
> I'd rather see sphinx-build-v0.9-3.4. IMO keeping the Python version at
> the very end in ev
On Thu, Dec 04, 2014 at 12:51:40AM +1000, Nick Coghlan wrote:
>
> On 4 Dec 2014 00:38, "Bohuslav Kabrda" wrote:
> >
> > So here are my proposals for changes in current guidelines [2]:
> > - In [3], it says "If the executables provide the same functionality
> independent of whether they are run on
I've stepped back from packaging for the most part but I think this is a
great idea. When I was active I'd often find something to cleanup in
python packaging for each release (pil => pillow; removing
python-setuptools-devel). A python-sig group would definitely help with
future cleanups like tho
On Mon, Aug 11, 2014 at 08:01:23PM +0200, bmorbach wrote:
> Hi everyone!
>
> I've been doing some work towards reproducible builds in Fedora (mostly
> with various upstreams so far) and one of the elephants in the Room are
> obviously Pythons .pyc and .pyo files.
>
> As those contain the mtime of
On Dec 10, 2013 6:26 AM, "Bohuslav Kabrda" wrote:
>
> - Original Message -
> > On 11/28/2013 12:42 AM, Bohuslav Kabrda wrote:
> > > I hope I covered all the important points. Basically, we can make
this work
> > > in a way acceptable for upstream, if we package setupttols and pip as
> > >
On Wed, Dec 04, 2013 at 01:36:53PM +0100, Dridi Boukelmoune wrote:
> On Wed, Dec 4, 2013 at 1:18 PM, Bohuslav Kabrda wrote:
> > - Original Message -
> >> Dne 4.12.2013 12:37, Bohuslav Kabrda napsal(a):
> >> > (tkinter is actually a subpackage of python itself)
> >>
> >> I guess you know wh
On Wed, Dec 04, 2013 at 02:41:30PM -0500, Ralph Bean wrote:
> Back in August, the {__python} macro was deprecated in favor of
> {__python2}. This is cool as it paves the way for an eventual python3
> takeover.
>
> https://fedoraproject.org/w/index.php?title=Packaging:Python&diff=350838&oldid=3508
In November of 2009, in time for Fedora 13, we solved a packaging issue in
the main python package that allowed us to remove a split in our
python-setuptools package. Instead of needing a separate
python-setuptools-devel subpackage for easy_install the python-setuptools
package could now contain a
The Change page for python3 as default has a pretty empty entry for policies
and guidelines. Just, "discuss with FPC"; no list of what to actually change.
We should start working on fleshing that out.
Here's one that should be fairly easy:
* https://fedoraproject.org/wiki/Packaging:Python#Guidel
On Wed, Aug 21, 2013 at 12:44:45PM +0200, Miro Hrončok wrote:
>
> The latter is awful. What we actually somehow could do is to generate
> pypy2-foo from python-foo SRPM and patch/tweak Bugzilla to allow
> aliases. Then simple add (by some script) {python,pypy}{2,3}-foo to
> link to python-foo so u
On Wed, Aug 21, 2013 at 02:09:33AM -0400, Bohuslav Kabrda wrote:
> - Original Message -
> > Greetings everyone, we had a productive session at flock and actually
> > covered everything that was in my email message about a potential agenda.
> > Here's the notes:
> >
> > https://fedoraprojec
Greetings everyone, we had a productive session at flock and actually
covered everything that was in my email message about a potential agenda.
Here's the notes:
https://fedoraproject.org/wiki/User:Toshio/Flock2013_Python_Guidelines
Note that we now need to:
1) Turn the notes into a guideline dr
On Mon, Jul 22, 2013 at 10:28:33AM +1000, Nick Coghlan wrote:
> -BEGIN PGP SIGNED MESSAGE-
>
> Are Matthew's replies stuck in the python-devel moderation queue?
> (Just realised the likely reason I'm only seeing half this
> conversation...)
>
> Hmm, also just realised I've been hitting Re
On Mon, Jul 22, 2013 at 10:15:31AM +1000, Nick Coghlan wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On 07/20/2013 06:11 AM, Toshio Kuratomi wrote:
> > pythonic is a very vague statement and I wouldn't consider most of
> > your list to be examples of
On Fri, Jul 19, 2013 at 02:41:23AM -0400, Bohuslav Kabrda wrote:
> - Original Message -
> > On Thu, Jul 18, 2013 at 11:24:22AM -0400, Bohuslav Kabrda wrote:
> > > Hi all,
> > > as a new Fedora Python maintainer, I have set myself a goal of moving
> > > Fedora to Python 3 as a default.
> >
On Wed, Jul 3, 2013 at 10:33 AM, Toshio Kuratomi wrote:
>
> *Do not* start mass rebuilding all your python packages with the expectation
> that this is the last major change for this release cycle -- there's
> a setuptools-0.8 package that is due out in a week or two and I wou
Just a note:
bkabrbda and dmalcolm are both unable to attend flock in person due to
other commitments at home. bkabrda should be able to attend via IRC
if we decide to do that. (I think dmalcolm could as well but I didn't
ask him specifically).
-Toshio
__
On Sun, May 26, 2013 at 8:18 PM, Nick Coghlan wrote:
> On 05/25/2013 04:11 AM, Toshio Kuratomi wrote:
>>
>> On the pre-registration list I currently see: mrunge, ncoghlan, toshio.
>> This seems tantalyzingly close to enough people to work on at least one of
>> the areas
(For those who are subscribed to this list as well, forgive me for CC'ing --
I hadn't recalled seeing you post here, so I wasn't sure if you were on the
list too).
Hey, who's going to flock[1]_? I'm thinking of adding a hackfest for discussing
a new version of the Python Guidelines if we have the
On Tue, May 07, 2013 at 01:57:01PM +1000, Nick Coghlan wrote:
> On 05/06/2013 10:43 PM, Bohuslav Kabrda wrote:
> >Hi all,
> >as mentioned in [1], I'd like to start a discussion about proposed Python
> >macros.
> >The full macro file can be seen at [2] and an example diff of converted spec
> >at [
On Tue, Mar 05, 2013 at 01:51:35PM +1000, Nick Coghlan wrote:
> I'll be at PyCon US next week (from the day before the language
> summit through to the end of the sprints). I just wanted to see who
> else will be around at the conference - it would be good to meet more
> Fedora Python folks in pers
On Sat, Nov 10, 2012 at 03:06:51PM -0500, Dylan Semler wrote:
> I believe polib provided by the current python-polib rpm supports both python2
> and python3[1]. However, the rpm only provides source in the python2.7/
> site-packages directory and there is no python3-polib rpm.
>
> I don't know t
On Wed, Sep 12, 2012 at 3:14 PM, Toshio Kuratomi wrote:
>
> Mapping of pypi distribution names was something that I looked into a small
> bit with some Canonical people at PyCon two years ago. IIRC, it was part of
> trying to map distribution packages with each other and with pypi i
On Wed, Sep 12, 2012 at 01:41:22PM +1000, Nick Coghlan wrote:
> I'll likely be helping to guide updates to the Python packaging format
> standards over the coming months. While they won't hit the standard
> library until 3.4, there will likely be third party tool support in
> earlier versions (sinc
On Sat, Aug 04, 2012 at 03:50:56AM -0400, Bohuslav Kabrda wrote:
> - Original Message -
> > On Fri, Aug 03, 2012 at 04:42:02AM -0400, Bohuslav Kabrda wrote:
> > > - Original Message -
> > > > On Fri, Aug 3, 2012 at 8:57 AM, Bohuslav Kabrda
> > > >
> > > > wrote:
> > > > > Hi,
> > >
On Fri, Aug 03, 2012 at 03:55:26AM -0400, Bohuslav Kabrda wrote:
> - Original Message - (From Nick)
> >
> > I believe Fedora uses Python for more core OS infrastructure than
> > Ubuntu
> > does, so it's a bigger migration challenge. Does anaconda run on
> > Python
> > 3? Does yum?
> >
>
On Tue, Jul 31, 2012 at 11:29:02AM -0400, David Malcolm wrote:
> For python packages that build python 2 and 3 subpackages from one
> shared src.rpm, the current example on
> http://fedoraproject.org/wiki/Packaging:Python#Example_spec_file
> has this fragment:
> %if 0%{?fedora} > 12 || 0%{?rhel
On Fri, Jul 27, 2012 at 12:27:31PM +1000, Nick Coghlan wrote:
> On 07/27/2012 07:28 AM, David Malcolm wrote:
> > With my proposed approach, you have to opt-in, your code can say: when I
> > say "xml", I really mean "xml", not "_xmlplus".
>
> You can do much the same thing at the application level
Last week I stumbled upon the fact that the newest python-docutils does not
pass its unittests if PyXML is installed. Looking into the issue brought me
to the conclusion that retiring PyXML may be the best thing to do as rrakus
(the current PyXML maintainer) was interested in doing in February:
h
On Mon, Jul 23, 2012 at 03:30:13PM -0400, David Malcolm wrote:
> dmalcolm: that should be fine. how many packages are we
> talking about?
> and how long should it take?
> about 30 iirc
>
Just an FYI: 100 packages is a better estimate.
$ lftp
mirrors.tummy.com:/pub/fedora.redhat.com/fedora/linu
On Tue, May 01, 2012 at 12:25:30PM +0700, Nick Fenwick wrote:
> On 05/01/2012 11:47 AM, Nick Fenwick wrote:
>
> python-2.7.2-5.2.fc16.x86_64
>
>
> It seems that because I had only the 64 bit python rpms installed, I didn't
> have the 32 bit libraries.
>
>
> ln -s /usr/lib64/libpython2.
!/usr/bin/python -tt
# -*- coding: utf-8 -*-
from distutils.core import setup
setup(name='test',
version='1.0',
description='Test',
author='Toshio Kuratomi',
author_email='tos...@fp.o',
license='MIT',
On Fri, Oct 29, 2010 at 05:45:09PM -0400, Luke Macken wrote:
> Just a heads up to some new behavior that I noticed in F14.
>
> When python-distutils-extra is installed, it will cause pylint to be run
> against your project automatically when `python setup.py sdist` is
> called. It installs DistUt
For those who aren't also subscribed to the python-dev mailing list :-),
Dave and Neal's posts about fpconst sparked some interest in porting work
there. Talking with Barry Warsaw we'd like to use the
python-port...@python.org mailing list to coordinate efforts to port so that
distros can help eac
sys.stdout.write(sys.version[:3])")}
-Toshio
> Robin
>
> On Thu, Sep 16, 2010 at 12:17 AM, Toshio Kuratomi wrote:
>
> On Wed, Sep 15, 2010 at 07:25:49PM +0800, Robin Lee wrote:
> > For a more concrete example:
> https://bugzilla.redhat.com/show_bug.cgi?id=
When we've talked about this before, in the Packaging Committee we
haven't really cared to stipulate one proper way that maintainers must
follow since there's several possible ways which all seem equally
valid. Inconsistency by itself is not a problem. If it's causing an
issue then it would be so
On Wed, Sep 15, 2010 at 07:25:49PM +0800, Robin Lee wrote:
> For a more concrete example:
> https://bugzilla.redhat.com/show_bug.cgi?id=567348
> I want to set the python(abi) requirement of the subpackage at buildtime. So,
> I
> want to set it like this:
> Requires: python(abi) = %{py3_ver}
>
>
On Thu, Aug 26, 2010 at 11:39:50AM +0530, Ms. Padmaja Sharma wrote:
>
> Hi
> I am using fedora 9 and python 2.6 but not able to display
> unicode (Assamese/Bengali)when i do proogram in python.
>Can I get some suggestion in this matter to display the unicode.
>
This could be a proble
On Fri, May 28, 2010 at 04:22:21PM -0400, David Malcolm wrote:
> On Thu, 2010-05-27 at 20:39 -0400, Toshio Kuratomi wrote:
> > On Thu, May 27, 2010 at 07:32:23PM -0400, David Malcolm wrote:
> > > I've added a list of Python-related features to our wiki page here:
> >
On Thu, May 27, 2010 at 07:32:23PM -0400, David Malcolm wrote:
> I've added a list of Python-related features to our wiki page here:
> https://fedoraproject.org/wiki/SIGs/Python#Python_Features
>
> Is anyone else working on Python-related Fedora features?
>
You are!
pypy and pynie are good stori
On Sun, Mar 21, 2010 at 05:22:48PM -0400, David Malcolm wrote:
> On Wed, 2010-03-17 at 02:51 -0400, Toshio Kuratomi wrote:
> > On Tue, Mar 16, 2010 at 07:45:27PM -0400, David Malcolm wrote:
> > > Python 2.6.5 and 3.1.2 are due at the end of this week.
> > >
> >
On Tue, Mar 16, 2010 at 07:45:27PM -0400, David Malcolm wrote:
> Python 2.6.5 and 3.1.2 are due at the end of this week.
>
> I plan to build 2.6.5 and 3.1.2 into Fedora 14 as soon as they're
> released (though if any other maintainer wants to do this, feel free!)
>
> My feeling is that they're to
On Sun, Mar 07, 2010 at 11:53:03AM -0500, Toshio Kuratomi wrote:
>
> It's a bit late for incompatible versions so I'm asking for opinions here:
>
> SQLAlchemy-0.6beta1 is out. Should we update the SA package in F-13 to the
> new version? Things that have been depr
It's a bit late for incompatible versions so I'm asking for opinions here:
SQLAlchemy-0.6beta1 is out. Should we update the SA package in F-13 to the
new version? Things that have been deprecated throughout the 0.5 release
cycle have been removed so it's possible that some things will break wit
On Sun, Mar 07, 2010 at 08:48:48AM +, Frank Murphy wrote:
> I don't know Python,
> but want to teach myself.
>
> For my efforts to be useful to Fedora,
> should I start with learning 3.x?
>
ATM everyone is programming in python2. But we're starting to help upstream
modules port to python3.
75 matches
Mail list logo
