On Feb 12, 2013, at 12:49 AM, Dmitrijs Ledkovs wrote:
>> Debian HPIJS and HPLIP maintainers
>>hplip
>>
>> Matthias Klose
>>python-reportlab
>>
>Does this mean that hplip & python-reportlab are now have all their
>dependenices ported to python3 and hence can also be ported? \o/
I *think*
On 10 February 2013 16:54, Matthias Klose wrote:
> There are 126 source packages needing updates. The list of packages
> and maintainers is attached below. I'll file bug reports later (user:
> d...@debian.org, tag: pillow).
>
I see that a few packages were identified to work out of the box by
fed
On Feb 11, 2013, at 10:14 PM, Matthias Klose wrote:
>probably, because the egg is called pillow. However introducing the pillow
>name for the fork, which may be not permanent, doesn't sound like a good idea
>(the current packages do provide the pillow names). I'll stick to the
>original names for
Am 11.02.2013 17:16, schrieb Barry Warsaw:
> On Feb 11, 2013, at 05:05 PM, Piotr Ożarowski wrote:
>
>> how about replacing python-imaging with python-pil in all packages that
>> do not need compat code (anymore) - this way all packages that are still
>> "broken" will have python-imaging as a depen
On Monday, February 11, 2013 05:05:23 PM Piotr Ożarowski wrote:
> [Barry Warsaw, 2013-02-11]
>
> > On Feb 11, 2013, at 03:51 PM, Piotr Ożarowski wrote:
> > >I'd also use python-pil and let python-imaging contain the compat code
> > >(with Depends: python-pil)
> >
> > Do you mean, get rid of the -
* Barry Warsaw , 2013-02-11, 10:53:
On Feb 11, 2013, at 03:51 PM, Piotr Ożarowski wrote:
[...]
I'd also use python-pil and let python-imaging contain the compat code
(with Depends: python-pil)
+1
Do you mean, get rid of the -compat package? I'd rather keep that as
an explicit dependency so
On Feb 11, 2013, at 05:05 PM, Piotr Ożarowski wrote:
>how about replacing python-imaging with python-pil in all packages that
>do not need compat code (anymore) - this way all packages that are still
>"broken" will have python-imaging as a dependency
+1
One minor question, should it be python{,3
[Barry Warsaw, 2013-02-11]
> On Feb 11, 2013, at 03:51 PM, Piotr Ożarowski wrote:
> >I'd also use python-pil and let python-imaging contain the compat code
> >(with Depends: python-pil)
>
> Do you mean, get rid of the -compat package?
yes
> I'd rather keep that as an
> explicit dependency so we
On Feb 10, 2013, at 06:14 PM, Jakub Wilk wrote:
>* Matthias Klose , 2013-02-10, 17:54:
>>Fixes should be easy and made in a way that works with both the old PIL
>>>modules and the new Pillow egg/package:
>>
>> import Image
>>
>>should become
>>
>> try:
>>from PIL import Image
>> except Imp
On Feb 11, 2013, at 03:51 PM, Piotr Ożarowski wrote:
>[Jakub Wilk, 2013-02-11]
>> Great, so it's not too late to rename them to comply with Python
>> Policy §2.2:
>>
>> python3-imaging -> python3-pil
>> python3-imaging-tk -> python3-pil.imagetk
>> python3-imaging-sane -> python3-sane
>
>+1
>
>I'd
[Jakub Wilk, 2013-02-11]
> Great, so it's not too late to rename them to comply with Python
> Policy §2.2:
>
> python3-imaging -> python3-pil
> python3-imaging-tk -> python3-pil.imagetk
> python3-imaging-sane -> python3-sane
+1
I'd also use python-pil and let python-imaging contain the compat co
* Matthias Klose , 2013-02-10, 17:54:
Packages were uploaded to experimental, currently waiting in NEW.
Great, so it's not too late to rename them to comply with Python Policy
§2.2:
python3-imaging -> python3-pil
python3-imaging-tk -> python3-pil.imagetk
python3-imaging-sane -> python3-sane
* Matthias Klose , 2013-02-10, 17:54:
Fixes should be easy and made in a way that works with both the old PIL
modules and the new Pillow egg/package:
import Image
should become
try:
from PIL import Image
except ImportError:
import Image
Why is the "import Image" fallback necessary?
13 matches
Mail list logo
