Thank you for trying the package and reporting the bug.
Could you please provide more information. Specifically,
1) File name you are referring to,
2) Platform you are working (eg. Linux, Windows), and
version of Python
3) The code that revelaed this bug, so that I can replicate
it in my system.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
The file referred to is APLEpy/LP.py. I haven't run the
software since I don't have XpressMP, but was very
interested in the project and will likely look at hooking to
another solver. lp_solve recently added a Python driver
which would make pyrex unnecessary. I found what I believe
to be a bug by simply reading the source code.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Thanks for the follow up. I did not implement the
functionality behind the 'fixed' keyword yet. I will check
your solution when I have a chance to continue development.
Currently, I am in research mode, planning and plotting some
novel language extensions.
However, my priority in development is to hook APLEpy up to
as many solvers as I can, particularly open source ones. I
was mentioned that the OSI library, hosted at coin-or, may
provide a single interface to all the known solvers. I will
check it during the holidays.
If you are an academic user, I can provide you, temporarily,
an XpressMP license under Linux. Let me know.
Also I was wondering if you had a chance to compile APLEpy
on Windows. I did not try it yet and I was wondering if it
would be easy.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
var.init mishandles fixed keyword --> var.init mishandles fixed keyword
Logged In: YES
user_id=958127
Thank you for trying the package and reporting the bug.
Could you please provide more information. Specifically,
1) File name you are referring to,
2) Platform you are working (eg. Linux, Windows), and
version of Python
3) The code that revelaed this bug, so that I can replicate
it in my system.
Logged In: YES
user_id=551623
The file referred to is APLEpy/LP.py. I haven't run the
software since I don't have XpressMP, but was very
interested in the project and will likely look at hooking to
another solver. lp_solve recently added a Python driver
which would make pyrex unnecessary. I found what I believe
to be a bug by simply reading the source code.
Logged In: YES
user_id=958127
Thanks for the follow up. I did not implement the
functionality behind the 'fixed' keyword yet. I will check
your solution when I have a chance to continue development.
Currently, I am in research mode, planning and plotting some
novel language extensions.
However, my priority in development is to hook APLEpy up to
as many solvers as I can, particularly open source ones. I
was mentioned that the OSI library, hosted at coin-or, may
provide a single interface to all the known solvers. I will
check it during the holidays.
If you are an academic user, I can provide you, temporarily,
an XpressMP license under Linux. Let me know.
Also I was wondering if you had a chance to compile APLEpy
on Windows. I did not try it yet and I was wondering if it
would be easy.