-
-
Notifications
You must be signed in to change notification settings - Fork 362
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
Generate setup.py file #896
Conversation
Codecov Report
@@ Coverage Diff @@
## master #896 +/- ##
==========================================
Coverage 100.00% 100.00%
==========================================
Files 20 33 +13
Lines 717 864 +147
==========================================
+ Hits 717 864 +147
Continue to review full report at Codecov.
|
Hi @mekanix! Thank you for this proposal! I may not have all the ins and outs about this but, from what I understood, it sounded like I wouldn't mind add this option if it's really needed on some systems, but if you could give me some insights about the status of |
Thank you for this proposal! I may not have all the ins and outs about this but, from what I understood, it sounded like `setup.py` was more or less deprecated. There is a long thread about this on Flit: pypa/flit#501
Well, it's like Python 2. It is dead, now just the rest of the ecosystem
needs to accept that. What I'm trying to say is that build systems in
operating systems are slow(er) to adopt new technologies.
I wouldn't mind add this option if it's really needed on some systems, but if you could give me some insights about the status of `setup.py` in the Python world, it would be really helpful :)
I can't speak on behalf of any community, but I will sure make an effort
to upgrade Python integration in FreeBSD. Naturally, I have two things
to do:
1) research flit and similar build tools more
2) talk to FreeBSD Python team about the best way to go forward.
Until then either this PR is needed or I should generate setup.py every
time I update port. What do you think is better?
|
Well, I would say it doesn't harm to add this option if it helps developers out there. I was being curious about the status of |
@all-contributors add @mekanix for platform |
I've put up a pull request to add @mekanix! 🎉 |
@mekanix Was your account compromised? 😓 |
I guess it was. I changed the password so let's see what happens now. |
As Python integration with FreeBSD ports is based on setup.py it would be so much easier to maintain it if that file was generated and uploaded. I am sure that FreeBSD is not the only OS that has this limitation, so potentially this will make porting easier for other operating systems, too.