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

Shall we move beautifulsoup out of the codebase #51

Open
mattions opened this issue Jul 11, 2012 · 1 comment
Open

Shall we move beautifulsoup out of the codebase #51

mattions opened this issue Jul 11, 2012 · 1 comment
Assignees

Comments

@mattions
Copy link
Owner

We now use BeautifulSoup3.2, bundled with Neuronvisio source code.

Given the fact it's on pipy http://pypi.python.org/pypi/BeautifulSoup/3.2.1, I was thinking that we may can extract it from the source code and introduce it as a package dependencies in the pavement.py.

At the same time we could move from the series 3.x to 4.x.

Hey @uricohen, What you think?

@uricohen
Copy link
Collaborator

Hey Michele, yes, I can give it a try. I'll try to do it early next week:

The docs make it sound easy.
Uri

On Wed, Jul 11, 2012 at 2:06 PM, Michele Mattioni <
[email protected]

wrote:

We now use BeautifulSoup3.2, bundled with Neuronvisio source code.

Given the fact it's on pipy
http://pypi.python.org/pypi/BeautifulSoup/3.2.1, I was thinking that we
may can extract it from the source code and introduce it as a package
dependencies in the pavement.py.

At the same time we could move from the series 3.x to 4.x.

Hey @uricohen, What you think?


Reply to this email directly or view it on GitHub:
#51

        Uri Cohen

@ghost ghost assigned uricohen Jul 12, 2012
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