matplotlib-devel Mailing List for matplotlib

 
Has anyone worked with quotes_historical_yahoo module enough to know if the
7th attribute, adjusted price, is available? Adjusted price is sort of a
total return figure -- price adjusted for splits and dividends -- and is
actually the critical number to consider for performance over long periods
of time. Finance.quothist in Perl provides this attribute as an option.
 
Steve Miller 

Charlie Moad wrote:
> That's great to hear! Thanks for the info. I am just surprised I
> have not seen this response when it has came up on the twisted list.
I, too, find that bizarre since Twisted and Zope were *the* reasons for that
feature.
-- 
Robert Kern
rob...@gm...
"In the fields of hell where the grass grows high
 Are the graves of dreams allowed to die."
 -- Richard Harter

That's great to hear! Thanks for the info. I am just surprised I
have not seen this response when it has came up on the twisted list.
- Charlie
On 12/12/05, Robert Kern <rob...@gm...> wrote:
> Charlie Moad wrote:
> > The way mpl uses the basemap toolkit will not work using
> > setuptools. This is also an issue that twisted runs into. Since
> > matplotlib will be put in one egg folder and basemap will be stuck in
> > another, trying to import matplotlib.toolkits.basemap will yield an
> > error. Just something to think about for down the road, but its
> > probably not a priority now.
>
> That's why setuptools/eggs have the concept of namespace packages. Both t=
he
> matplotlib egg and basemap egg provide the matplotlib.toolkits namespace =
package.
>
> E.g.:
>
> setup(#...
> namespace_packages=3D['matplotlib.toolkits'],
> )
>
> --
> Robert Kern
> rob...@gm...
>
> "In the fields of hell where the grass grows high
> Are the graves of dreams allowed to die."
> -- Richard Harter
>
>
> -------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc. Do you grep through log fi=
les
> for problems? Stop! Download the new AJAX search engine that makes
> searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
> http://ads.osdn.com/?ad_id=3D7637&alloc_id=3D16865&op=3Dclick
> _______________________________________________
> Matplotlib-devel mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
>

Charlie Moad wrote:
> The way mpl uses the basemap toolkit will not work using
> setuptools. This is also an issue that twisted runs into. Since
> matplotlib will be put in one egg folder and basemap will be stuck in
> another, trying to import matplotlib.toolkits.basemap will yield an
> error. Just something to think about for down the road, but its
> probably not a priority now.
That's why setuptools/eggs have the concept of namespace packages. Both the
matplotlib egg and basemap egg provide the matplotlib.toolkits namespace package.
E.g.:
setup(#...
 namespace_packages=['matplotlib.toolkits'],
)
-- 
Robert Kern
rob...@gm...
"In the fields of hell where the grass grows high
 Are the graves of dreams allowed to die."
 -- Richard Harter

 The way mpl uses the basemap toolkit will not work using
setuptools. This is also an issue that twisted runs into. Since
matplotlib will be put in one egg folder and basemap will be stuck in
another, trying to import matplotlib.toolkits.basemap will yield an
error. Just something to think about for down the road, but its
probably not a priority now.
- Charlie
On 12/11/05, Andrew Straw <str...@as...> wrote:
> Hi All,
>
> I've added a hopefully innocuous few lines to matplotlib's setup.py:
>
> +
> +try:
> + from setuptools import setup # use setuptools if possible
> +except ImportError:
> + pass
> +
>
> This will use setuptools.setup() to install matplotlib if you have
> setuptools installed on your system. I assume that if you have
> setuptools installed, you want to use it, hence the change. However, I
> thought this may potentially cause issues for folks, so I wanted to
> announce the change here.
>
> This change should have no effect for those without setuptools. If you
> do have setuptools, it also means that the matplotlib data files are now
> placed in the resulting .egg. I've therefore also modified
> _get_data_path() in lib/matplotlib/__init__.py to support this change.
>
> For more information on setuptools, see
> http://peak.telecommunity.com/DevCenter/setuptools
>
>
> -------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc. Do you grep through log fi=
les
> for problems? Stop! Download the new AJAX search engine that makes
> searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
> http://ads.osdn.com/?ad_id=3D7637&alloc_id=3D16865&op=3Dclick
> _______________________________________________
> Matplotlib-devel mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
>

Charlie Moad wrote:
>FYI, built a bdist_wininst and it worked fine.
>
>
I just tested it too and it works for me with a non-setuptools install,
with a setuptools install, and with a non-setuptools install in which
setuptools was later installed. I think it should be fine.

FYI, built a bdist_wininst and it worked fine.
On 12/12/05, Charlie Moad <cw...@gm...> wrote:
> I just committed my changes. The simplest approach would be to
> specify the matplotlib module package_data, but the current cvs layout
> doesn't tailor to that very well. So I mimicked distutils install
> command to determine where matplotlib is installed. The datapath is
> then defined as $platlib/matplotlib/mpl-data.
> Why this change? If you take a look at
> matplotlib._get_data_path() you will see. This method has grown to
> probably 100 lines of code to check for various cases, e.g. py2exe,
> setuptools, embedding mpl, etc. Now that the data is installed into
> the matplotlib module you could pretty much reduce to 1 line:
> "os.sep.join([os.path.dirname(__file__), 'mpl-data'])". This now
> handles all the cases mentioned above. I left in the initial check
> for the MATPLOTLIBDATA env key to still allow for some flexibility.
> I have tested on posix and w/wo setuptools. I am going to check
> windows right now, but pretty sure it should work. Please check this
> very carefully before next release as it is a pretty major change.
> Let me know if anyone encounters a problem.
>
> Thanks,
> - Charlie
>
> On 12/7/05, John Hunter <jdh...@ac...> wrote:
> > >>>>> "Charlie" =3D=3D Charlie Moad <cw...@gm...> writes:
> >
> > Charlie> Would it be considered cleaner to embed the mpl data into
> > Charlie> the matplotlib module? This would make it easier to
> > Charlie> clean a mpl install. The data path could be expressed
> > Charlie> fairly easily too, as a one-liner:
> >
> > Charlie> os.sep.join([os.path.split(matplotlib.__file__)[0],
> > Charlie> 'matplotlib-data'])
> >
> > Yes, if you can engineer in a way that works with setup w/ and w/o a
> > --prefix arg it would be preferable, in my view.
> >
> > JDH
> >
>

 I just committed my changes. The simplest approach would be to
specify the matplotlib module package_data, but the current cvs layout
doesn't tailor to that very well. So I mimicked distutils install
command to determine where matplotlib is installed. The datapath is
then defined as $platlib/matplotlib/mpl-data.
 Why this change? If you take a look at
matplotlib._get_data_path() you will see. This method has grown to
probably 100 lines of code to check for various cases, e.g. py2exe,
setuptools, embedding mpl, etc. Now that the data is installed into
the matplotlib module you could pretty much reduce to 1 line:
"os.sep.join([os.path.dirname(__file__), 'mpl-data'])". This now
handles all the cases mentioned above. I left in the initial check
for the MATPLOTLIBDATA env key to still allow for some flexibility.
 I have tested on posix and w/wo setuptools. I am going to check
windows right now, but pretty sure it should work. Please check this
very carefully before next release as it is a pretty major change.=20
Let me know if anyone encounters a problem.
Thanks,
- Charlie
On 12/7/05, John Hunter <jdh...@ac...> wrote:
> >>>>> "Charlie" =3D=3D Charlie Moad <cw...@gm...> writes:
>
> Charlie> Would it be considered cleaner to embed the mpl data into
> Charlie> the matplotlib module? This would make it easier to
> Charlie> clean a mpl install. The data path could be expressed
> Charlie> fairly easily too, as a one-liner:
>
> Charlie> os.sep.join([os.path.split(matplotlib.__file__)[0],
> Charlie> 'matplotlib-data'])
>
> Yes, if you can engineer in a way that works with setup w/ and w/o a
> --prefix arg it would be preferable, in my view.
>
> JDH
>

Hi All,
I've added a hopefully innocuous few lines to matplotlib's setup.py:
+
+try:
+ from setuptools import setup # use setuptools if possible
+except ImportError:
+ pass
+
This will use setuptools.setup() to install matplotlib if you have
setuptools installed on your system. I assume that if you have
setuptools installed, you want to use it, hence the change. However, I
thought this may potentially cause issues for folks, so I wanted to
announce the change here.
This change should have no effect for those without setuptools. If you
do have setuptools, it also means that the matplotlib data files are now
placed in the resulting .egg. I've therefore also modified
_get_data_path() in lib/matplotlib/__init__.py to support this change.
For more information on setuptools, see
http://peak.telecommunity.com/DevCenter/setuptools