#11549: Review dependencies on Python 2
-----------------------------+------------------------
Reporter: pierre.labastie | Owner: blfs-book
Type: enhancement | Status: new
Priority: normal | Milestone: x-future
Component: BOOK | Version: SVN
Severity: normal | Resolution:
Keywords: Python 2 |
-----------------------------+------------------------
Comment (by pierre.labastie):
Well, let's discuss some sort of policy (I do not have the whole picture
yet, so may need adjustments later). From Douglas and Bruce inputs, I'd
say it could be:
- Python modules: always build for P3, except when impossible (pygtk).
Build for P2 only when really needed by something in the book (normally,
already implemented).
- Other applications:
- Python bindings: don't prevent building bindings for P3 (but do not
build them if upstream default is to not build them), and always prevent
building them for P2, unless the package itself or a dependent package
require P2.
- Python apps: build only for P3 as much as possible. Build for P2 only
when upstream ~~is too lazy~~ has been too busy to take the time to switch
to P3.
--
Ticket URL: <http://wiki.linuxfromscratch.org/blfs/ticket/11549#comment:14>
BLFS Trac <http://wiki.linuxfromscratch.org/blfs>
Beyond Linux From Scratch
--
http://lists.linuxfromscratch.org/listinfo/blfs-book
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
