-
Notifications
You must be signed in to change notification settings - Fork 15
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
Hypermodern Python Package #25
Comments
Hi @pauleveritt thank you so much for all the work you put up on this to build the vision! tech infrastructure: Regarding the blue/black discussion on #22, currently PyScript is using black and we intend to tweak it to make it look "nicer". I'm of the personal opinion of using a smaller number o tools across sister projects. We can maybe decide what to do here and copy our results to the main repo. Another question in this topic is regarding nox, I've never used it before. Do we need it? I'm asking because I can't think of an user case for it. For CI maybe...? Thanks!
I understand this point but I have some concerns. I wonder if a divergence here will cause problems regarding maintenance, basically if it will make it harder for us to maintain both things, e.g. if I have a package that exists only in the conda ecosystem then that's a problem for the poetry users (think about the extended ecosys. too, like conda-forge, my goal is not to dogfood conda necessarily[1]), besides that we can have divergent errors between the package's versions of poetry vs. conda. Maybe the question is should we shift everything to poetry? Bearing in mind if it's the best/most used solution to our users, specially the beginners. hosting infrastructure: Another question I have is regarding licensing and actual place where this repository is going to live. Is the idea to be something parellel to
That’s pretty long, though. Perhaps PyScript should adopt ps- as the prefix? ::: IMO that's good. code of conduct: You think it's a bad thing to have people pointed to the [1] we actually currently have an example like this where we're trying to use a package that's not available open source (it's owned by Microsoft) and I'm looking into making it open source by using conda-forge Once again, I hope my points are not discouraging, I'm really excited about the progress and what I meant with them was to have a back and forth and understand your point and this whole hyperdrive thing that's new to me. |
Thanks @marimeireles for taking the time to do a detailed analysis. I also talked with Fabio this week on some of these topics. I'll break things out.
All good points, thanks! |
Excellent conversation! 👍 Just my addendum on a couple of points. In general, the more we can reused things from PyScript core repo for the collective and vice-versa, unless it becames "a stretch and unnatural"
We use conda on the main repo mostly out of force of habit on my side, not because it's an Anaconda thing or because it's needed. I also don't think we should give too much thought to "Conda is more intentional: it’s less used per the PSF survey, and we want to show that PyScript isn’t tied to Anaconda no Conda." That's not what makes PyScript tied to Anaconda. The fact that PyScript was created inside Anaconda and the initial core team was (is) mostly Anaconda employees is a much stronger tie to Anaconda that, with time and adoption, we will hopefully change. This is not new to Anaconda (Bokeh, Dask, and many other projects were born at Anaconda but are OSS projects governed by people and organizations not affiliated to Anaconda). The way we change this is by adding more diverse core developers/steering council members and through the governance model (not a tool). With that said, pyscript-cli, the
fwiw,
Yes! Lots of potential here...
+1 (with the caveat that I mentioned above) |
Note: We've approved the work on the prototype. We're going to re-do it over here, on a branch, using "Diary Driven Development.
In this step, we'll make a new branch and bring over the work described in the first step of the prototype. Namely:
The text was updated successfully, but these errors were encountered: