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.

Sign up for GitHub

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

Jump to bottom

pymoses.so -> pyasmoses.so? #59

Closed
mhatta opened this issue Aug 23, 2019 · 2 comments
Closed

pymoses.so -> pyasmoses.so? #59

mhatta opened this issue Aug 23, 2019 · 2 comments

Comments

@mhatta
Copy link
Contributor

mhatta commented Aug 23, 2019

I'm packaging asmoses for Debian. It looks moses and asmoses basically can co-exist (things are renamed with prefix "as" in asmoses), but pymoses is still pymoses, not pyasmoses. Since 2 Debian packages can't have files of the same name, I have to set Conflicts: to them. Is it possible to rename pymoses or any reason we can't?
@linas
Copy link
Member

linas commented Aug 24, 2019

there's no reason; you should send a pull request

@mhatta mhatta mentioned this issue Aug 24, 2019
Merged
linas pushed a commit to linas/as-moses that referenced this issue Feb 27, 2020
@ngeiswei
Merge pull request opencog#59 from ngeiswei/minor-comment-fix
639b9e5 
That variation of hill-climbing is stochastic, not exhaustive
@linas
Copy link
Member

linas commented Jul 25, 2022

Closing; There is now a pyasmoses.so and it works for python3 (fixed in pull req #96)

@linas linas closed this as completed Jul 25, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@mhatta @linas