Bug 453334

Summary:	virtual/pmw (was: dev-python/pmw-2.0.0 Version Bump)
Product:	Gentoo Linux	Reporter:	Justin Lecher (RETIRED) <jlec>
Component:	Current packages	Assignee:	Python Gentoo Team <python>
Status:	RESOLVED FIXED
Severity:	normal
Priority:	Normal
Version:	unspecified
Hardware:	All
OS:	Linux
Whiteboard:
Package list:		Runtime testing required:	---
Bug Depends on:	453568, 453570, 453572, 453574
Bug Blocks:

Description Justin Lecher (RETIRED) gentoo-dev

2013-01-21 13:54:54 UTC

Situation is as following:

version 1.* purely py2
version 2.* purely py3

I added pmw-2.0.0 without keywords. What should we dohere? Move to different slotts?

Comment 1 Michał Górny archtester

2013-01-21 14:05:21 UTC

It's a case similar to pyparsing. Are the two versions API-compatible?

In any case, slotting is probably the way to go. If the versions are compatible, introducing a virtual is also a good idea.

Comment 2 Justin Lecher (RETIRED) gentoo-dev

2013-01-22 19:33:45 UTC

I adopted the virtual from pyparsing. All packages in the tree depend fixed on pmw:0 now, until they are moved to the new python eclasses.

Comment 3 Michał Górny archtester

2013-01-22 21:08:15 UTC

(In reply to comment #2)
> I adopted the virtual from pyparsing. All packages in the tree depend fixed
> on pmw:0 now, until they are moved to the new python eclasses.

Well, you can always dep on the virtual. If new eclasses aren't used, most users will still get what is necessary due to PYTHON_TARGETS being the same for all packages.