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

Developer usability concerns #414

Closed
drdavella opened this issue Dec 15, 2017 · 3 comments
Closed

Developer usability concerns #414

drdavella opened this issue Dec 15, 2017 · 3 comments
Assignees

Comments

@drdavella
Copy link
Contributor

There are a few issues that bite new developers (and, speaking from experience, even some more experienced ones) when trying to get started with ASDF and building from source:

  • making sure the asdf-standard submodule is initialized and up-to-date
  • the fact that it is not possible to import and use asdf from the source directory

It would be nice to address these issues somehow so that new developers are not put off by the project.

@drdavella drdavella self-assigned this Dec 15, 2017
@Cadair
Copy link
Contributor

Cadair commented Dec 18, 2017

What get's me is the fact that doing pip install -e . doesn't work, i.e. even trival changes to the python source are not reflected in the imported version. This is probably the same as being able to import it from the source directory.

@drdavella
Copy link
Contributor Author

@Cadair this should be fixed on the latest master. The problem appears to have been the use of use_2to3 in setup.py, which was removed in #409.

@drdavella
Copy link
Contributor Author

Closing since the major issues here have been addressed. A solution for making sure asdf-standard is always up to date exists in #419, but I am hesitant to merge this due to potential security issues.

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

No branches or pull requests

2 participants