On Wednesday, 22 January 2025 at 20:30:46 UTC-8 jackson...@gmail.com wrote:
I had a similar thought but didn’t know if it was possible. I don’t really
understand the idea of being religious about not touching someone’s PR if
they were the one that opened it. Surely just getting the code finished
I had a similar thought but didn’t know if it was possible. I don’t really
understand the idea of being religious about not touching someone’s PR if
they were the one that opened it. Surely just getting the code finished and
merged is more important, and being able to rebase rather than abandoning
When we were on trac, if there was a PR that had been dormant, but was
close to completion, someone else could rebase it, and make the necessary
changes to pull it across the finish line. I'd like to see that happen in
our new system, instead of just closing these PRs. Is that possible? My
i
Yes,. I also have the M1 files in /opt. Is there some way of removing the
old inter brew files? This was an artifact of moving to the new laptop and
just moving the system over. I suspet that the best thing to do is to
reset the system and restore just necessary files from the backup, but I
I would be against automatically closing stale issues just because
realistically we aren't closing issues that fast (I would love if all Sage
issues were resolved in 90 days, but I don't think that is realistic right
now). Perhaps as a first step for dealing with all the open issues would be
do
As a comparision, in void-packages there is the following policy:
- an issue (or PR) with 90 days of inactivity is labeled "stale" and will send
a notification.
- any activity in the issue will reset the "stale" label, so an author can
just make a status report on receipt of the notification to
On Wed, Jan 22, 2025 at 9:48 AM kcrisman wrote:
>
> This would be a change in (perhaps not official) policy from Trac.
> Since PRs are separated from issues on GH (which wasn't really the case on
> Trac), a change might make sense. However, my opinion (for whatever it's
> worth) is that this is
To be clear, my proposal isn't that PRs can't take months or years. It's simply
that if changes are requested and the developer doesn't respond for several
months (so no progress on the ticket at all) then the PR is closed but can be
reopened (even by the person who made the PR ideally, if GitHu
It seems you have an obsolete version of Homebrew in /usr/local - the one for
M1 installs itself to /opt, normally speaking.
On 21 January 2025 19:10:55 GMT-06:00, David Einstein wrote:
>Macosx 15.1.1 M1 laptop
>
>I probably messed something up with my python setup but I cannot figure out
>wha
This would be a change in (perhaps not official) policy from Trac. Since
PRs are separated from issues on GH (which wasn't really the case on Trac),
a change might make sense. However, my opinion (for whatever it's worth)
is that this is not really necessary, and could lead to useful code bein
If you want to plot a list of points, there are several ways to do so,
including points() and list_plot().
def f1(x): return sum(i for i in range(x))
L = [(n,f1(n)) for n in [2..4]]
list_plot(L) # or points(L)
--
You received this message because you are subscribed to the Google Groups
"sage-d
11 matches
Mail list logo
