Re: [Numpy-discussion] A numpy based Entity-Component-System

2016-05-23 Thread Benjamin Root
As a bit of a real-life example where things can go wrong with naming. The "pylab" name was accidentally hijacked a couple years ago on pypi, and caused several bug reports to be filed against matplotlib for failing scripts. Some people thought that one should do "pip install pylab" to do "from

Re: [Numpy-discussion] A numpy based Entity-Component-System

2016-05-20 Thread Nathaniel Smith
On May 20, 2016 4:24 PM, "Elliot Hallmark" wrote: > > I have a Data Oriented programing library I'm writing that uses the Entity-Component-System model. > > https://github.com/Permafacture/data-oriented-pyglet > > I have initially called it Numpy-ECS but I don't know if

[Numpy-discussion] A numpy based Entity-Component-System

2016-05-20 Thread Elliot Hallmark
I have a Data Oriented programing library I'm writing that uses the Entity-Component-System model. https://github.com/Permafacture/data-oriented-pyglet I have initially called it Numpy-ECS but I don't know if that name is okay. The numpy license says: Neither the name of the NumPy Developers