Critical Path: New Python version (2.7.6) in Rawhide
by Tomas Radej
Hi,
I have updated Python in Rawhide to version 2.7.6. The build is already
tagged as f21. As far as I checked, the API/ABI should remain the same.
Most patches applied neatly, only a few needed a rebase, and two were
1:1 incorporated upstream.
If something Python-related starts acting up, try looking at this
first, and if this version is indeed the cause, don't hesitate to untag
the build and/or let me know, I will fix it.
Cheers,
--
Tomas Radej <tradej(a)redhat.com>
9 years, 4 months
about mod_wsgi for python3
by 陳貴鑫
Hi, I'm new in this mailing list.
I want to use mod_wsgi with python 3.
but someone tell me mod_wsgi in fedora is compiled with python 2 and
suggest me to recompile it.
However, when i recompile it, it show this message
/usr/lib64/apr-1/build/libtool --silent --mode=link gcc -std=gnu99
-Wl,-z,relro,-z,now -o mod_wsgi.la -rpath /usr/lib64/httpd/modules
-module -avoid-version mod_wsgi.lo -L/usr/lib64
-L/usr/lib64/python3.3/config -lpython3.3 -lpthread -ldl -lutil -lm
/usr/bin/ld: cannot find -lpython3.3
collect2: error: ld returned 1 exit status
apxs:Error: Command failed with rc=65536
.
make: *** [mod_wsgi.la] Error 1
My ./configure argument:
./configure --with-python=/usr/bin/python3 --with-apxs=/usr/bin/apxs
--enable-shared
I want to know what arguments fedora used.
9 years, 4 months
SQLAlchemy 0.9 (python-sqlalchemy)
by Nils Philippsen
Hi everybody,
just a heads up that I'll build python-sqlalchemy-0.9.1 in Rawhide
shortly. If your package uses SQLAlchemy, please check "What's New in
SQLAlchemy 0.9?"[1] for changes that might affect you. And test stuff,
of course.
Nils
[1]: http://docs.sqlalchemy.org/en/rel_0_9/changelog/migration_09.html
--
Nils Philippsen "Those who would give up Essential Liberty to purchase
Red Hat a little Temporary Safety, deserve neither Liberty
nils(a)redhat.com nor Safety." -- Benjamin Franklin, 1759
PGP fingerprint: C4A8 9474 5C4C ADE3 2B8F 656D 47D8 9B65 6951 3011
9 years, 5 months
python compat package change needed
by Toshio Kuratomi
The new setuptools shipped in F20+ has one change that breaks things for
a subset of python packages. I'm proposing a very small guideline change
for the Pyhton Eggs guidelines to address that. Maintainers of backwards
and forward compat packages will likely want to address this as it will
break upgrades of those backwards compat packages from f19 to f20.
When we ship backwards compat pyhton modules we take advantage of a feature
of pythhon eggs to install the multiple versions:
https://fedoraproject.org/wiki/Packaging:Python_Eggs#Multiple_Versions
The guidelines say to use the following command line for performing the
install:
easy_install -m --prefix $RPM_BUILD_ROOT%{_usr} dist/*.egg
In Fedora 19's setuptools package, this resulted in a new directory being
installed into site-packages that held the versioned egg.
In Fedora 20's setuptools package, this command results in a zipped egg file
being installed into site-packages. The zipped egg has the same filename as
the previous directory.
This causes problems for rpm as rpm cannot handle replacing a directory with
a file without jumping through hoops. Because rpm cannot perform that
replacement, we end up with bug reports like this:
https://bugzilla.redhat.com/show_bug.cgi?id=1047570#c0
where the user is unable to upgrade the F19 package to the F20 package.
The solution is to force easy_install to install unzipped eggs rather than
zipped eggs. This can be done via a command line switch, -Z. I've proposed
adding that switch to the Pyhton Eggs guidelines:
https://fedorahosted.org/fpc/ticket/378
If you get similar bug reports to the one menitoned, you can add the switch
to workaround the problem now. I'll send a new message to this list if (for
some reason I don't know about) adding -Z is deemed unacceptable.
-Toshio
9 years, 5 months
