-
Notifications
You must be signed in to change notification settings - Fork 1.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[packaging discussion] Establishing communication with pip maintainers #1932
Comments
👋🏻 I'm a pip maintainer and I'm subscribing to this ticket. Please feel free to ask "how to communicate" or similar questions that I could answer. I'll be happy to answer what I can. |
@pradyunsg thanks so much for dropping by ❤️ I'm done writing a summary of how p4a uses python packaging and I'll link it soon here https://discuss.python.org/t/packaging-and-python-for-android/2036 once I got a quick go-ahead here from the others to do so. I guess it might then make most sense to see in the discourse thread what sort of communication might best work (I assume us knowing how to know where PEPs are drafted and which ones we need to keep an eye on and comment on would be a part of that?) @inclement @AndreMiras @tito any objections if I go ahead and introduce python-for-android and it's way of using pip a little in the python discuss forum? Anyone else who wants to volunteer or have some more concrete input on this? I'll wait for protests here for another few days and if none are voiced I'll go ahead (although I'd prefer an explicit ok if any of you have the time!) so we can hopefully move this ahead |
@Jonast As discussed on discord: please go right ahead. I'll try to keep up with this, but I haven't had much time to follow it recently. |
Given the OP's ghost status, do we need to start this effort again, or has the moment passed and we are all good now? |
Due to an upcoming potential issue with pip's new feature of "build isolation" being likely problematic for python-for-android, we've been asked to establish a communication channel by the pip developers so we can bring in such concerns earlier in the future.
Communication channel ideas:
We are asked to kinda introduce ourselves and how we work here: https://discuss.python.org/t/packaging-and-python-for-android/2036 - we should decide who does that (I would be open for doing so)
We should somewhere share how we roughly use pip, in a way that is useful to someone who knows how pip and python packages work but not how p4a works. I proposed a first document for this here, which could then be shared with interested people: Add a document describing how p4a interacts with pip & python packages #1931
It has been proposed that some of us may want to take a look at future plans in PEPs of pip developers to watch out for potential pitfalls. Again we should decide who does that, I would again be open to do that if it is decided I should do so
In general we should think about if this will be a very involved thing where all of us somehow vote on opinions, or more a basic approach where one of us (e.g. me) just does their best effort to keep the communication going and tries to make sure all relevant things are brought up by using their judgement, and how we all want to be kept in the loop
Edit: open for any other ideas, of course! This list is just what I came up with what might be a nice idea to do, we don't need to stick to any of this, obviously
The text was updated successfully, but these errors were encountered: