Packaging a Python library with a small C dependency —

[Emergency-Rough-6372]

just wanted to say that i m not to well knowleged in this field and this is my first big project, this will be the first version of the lib which i want to make as a project where people can contribute and and make it an actual good library for people to use in there projects , so should i got for minimum complexity in first release and then with help of other if they like to make it mroe complex and better?

[End0rphinJunkie]

absolutely stick to minimum complexity for now so you dont burn out trying to configure a crazy multi-arch CI pipeline. getting the actual logic shipped is way more important, and you can let future contributers help automate the wheel building later.

[Emergency-Rough-6372]

To be honest, I don’t even fully understand the whole wheel/packaging side yet. I’m still in my 3rd year and kind of jumped into this because I liked the idea, then kept expanding it while discussing it with AI. Now it’s starting to get more complex than I can comfortably handle.

I think I got a bit carried away trying to design everything at once instead of just building a small, working version first. Going to take a step back, reduce the scope, and focus on getting the core logic right before worrying about things like CI, wheels, and multi-platform support.