Recently many of these setup.py files were deleted so now there is only:

common/setup.py      <------   going away anyway with
https://pulp.plan.io/issues/3066
platform/setup.py
plugins/setup.py

I think it's good to have the folder use the python namespace names. If we
did that it would be renaming 'platform' to 'pulpcore' with `git mv
platform pulpcore`. I made an issue for this here [0] if that is what we
want to do.

[0]: https://pulp.plan.io/issues/3089


On Mon, Jun 19, 2017 at 2:54 PM, Austin Macdonald <aus...@redhat.com> wrote:

> We recently made the decision to namespace Pulp as "pulpcore" [0], but
> this has made our app location a little awkward:
> `pulp/platform/pulpcore/app`
>
> To kick off the conversation, I think the best place to start is a map of
> all of the setup.py files:
>
> bindings/setup.py
> client_admin/setup.py
> client_consumer/setup.py
> client_lib/setup.py
> common/setup.py
> devel/setup.py
> oid_validation/setup.py
> platform/setup.py
> plugins/setup.py
> repoauth/setup.py
> server/setup.py
> streamer/setup.py
>
>
> To me, it makes sense that pulpcore should move up a level, so the app
> would live in `pulp/pulpcore/app` and the setup py would live in
> `pulp/pulpcore/setup.py`
>
>
> [0]: https://www.redhat.com/archives/pulp-dev/2017-May/msg00030.html
>
> _______________________________________________
> Pulp-dev mailing list
> Pulp-dev@redhat.com
> https://www.redhat.com/mailman/listinfo/pulp-dev
>
>
_______________________________________________
Pulp-dev mailing list
Pulp-dev@redhat.com
https://www.redhat.com/mailman/listinfo/pulp-dev

Reply via email to