[openstack-dev] [tap-as-a-service] publish on pypi

[Takashi Yamamoto]

hi,

i'm thinking about publishing the latest release of tap-as-a-service on pypi.
background: https://review.openstack.org/#/c/555788/
iirc, the naming (tap-as-a-service vs neutron-taas) was one of concerns
when we talked about this topic last time. (long time ago. my memory is dim.)
do you have any ideas or suggestions?
probably i'll just use "tap-as-a-service" unless anyone has strong opinions.
because:
- it's the name we use the most frequently
- we are not neutron (yet?)

__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: OpenStack-dev-***@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listi

[Clark Boylan]

Post by Takashi Yamamoto
hi,
i'm thinking about publishing the latest release of tap-as-a-service on pypi.
background: https://review.openstack.org/#/c/555788/
iirc, the naming (tap-as-a-service vs neutron-taas) was one of concerns
when we talked about this topic last time. (long time ago. my memory is dim.)
do you have any ideas or suggestions?
probably i'll just use "tap-as-a-service" unless anyone has strong opinions.
- it's the name we use the most frequently
- we are not neutron (yet?)

http://git.openstack.org/cgit/openstack/tap-as-a-service/tree/setup.cfg#n2 shows that tap-as-a-service is the existing package name so probably a good one to go with as anyone that already has it installed from source should have pip do the right thing when talking to pypi.

Clark

__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: OpenStack-dev-***@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/

[Takashi Yamamoto]

thank you. done. https://pypi.org/project/tap-as-a-service/

Post by Clark Boylan

Post by Takashi Yamamoto
hi,
i'm thinking about publishing the latest release of tap-as-a-service on pypi.
background: https://review.openstack.org/#/c/555788/
iirc, the naming (tap-as-a-service vs neutron-taas) was one of concerns
when we talked about this topic last time. (long time ago. my memory is dim.)
do you have any ideas or suggestions?
probably i'll just use "tap-as-a-service" unless anyone has strong opinions.
- it's the name we use the most frequently
- we are not neutron (yet?)

http://git.openstack.org/cgit/openstack/tap-as-a-service/tree/setup.cfg#n2 shows that tap-as-a-service is the existing package name so probably a good one to go with as anyone that already has it installed from source should have pip do the right thing when talking to pypi.
Clark
__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: OpenStack-dev-***@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailma