#9739: Forex trading - Expert
-------------------------------+--------------------------------------------
Reporter: mpatel | Owner: mvngu
Type: task | Status: needs_work
Priority: trivial | Milestone: sage-4.6.2
Component: build | Keywords: currency trading, forex
analysis, forex trading, online forex trading
Author: Mitesh Patel | Upstream: N/A
Reviewer: Robert Bradshaw | Merged:
Work_issues: |
-------------------------------+--------------------------------------------
Changes (by forextrading11):
* cc: drkirkby, jhpalmieri, leif, robertwb, jdemeyer (removed)
* cc: Marian, Rosales (added)
* component: doctest => build
* priority: blocker => trivial
* keywords: doctest scripts => currency trading, forex analysis, forex
trading, online forex trading
* type: defect => task
Old description:
> When we test
>
> `/path/to/foo.py`
>
> `sage-doctest` writes
>
> `SAGE_TESTDIR/.doctest_foo.py`
>
> runs the new file through `python`, and deletes it. This can cause
> collisions when we test in parallel multiple files with the same
> basename, e.g., `__init__`, `all`, `misc`, `conf`, `constructor`,
> `morphism`, `index`, `tests`, `homset`, `element`, `twist`, `tutorial`,
> `sagetex`, `crystals`, `cartesian_product`, `template`, `ring`, etc.
>
> There's a similar problem with testing non-library files, which `sage-
> doctest` first effectively copies to `SAGE_TESTDIR`.
>
> See [http://groups.google.com/group/sage-
> devel/browse_thread/thread/0239f712a39fce4a/367bfc0d83c0e9b8#367bfc0d83c0e9b8
> sage-devel] for background.
>
> This ticket may help with some of the doctesting problems discussed on
> the Sage mailing lists. Related tickets: #9224, #9225, #9449.
New description:
[[Image(http://www.forextradingcoach-simon.com/wp-content/uploads/2010/01
/forex-trading.jpg)]]
If you are an expert on '''[http://www.forexinsider.co.uk forex
trading]''' you know already what it is to be a forex trader and the
process that you have been in to is not easy but if you know how to handle
tough tradings then it would be good for you because it will be who you
are when you mature in this type of business.
--
Comment:
Replying to [ticket:9739 mpatel]:
> When we test
>
> `/path/to/foo.py`
>
> `sage-doctest` writes
>
> `SAGE_TESTDIR/.doctest_foo.py`
>
> runs the new file through `python`, and deletes it. This can cause
> collisions when we test in parallel multiple files with the same
> basename, e.g., `__init__`, `all`, `misc`, `conf`, `constructor`,
`morphism`, `index`, `tests`, `homset`, `element`, `twist`, `tutorial`,
`sagetex`, `crystals`, `cartesian_product`, `template`, `ring`, etc.
>
> There's a similar problem with testing non-library files, which `sage-
doctest` first effectively copies to `SAGE_TESTDIR`.
>
> See [http://groups.google.com/group/sage-
devel/browse_thread/thread/0239f712a39fce4a/367bfc0d83c0e9b8#367bfc0d83c0e9b8
sage-devel] for background.
>
> This ticket may help with some of the doctesting problems discussed on
the Sage mailing lists. Related tickets: #9224, #9225, #9449.
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/9739#comment:35>
Sage <http://www.sagemath.org>
Sage: Creating a Viable Open Source Alternative to Magma, Maple, Mathematica,
and MATLAB
--
You received this message because you are subscribed to the Google Groups
"sage-trac" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/sage-trac?hl=en.
