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

Update enet to version 1.3.13.2 #2609

Open
LinuxDonald opened this Issue Jan 29, 2017 · 11 comments

Comments

Projects
None yet
3 participants
@LinuxDonald
Member

LinuxDonald commented Jan 29, 2017

Our last enet version is 1.3.3 e011d0f

Newest version is: pyenet 1.3.13.2

https://pypi.python.org/pypi/pyenet

@squiddy squiddy added the A-internals label Jan 29, 2017

@LinuxDonald

This comment has been minimized.

Show comment
Hide comment
@LinuxDonald
Member

LinuxDonald commented Feb 1, 2017

@squiddy

This comment has been minimized.

Show comment
Hide comment
@squiddy

squiddy Feb 25, 2017

Member

Weird, it seems pyenet on pypi is gone. It consistently returns 404 for me, and the search for pyenet only returns a match for pygnetic.

Member

squiddy commented Feb 25, 2017

Weird, it seems pyenet on pypi is gone. It consistently returns 404 for me, and the search for pyenet only returns a match for pygnetic.

@LinuxDonald

This comment has been minimized.

Show comment
Hide comment
@LinuxDonald

LinuxDonald Feb 26, 2017

Member

Here is the git version of it: https://github.com/aresch/pyenet

Fife will add enet in the future.
fifengine/fifengine#994

Member

LinuxDonald commented Feb 26, 2017

Here is the git version of it: https://github.com/aresch/pyenet

Fife will add enet in the future.
fifengine/fifengine#994

@squiddy

This comment has been minimized.

Show comment
Hide comment
@squiddy

squiddy Feb 26, 2017

Member

Obviously FIFE is free to do what they want with their time, but I don't think we would gain much, would we? It's probably just another abstraction, right now it's merely Python Wrapper -> enet, then Python Wrapper -> FIFE -> enet.

Member

squiddy commented Feb 26, 2017

Obviously FIFE is free to do what they want with their time, but I don't think we would gain much, would we? It's probably just another abstraction, right now it's merely Python Wrapper -> enet, then Python Wrapper -> FIFE -> enet.

@LinuxDonald

This comment has been minimized.

Show comment
Hide comment
@LinuxDonald

LinuxDonald Feb 26, 2017

Member

yeah maybe that it is. But fife itself needs network lib too. Not for us. We have it already.
But broken.... (Out-of-sync)

Member

LinuxDonald commented Feb 26, 2017

yeah maybe that it is. But fife itself needs network lib too. Not for us. We have it already.
But broken.... (Out-of-sync)

@LinuxDonald LinuxDonald modified the milestones: 2017.3, Multiplayer Apr 23, 2017

@squiddy

This comment has been minimized.

Show comment
Hide comment
@squiddy

squiddy Jun 13, 2017

Member

What needs to be done here? Merely building new versions of pyenet that we ship with the game?

Member

squiddy commented Jun 13, 2017

What needs to be done here? Merely building new versions of pyenet that we ship with the game?

@LinuxDonald

This comment has been minimized.

Show comment
Hide comment
@LinuxDonald

LinuxDonald Jun 13, 2017

Member

Need version of pyenet still for Windows for all supported python3 versions. For Linux an python3 3.5 Build? On freebsd we need to builds. Or we must talk with the maintainer that they create an python3 package.

Member

LinuxDonald commented Jun 13, 2017

Need version of pyenet still for Windows for all supported python3 versions. For Linux an python3 3.5 Build? On freebsd we need to builds. Or we must talk with the maintainer that they create an python3 package.

@LinuxDonald

This comment has been minimized.

Show comment
Hide comment
@LinuxDonald

LinuxDonald Jun 17, 2017

Member

We need now python3-enet rebuild for python3 3.5. Debian 9 is out now an we should switch to min python 3.5 Support now?

Member

LinuxDonald commented Jun 17, 2017

We need now python3-enet rebuild for python3 3.5. Debian 9 is out now an we should switch to min python 3.5 Support now?

@MasterofJOKers

This comment has been minimized.

Show comment
Hide comment
@MasterofJOKers

MasterofJOKers Jun 17, 2017

Contributor

Why do we need 3.5 packages? As long as we're using 3.4 on travis, we don't have to rebuild packages. Once we only want to support 3.5, that rebuild can be done, I guess. But we should probably change to docker on travis first, as I would have to replicate the python3.5 environment available on travis to build a 3.5 package for travis, which sounds like too much effort really.

Contributor

MasterofJOKers commented Jun 17, 2017

Why do we need 3.5 packages? As long as we're using 3.4 on travis, we don't have to rebuild packages. Once we only want to support 3.5, that rebuild can be done, I guess. But we should probably change to docker on travis first, as I would have to replicate the python3.5 environment available on travis to build a 3.5 package for travis, which sounds like too much effort really.

@LinuxDonald

This comment has been minimized.

Show comment
Hide comment
@LinuxDonald

LinuxDonald Jun 17, 2017

Member

My plan is to change travis to python3 3.5
Maybe we should upload the enet and python3-enet to opensuse build service and build there the packages?

Member

LinuxDonald commented Jun 17, 2017

My plan is to change travis to python3 3.5
Maybe we should upload the enet and python3-enet to opensuse build service and build there the packages?

@LinuxDonald

This comment has been minimized.

Show comment
Hide comment
@LinuxDonald

LinuxDonald Jun 17, 2017

Member

When it takes to much time to rebuild it. It can wait.

Member

LinuxDonald commented Jun 17, 2017

When it takes to much time to rebuild it. It can wait.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment