Open Stack

On 11/17/2014 06:43 AM, Yves-Gwenaël Bourhis wrote:
> Le 17/11/2014 14:19, Matthias Runge a écrit :
>
>> There is already horizon on pypi[1]
>>
>> IMHO this will lead only to more confusion.
>>
>> Matthias
>>
>>
>> [1] https://pypi.python.org/pypi/horizon/2012.2
>
> Well the current "horizon" on Pypi is "The OpenStack Dashboard" +
> horizon(_lib) included
>
> If the future "horizon" on pypi is "openstack_dashboard" alone, it would
> still pull "horizon_lib" as a dependency, so it would not brake the
> existing.
>
> So indeed the "horizon" package itself in Pypi would not have
> horizon(_lib) in it anymore, but he "pip install horizon" would pull
> everything due to the dependency horizon will have with horizon_lib.
>
> I find this the least confusing issue and the "horizon" package on Pypi
> would still be seen as "The OpenStack Dashboard" like it is now. We
> would only add an "horizon_lib" package on Pypi.
> Therefore existing third-party "requirements.txt" would not brake
> because they would pull horizon_lib with horizon. and they would still
> import the proper module. Every backwards compatibility (requirements
> and module) is therefore preserved.
>

+1 on this proposal as well

On Mon, Nov 17, 2014 at 6:00 PM, Jason Rist <jrist at redhat.com> wrote:

> On 11/17/2014 06:43 AM, Yves-Gwenaël Bourhis wrote:
> > Le 17/11/2014 14:19, Matthias Runge a écrit :
> >
> >> There is already horizon on pypi[1]
> >>
> >> IMHO this will lead only to more confusion.
> >>
> >> Matthias
> >>
> >>
> >> [1] https://pypi.python.org/pypi/horizon/2012.2
> >
> > Well the current "horizon" on Pypi is "The OpenStack Dashboard" +
> > horizon(_lib) included
> >
> > If the future "horizon" on pypi is "openstack_dashboard" alone, it would
> > still pull "horizon_lib" as a dependency, so it would not brake the
> > existing.
> >
> > So indeed the "horizon" package itself in Pypi would not have
> > horizon(_lib) in it anymore, but he "pip install horizon" would pull
> > everything due to the dependency horizon will have with horizon_lib.
> >
> > I find this the least confusing issue and the "horizon" package on Pypi
> > would still be seen as "The OpenStack Dashboard" like it is now. We
> > would only add an "horizon_lib" package on Pypi.
> > Therefore existing third-party "requirements.txt" would not brake
> > because they would pull horizon_lib with horizon. and they would still
> > import the proper module. Every backwards compatibility (requirements
> > and module) is therefore preserved.
> >
> >
>
> +1 to this solution
>
> --
> Jason E. Rist
> Senior Software Engineer
> OpenStack Management UI
> Red Hat, Inc.
> openuc: +1.972.707.6408
> mobile: +1.720.256.3933
> Freenode: jrist
> github/identi.ca: knowncitizen
>
> _______________________________________________
> OpenStack-dev mailing list
> OpenStack-dev at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20141117/c56356b3/attachment.html>