Thanks for your interest in Pypes! I am able to reproduce the submit
button bug, however, the FastXML Publisher works without any issue.
Can you answer a few questions for us:
What platform are you using?
What browser?
What version of Pypes?
What version of Stackless?
I just setup a fresh installation of Pypes 1.1, MacOS 10.6.4,
Stackless Python 2.6.4, using Google Chrome:
1. Download pypes from http://bitbucket.org/diji/pypes/get/v1.1.tar.gz
2. tar -xvzf pypes-v1.1.tar.gz
3. cd pypes
4. python bootstrap.py # make sure you are using your stackless
interpreter here
5. ./bin/buildout
6. ./bin/paster make-config pypesvds production.ini
7. ./bin/paster setup-app production.ini
8. ./bin/paster serve production.ini
Once Pypes was running I created a simple Pipeline using the CSV
Adapter and the FAST Xml Publisher and clicked Save.
Then I opened a new terminal window (assume $PYPES is the location you
extracted and installed pypes)
1. cd $PYPES
2. mkdir tmp
3. echo "1,2,3,4,5,6" > tmp/test.csv # just create a basic csv file
here is not using unix
4. ./bin/FileCrawler.py -e csv tmp/
Thats it, assuming you used the default output directory, there should
be a folder called $PYPES/fastxml and a single file in it that looks
similar to:
<?xml version="1.0" encoding="utf-8"?>
<documents>
<document>
<element name="column1">
<value><![CDATA[1]]></value>
</element>
<element name="column2">
<value><![CDATA[2]]></value>
</element>
<element name="column3">
<value><![CDATA[3]]></value>
</element>
<element name="column4">
<value><![CDATA[4]]></value>
</element>
<element name="column5">
<value><![CDATA[5]]></value>
</element>
<element name="column6">
<value><![CDATA[6]]></value>
</element>
</document>
</documents>
I will open a bug report and look into the Submit button issue.
Thanks,
Matt Weber
I have a few questions: I've downloaded and run Pypes as the Wiki
suggested:
1. The 'Submit' button doesn't pop up a dialog as the Help suggests -
is this expected?
2. The FASTXML component creates an output folder, but creates no data
- I had a very simple project where the data was split to a Debug
component, which was showing output to the console, so I know there
was data moving through the system.
--
Thanks,
Matt Weber
--
Thanks,
Matt Weber
Hi Matt,
>
> Thanks for your interest in Pypes! I am able to reproduce the submit
> button bug, however, the FastXML Publisher works without any issue.
> Can you answer a few questions for us:
>
> What platform are you using?
Windows XP
> What browser?
Firefox 3.6.8
> What version of Pypes?
v1.1
> What version of Stackless?
2.7, the .msi from the Stackless website. I've just realised Pypes'
INSTALL.txt specifies 2.6.2 .... I can retry with that if you like.
>
> I just setup a fresh installation of Pypes 1.1, MacOS 10.6.4,
> Stackless Python 2.6.4, using Google Chrome:
>
> 1. Download pypes from http://bitbucket.org/diji/pypes/get/v1.1.tar.gz
> 2. tar -xvzf pypes-v1.1.tar.gz
> 3. cd pypes
> 4. python bootstrap.py # make sure you are using your stackless
> interpreter here
> 5. ./bin/buildout
> 6. ./bin/paster make-config pypesvds production.ini
> 7. ./bin/paster setup-app production.ini
> 8. ./bin/paster serve production.ini
>
> Once Pypes was running I created a simple Pipeline using the CSV
> Adapter and the FAST Xml Publisher and clicked Save.
I did something very similar on Windows. I then used FileCrawler.py to
submit some files - splitting the output to the Debug component, which
showed some files making it through the process. The fastxml folder was
created, but no files appeared.
Cheers
Charlie
--
Charlie Hull
Flax - Open Source Enterprise Search
tel/fax: +44 (0)8700 118334
mobile: +44 (0)7767 825828
web: www.flax.co.uk
I have created a bug report for this issue:
http://bitbucket.org/diji/pypes/issue/2/fastxml-publisher-does-not-work-on-windows.
I will get Pypes setup on Windows to see if I can figure out what is
going on. Python 2.7 vs. 2.6 should not be an issue, but I will try
with both versions and get back to you.
--
Thanks,
Matt Weber
--
Thanks,
Matt Weber
Verified here - great! I'll have a think about how we might get further
involved.
Best
Charlie
>
> -Eric
>
>
> On Tue, Sep 7, 2010 at 12:27 AM, Matt Weber <ma...@mattweber.org
> <mailto:ma...@mattweber.org>> wrote:
>
> Charlie,
>
> I have created a bug report for this issue:
> http://bitbucket.org/diji/pypes/issue/2/fastxml-publisher-does-not-work-on-windows.
> I will get Pypes setup on Windows to see if I can figure out what is
> going on. Python 2.7 vs. 2.6 should not be an issue, but I will try
> with both versions and get back to you.
>
>
> --
> Thanks,
> Matt Weber
>
> :58 AM, Charlie Hull <cha...@flax.co.uk
> >>> (www.flax.co.uk <http://www.flax.co.uk>) - we work with open
> > web: www.flax.co.uk <http://www.flax.co.uk>
> >
>
>
>
> --
> Thanks,
> Matt Weber
On 10/09/2010 04:19, Eric Gaumer wrote:Verified here - great! I'll have a think about how we might get further involved.
Matt just pushed a fix for this in tip.
http://bitbucket.org/diji/pypes/changeset/7c24ef1a60b7
<http://bitbucket.org/diji/pypes/changeset/7c24ef1a60b7>The change is
minor so you might want to just patch manually.
> I looked at Flax a few years ago when I was researching Xapian and even
> then, it seemed like an exciting project. I'd like to catch up at the
> conference in Boston and talk more about Flax.
Yes, looking forward to that myself.
>
> We have a number of clients but we don't typically promote any specific
> search technology. Instead, we try to match the clients needs to the
> best solution so we can reduce the friction and achieve our goals.
We're actually of the same mind - although we've developed the Flax
layer on top of Xapian, we've also worked with Lucene, Ultraseek and
many others over the years. Whatever solves the client's problem.
>
> It certainly would be interesting to add Flax to that list of choices.
> Aside from pypes, which seems like it could fit very well into Flax, we
> also do a lot of work involving NLP via the NLTK (now under an Apache
> 2.0 license). Marrying some of these features together would a
> worthwhile effort.
>
Yes indeed!
> I'm already looking into writing a Flax publishing component for pypes
> by leveraging Xappy. This would allow us to, for instance, map existing
> FastXML into Flax or submit other formats for indexing. As Xappy is
> Python, it almost seems like a marriage made in heaven.
Actually, I'm going to suggest avoiding Xappy and looking at flax.core :
it's a simpler layer for a start. We've blogged about this recently at
http://www.flax.co.uk/blog/ and also about flax.crawler, which might be
something else we can look at.
Let me know what you think!
Cheers
Charlie
>
> Very exciting stuff and I look forward to meeting in Boston.
>
> -Eric
>
Actually, I'm going to suggest avoiding Xappy and looking at flax.core : it's a simpler layer for a start. We've blogged about this recently at
I'm already looking into writing a Flax publishing component for pypes
by leveraging Xappy. This would allow us to, for instance, map existing
FastXML into Flax or submit other formats for indexing. As Xappy is
Python, it almost seems like a marriage made in heaven.
http://www.flax.co.uk/blog/ and also about flax.crawler, which might be something else we can look at.
Let me know what you think!
> Great.
>
> I looked at Flax a few years ago when I was researching Xapian and even
> then, it seemed like an exciting project. I'd like to catch up at the
> conference in Boston and talk more about Flax.
Hi Eric,
I'm arriving on Tuesday night and will be around for Wednesday-Friday.
Currently I'm booked for 1-5pm on Wednesday and 10-11 on Friday, and
will be attending conference sessions - although I doubt I'll go to
everything! Is it worth arranging a time to meet or shall we just swap
contact details?