> Alternatively, if you are only using SymPy interactively, you can clone
the SymPy git repository and run Python (or Jupyter or IPython) from that
directory, without installing it.
Unfortunately, I don't recommend this because that makes jupyter notebooks
appear on the git diff.
There are
On Fri, 3 Mar 2023 at 23:29, Oscar Benjamin wrote:
>
> On Fri, 3 Mar 2023 at 21:32, David Bailey wrote:
> >
> > Oscar,
> >
> > The release of SymPy 1.12 seemed to be very close, but nothing has
> > happened!
> >
> > It doesn't really matter to me, but it would be interesting to explore
> >
On Fri, 3 Mar 2023 at 21:32, David Bailey wrote:
>
> Oscar,
>
> The release of SymPy 1.12 seemed to be very close, but nothing has
> happened!
>
> It doesn't really matter to me, but it would be interesting to explore
> whatever is new.
Hi David,
I should have sent an announcement to the
Oscar,
The release of SymPy 1.12 seemed to be very close, but nothing has
happened!
It doesn't really matter to me, but it would be interesting to explore
whatever is new.
David
--
You received this message because you are subscribed to the Google Groups
"sympy" group.
To unsubscribe
On 26/01/2023 20:48, Oscar Benjamin wrote:
Hi David,
There is nothing on PyPI to install yet but if you are using pip for
installation then you can install the latest development version of
sympy from github like this:
pip install git+https://github.com/sympy/sympy.git@master
That works for
On Thu, Jan 26, 2023 at 1:49 PM Oscar Benjamin
wrote:
> On Thu, 26 Jan 2023 at 20:28, David Bailey wrote:
> >
> > On 26/01/2023 12:56, Oscar Benjamin wrote:
> > > I've opened an issue to track releasing SymPy 1.12:
> > > https://github.com/sympy/sympy/issues/24601
> > >
> > I went ahead and
On Thu, 26 Jan 2023 at 20:28, David Bailey wrote:
>
> On 26/01/2023 12:56, Oscar Benjamin wrote:
> > I've opened an issue to track releasing SymPy 1.12:
> > https://github.com/sympy/sympy/issues/24601
> >
> I went ahead and installed what I thought would be sympy 1.12, but ended
> up
On 26/01/2023 12:56, Oscar Benjamin wrote:
I've opened an issue to track releasing SymPy 1.12:
https://github.com/sympy/sympy/issues/24601
I went ahead and installed what I thought would be sympy 1.12, but ended
up re-installing 1.11.1 !
David
--
You received this message because you are
I've opened an issue to track releasing SymPy 1.12:
https://github.com/sympy/sympy/issues/24601
--
You received this message because you are subscribed to the Google Groups
"sympy" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to
I can help. I have also considerable amount of free time.
On Friday, May 17, 2013 7:10:05 AM UTC+5:30, Aaron Meurer wrote:
Is anyone willing to commit some time over the next few weeks or so to
help get a release out?
If so, then I think we should do it. It will make things easier for
I can help having good amount of free time till the end of July.
On Fri, May 17, 2013 at 4:23 PM, Ramana Venkata idlike2dr...@gmail.comwrote:
I can help. I have also considerable amount of free time.
On Friday, May 17, 2013 7:10:05 AM UTC+5:30, Aaron Meurer wrote:
Is anyone willing to
I'd be willing to help out in whatever capacity I can.
Cheers,
~ Luke
On Thursday, May 16, 2013 9:40:05 PM UTC-4, Aaron Meurer wrote:
Is anyone willing to commit some time over the next few weeks or so to
help get a release out?
If so, then I think we should do it. It will make things
I'm willing to help out too.
On Friday, 17 May 2013 11:40:05 UTC+10, Aaron Meurer wrote:
Is anyone willing to commit some time over the next few weeks or so to
help get a release out?
If so, then I think we should do it. It will make things easier for
Ondrej and I for our SciPy
OK, well the first thing that needs to be done is we need to go through all
the pull requests and make sure that any that should be merged before a
release are merged.
Second, we need to go through all issues with the milestone-release0.7.3
flag and resolve them (
On Sat, Dec 3, 2011 at 6:53 AM, Aaron Meurer asmeu...@gmail.com wrote:
The biggest problem with Jenkins in my opinion is that it has such a
terrible user interface.
SymPy-Bot is nice in that it allows completely distributed testing.
The script is so simple and self-contained that anyone can
Am 03.12.2011 11:39, schrieb Vladimir Perić:
[...]
Yep, I had found your work through Google, but only after sending my
messages, so I thought aw heck, he'll talk if he's still behind it, I
don't want to pressure Vladimir into coming forth :-)
Jo, if you are interested in playing around
I agree with Vladimir that using Jenkins is the right solution. But for the
moment I've written a very ugly and short script to automate the pull
request testing. I'll start running it today (It's still not tested)
Stefan
On 3 December 2011 12:50, Joachim Durchholz j...@durchholz.org wrote:
Am
I forgot copy the link to the script:
https://github.com/sympy/sympy-bot/pull/74
On 3 December 2011 14:04, krastanov.ste...@gmail.com
krastanov.ste...@gmail.com wrote:
I agree with Vladimir that using Jenkins is the right solution. But for
the moment I've written a very ugly and short script
The biggest problem with Jenkins in my opinion is that it has such a
terrible user interface.
SymPy-Bot is nice in that it allows completely distributed testing.
The script is so simple and self-contained that anyone can just clone
it and run it (I guess there are a few Python dependencies to
I went ahead and registered for the Shining Panda thing, since it was
free. There apparently is a waiting list for the free open source
plan, and we are number 6. I'll let you know when it goes online.
Aaron Meurer
On Sat, Dec 3, 2011 at 7:53 AM, Aaron Meurer asmeu...@gmail.com wrote:
The
It looks like shining panda gives one hour per day free to foss projects.
Is this sufficient for our needs? Or rather, how much compute time would a
nice testing system require?
On Sat, Dec 3, 2011 at 8:57 AM, Aaron Meurer asmeu...@gmail.com wrote:
I went ahead and registered for the Shining
I've started the script I've written about in the previous mail. Now every
6 hours all open mergeable pull requests that are not tested will be tested
in python 2.7.1.
The computer I'm using will continue to do the tests unless there is a
hardware problem (which is possible as there are some
Am 03.12.2011 15:53, schrieb Aaron Meurer:
The biggest problem with Jenkins in my opinion is that it has such a
terrible user interface.
In configuration, or when reading and interpreting test results?
--
You received this message because you are subscribed to the Google Groups
sympy group.
On Sat, Dec 3, 2011 at 10:47 AM, Joachim Durchholz j...@durchholz.org wrote:
Am 03.12.2011 15:53, schrieb Aaron Meurer:
The biggest problem with Jenkins in my opinion is that it has such a
terrible user interface.
In configuration, or when reading and interpreting test results?
I haven't
Probably not, if we want to test all the pull requests.
But if we set up a system like what I was talking about where the
server can server out tests, then I too can probably set up an old
computer or two to do testing with. Old computers like this are
actually not that hard to come by (indeed,
Le samedi 03 décembre 2011 à 11:39 +0100, Vladimir Perić a écrit :
On Sat, Dec 3, 2011 at 8:18 AM, Joachim Durchholz j...@durchholz.org wrote:
That take a test from the queue and distribute it, deal with downtimes and
failures, do some reporting... that sounds like a wheel already invented by
Am 03.12.2011 20:48, schrieb Aaron Meurer:
Right now, Stefan's script works only for his machine, if I were to
run the same script, we would just get duplicate reports (unless we
timed them to be offset or something). So we really need to get some
poling mechanism implemented,
This sounds
On Sat, Dec 3, 2011 at 3:35 PM, Joachim Durchholz j...@durchholz.org wrote:
Am 03.12.2011 20:48, schrieb Aaron Meurer:
Right now, Stefan's script works only for his machine, if I were to
run the same script, we would just get duplicate reports (unless we
timed them to be offset or something).
Hi,
On 30 November 2011 22:50, Aaron Meurer asmeu...@gmail.com wrote:
Yeah, I'm totally free until the end of January, starting in two
weeks. We'll probably need to do some cleaning up from pull requests
and stuff after GCI too (e.g., right now, I'm basically ignoring all
non-critical
On Fri, Dec 2, 2011 at 2:22 AM, Mateusz Paprocki matt...@gmail.com wrote:
Hi,
On 30 November 2011 22:50, Aaron Meurer asmeu...@gmail.com wrote:
Yeah, I'm totally free until the end of January, starting in two
weeks. We'll probably need to do some cleaning up from pull requests
and stuff
On Fri, Dec 2, 2011 at 5:05 PM, Aaron Meurer asmeu...@gmail.com wrote:
On Fri, Dec 2, 2011 at 2:22 AM, Mateusz Paprocki matt...@gmail.com wrote:
Hi,
On 30 November 2011 22:50, Aaron Meurer asmeu...@gmail.com wrote:
Yeah, I'm totally free until the end of January, starting in two
weeks.
On Fri, Dec 2, 2011 at 10:57 AM, Vladimir Perić vlada.pe...@gmail.com wrote:
On Fri, Dec 2, 2011 at 5:05 PM, Aaron Meurer asmeu...@gmail.com wrote:
On Fri, Dec 2, 2011 at 2:22 AM, Mateusz Paprocki matt...@gmail.com wrote:
Hi,
On 30 November 2011 22:50, Aaron Meurer asmeu...@gmail.com wrote:
On Fri, Dec 2, 2011 at 10:42 AM, Aaron Meurer asmeu...@gmail.com wrote:
On Fri, Dec 2, 2011 at 10:57 AM, Vladimir Perić vlada.pe...@gmail.com wrote:
On Fri, Dec 2, 2011 at 5:05 PM, Aaron Meurer asmeu...@gmail.com wrote:
On Fri, Dec 2, 2011 at 2:22 AM, Mateusz Paprocki matt...@gmail.com wrote:
On the topic of testing: What is the reason that the pull requests are not
all tested automatically? And tox run every week or so. I thought that all
the code for the automated testing is already written. And there is that
google app engine instance. If it's only a processing power issue I have a
On Dec 2, 2011, at 1:49 PM, Ondřej Čertík ondrej.cer...@gmail.com wrote:
On Fri, Dec 2, 2011 at 10:42 AM, Aaron Meurer asmeu...@gmail.com wrote:
On Fri, Dec 2, 2011 at 10:57 AM, Vladimir Perić vlada.pe...@gmail.com
wrote:
On Fri, Dec 2, 2011 at 5:05 PM, Aaron Meurer asmeu...@gmail.com wrote:
On 2 December 2011 22:23, Aaron Meurer asmeu...@gmail.com wrote:
On Dec 2, 2011, at 1:49 PM, Ondřej Čertík ondrej.cer...@gmail.com
wrote:
On Fri, Dec 2, 2011 at 10:42 AM, Aaron Meurer asmeu...@gmail.com
wrote:
On Fri, Dec 2, 2011 at 10:57 AM, Vladimir Perić vlada.pe...@gmail.com
wrote:
2011/12/2 krastanov.ste...@gmail.com krastanov.ste...@gmail.com:
On the topic of testing: What is the reason that the pull requests are not
all tested automatically? And tox run every week or so. I thought that all
That's the plan, but I got busy to set this up, so it's not done yet.
the code
2011/12/2 Ondřej Čertík ondrej.cer...@gmail.com:
2011/12/2 krastanov.ste...@gmail.com krastanov.ste...@gmail.com:
On the topic of testing: What is the reason that the pull requests are not
all tested automatically? And tox run every week or so. I thought that all
That's the plan, but I got
Oh, and if someone could go through and add priority labels and code
in labels to all the sympy-bot issues
(https://github.com/sympy/sympy-bot/issues?sort=createddirection=descstate=open),
then we can put these in the next round for code-in, and maybe some of
them will be fixed through that. I
We need to implement sympy-bot work to do automated testing, but other
than that, I think we just need computing power. Ondřej was going to use
linode or something, but if you can donate computing power, that would be
great.
Aaron Meurer
Sent from my iPhone.
On Dec 2, 2011, at 2:19 PM,
That take a test from the queue and distribute it, deal with downtimes
and failures, do some reporting... that sounds like a wheel already
invented by Hudson/Jenkins. And if Jenkins doesn't work for Python
stuff, test-on-commit isn't exactly an uncommon demand, so something for
Python should
A company named Shining Panda offers free Jenkins hosts for Python to
FLOSS projects.
See https://www.shiningpanda.com/pricing/
--
You received this message because you are subscribed to the Google Groups
sympy group.
To post to this group, send email to sympy@googlegroups.com.
To unsubscribe
Yeah, I'm totally free until the end of January, starting in two
weeks. We'll probably need to do some cleaning up from pull requests
and stuff after GCI too (e.g., right now, I'm basically ignoring all
non-critical non-gci pull requests).
Aaron Meurer
On Wed, Nov 30, 2011 at 10:13 AM, Vladimir
On Nov 16, 2:41 am, Mateusz Paprocki matt...@gmail.com wrote:
By the way, where are you giving the tutorial at?
SciPy.In in Mumbai (Bombay), India.
\o/
Have fun in Mumbai Mateusz! Its a really friendly place. Go easy
on the local street food though ;-)
BTW, you can mention to the students
In pull request 673 there is a new plotting module. It's functional and
Aaron and Ondrej were interested in merging it before the next release.
It seems that the release will be sooner than expected. Does this change
the plans about the pull request 673? As I've said the code is mostly
ready, but
On Tue, Nov 15, 2011 at 9:20 PM, krastanov.ste...@gmail.com
krastanov.ste...@gmail.com wrote:
In pull request 673 there is a new plotting module. It's functional and
Aaron and Ondrej were interested in merging it before the next release.
It seems that the release will be sooner than expected.
On Tue, Nov 15, 2011 at 1:31 PM, Vladimir Periæ vlada.pe...@gmail.com wrote:
On Tue, Nov 15, 2011 at 9:20 PM, krastanov.ste...@gmail.com
krastanov.ste...@gmail.com wrote:
In pull request 673 there is a new plotting module. It's functional and
Aaron and Ondrej were interested in merging it
On Tue, Nov 15, 2011 at 12:37 PM, Mateusz Paprocki matt...@gmail.com wrote:
Hi,
On 14 November 2011 23:02, Mateusz Paprocki matt...@gmail.com wrote:
Hi,
Is there a chance we could release SymPy 0.7.2 in two weeks? Early
December I will give a tutorial about SymPy and I would like to take
So I saw that Vladimir removed the milestone on some issues, but he
wasn't nearly as aggressive as I would have hoped, so I just went
through myself, and removed the milestone from many issues, and
postponed some others. What remains are eight issues, two of which
could be further postponed if
On Dec 20, 3:54 am, Aaron S. Meurer asmeu...@gmail.com wrote:
Everything including the docs works for me in Mac OS X 10.6.2. It installed
fine, the isympy shortcut works in my path, and the tests all pass.
To David: I have sphinx installed through fink, which I think is a
requirement for
I just released a release candidate, please test it [1]. I especially
don't know whether the windows installer [2] works, it would be great
if someone could try it out.
Vinzent
[1] http://sympy.googlecode.com/files/sympy-0.6.6.rc1.tar.gz
[2]
Everything including the docs works for me in Mac OS X 10.6.2. It installed
fine, the isympy shortcut works in my path, and the tests all pass.
To David: I have sphinx installed through fink, which I think is a requirement
for the docs to work. There are quite a few errors and warnings
On Fri, Dec 11, 2009 at 12:41 PM, Aaron S. Meurer asmeu...@gmail.com wrote:
A couple of other things:
SymPy 0.6.5 never got pushed to fink, and I don't know if it ever made it to
any of the other package managers. Ondrej mentioned something about making a
Debian package for it (it's
Le vendredi 11 décembre 2009 à 12:48 -0800, Ondrej Certik a écrit :
On Fri, Dec 11, 2009 at 12:41 PM, Aaron S. Meurer asmeu...@gmail.com wrote:
Also, we should mention in the change log the things that are depreciated,
namely, the old assumptions. All new code should use new assumptions,
Le vendredi 11 décembre 2009 à 14:24 -0800, Ondrej Certik a écrit :
On Fri, Dec 11, 2009 at 2:17 PM, Ronan Lamy ronan.l...@gmail.com wrote:
Le vendredi 11 décembre 2009 à 12:48 -0800, Ondrej Certik a écrit :
On Fri, Dec 11, 2009 at 12:41 PM, Aaron S. Meurer asmeu...@gmail.com
wrote:
On Fri, Dec 11, 2009 at 4:36 PM, Ronan Lamy ronan.l...@gmail.com wrote:
Le vendredi 11 décembre 2009 à 14:24 -0800, Ondrej Certik a écrit :
On Fri, Dec 11, 2009 at 2:17 PM, Ronan Lamy ronan.l...@gmail.com wrote:
Le vendredi 11 décembre 2009 à 12:48 -0800, Ondrej Certik a écrit :
On Fri, Dec
On 10 déc, 02:36, asmeurer asmeu...@gmail.com wrote:
I modified it (added --since=sympy-0.6.5 to the git log command) and I
get:
dhcp-baca-10:sympy aaronmeurer(master$)$ruby ~/Downloads/git-rank-
contributors.sh -v
Vinzent Steinberg vinzent.steinb...@gmail.com: 54995 lines of diff
Aaron
On Dec 8, 3:06 am, Ondrej Certik ond...@certik.cz wrote:
I reviewed all patches here.
[2]http://code.google.com/p/sympy/issues/list?q=NeedsBetterPatch
Now we have 22 patches, that need more work. Lots of times it's some
small additions, like tests or doctests, so anyone can help with this.
On Dec 9, 2009, at 4:45 PM, Vinzent Steinberg wrote:
On Dec 8, 3:06 am, Ondrej Certik ond...@certik.cz wrote:
I reviewed all patches here.
[2]http://code.google.com/p/sympy/issues/list?q=NeedsBetterPatch
Now we have 22 patches, that need more work. Lots of times it's some
small
On Wed, Dec 9, 2009 at 3:45 PM, Vinzent Steinberg
vinzent.steinb...@googlemail.com wrote:
On Dec 8, 3:06 am, Ondrej Certik ond...@certik.cz wrote:
I reviewed all patches here.
[2]http://code.google.com/p/sympy/issues/list?q=NeedsBetterPatch
Now we have 22 patches, that need more work. Lots
There is this script to rank people by diff size (though I think it will need
to be modified to only go since the sympy-0.6.5 tag).
http://git-wt-commit.rubyforge.org/git-rank-contributors
Aaron Meurer
On Dec 9, 2009, at 4:45 PM, Vinzent Steinberg wrote:
On Dec 8, 3:06 am, Ondrej Certik
I modified it (added --since=sympy-0.6.5 to the git log command) and I
get:
dhcp-baca-10:sympy aaronmeurer(master$)$ruby ~/Downloads/git-rank-
contributors.sh -v
Vinzent Steinberg vinzent.steinb...@gmail.com: 54995 lines of diff
Aaron Meurer asmeu...@gmail.com: 15582 lines of diff
Chris Smith
I'm getting a failure on windows which is kind of weird as it is
complaining about True:
__ sympy\queries\tests\test_query.py:test_type_extensibility
___
File c:\documents and settings\chris\sympy\sympy\queries\tests
\test_query.py, line 963, in test_type_extensibility
On Sun, Dec 6, 2009 at 6:35 AM, Vinzent Steinberg
vinzent.steinb...@googlemail.com wrote:
If you want to help, you can have a look at the remaining patches to
be reviewed [1] or improve existing patches [2], thanks!
Vinzent
[1] http://code.google.com/p/sympy/issues/list?q=NeedsReview
I
If you want to help, you can have a look at the remaining patches to
be reviewed [1] or improve existing patches [2], thanks!
Vinzent
[1] http://code.google.com/p/sympy/issues/list?q=NeedsReview
[2] http://code.google.com/p/sympy/issues/list?q=NeedsBetterPatch
--
You received this message
Vinzent Steinberg wrote:
If you want to help, you can have a look at the remaining patches to
be reviewed [1] or improve existing patches [2], thanks!
Thanks for managing this release, Vinzent. I'll get time to help out
when I finish my exams (next week!).
Fabian
Vinzent
[1]
Also, I'm assuming we need to go through all of the Milestone-Release0.6.6
issues [1], and either fix them or postpone them. For example, I think we
should see if we can fix the --random test failures (I narrowed one down in
issue 1747), though some like 1244 will be best to just wait for the
67 matches
Mail list logo
