Shall we move beautifulsoup out of the codebase

[mattions]

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]

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

• move to use BeautifulSoup from pypi (add dependency, etc.)
• move to use BeautifulSoup4 by changing the needed names ( http://www.crummy.com/software/BeautifulSoup/bs4/doc/#porting-code-to-bs4)

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: https://github.com/mattions/neuronvisio/issues/51

        Uri Cohen