Skip to content
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

Updating python #485

Open
kusabana opened this issue Jul 3, 2023 · 3 comments
Open

Updating python #485

kusabana opened this issue Jul 3, 2023 · 3 comments

Comments

@kusabana
Copy link

kusabana commented Jul 3, 2023

I realize this might have been a better fit for the forum, but I'm unable to register as i get flagged as a spammer.

I've been maintaining a private fork where I've been working on updating various aspects of Source.Python for my own server because i was under the impression that this was somewhat dead, but I've now realized that it's still being maintained so there was no need.

Are there currently any plans to update python and other dependencies to their latest versions? Is there anything holding the project back from being updated or is it just a lot of work no one has been willing to do?

@jordanbriere
Copy link
Contributor

Is there anything holding the project back from being updated or is it just a lot of work no one has been willing to do?

Pretty much the later on my side. In addition to backward compatibility concerns with existing UGC (which has been the utmost priority for quite a while now). Without mentioning all the potential conflicts with many host providers that still run prehistoric architectures, etc. I'm not sure about others but, personally, the occasional bug fixes/optimizations is the only effort I'm still willing to devote to this project.

That said, it's probably not even something we would accept PR for, considering the sensitive nature of merging pre-compiled binaries. That is, unless the risks can be mitigated by using builds from official/trusted sources, I guess.

@kusabana
Copy link
Author

kusabana commented Jul 4, 2023

That said, it's probably not even something we would accept PR for, considering the sensitive nature of merging pre-compiled binaries. That is, unless the risks can be mitigated by using builds from official/trusted sources, I guess.

Could this not be solved by compiling it as part of the build process, instead of using pre-compiled binaries?

@Ayuto
Copy link
Member

Ayuto commented Jul 5, 2023

Is there anything holding the project back from being updated or is it just a lot of work no one has been willing to do?

Pretty much the later on my side. In addition to backward compatibility concerns with existing UGC (which has been the utmost priority for quite a while now).

Same for me. I actually started two attempts, but never had the time to finish as I ran into problems due to changes in the required GCC/MSVC versions.

Also, my time, interest and motivation for this project is not as high as it was a few years ago when I spend many hours every week on this project.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants