When preparing a portion of the Sage library as a distribution package,
dependencies matter.
*Build-time dependencies: *If the portion of the library contains any
Cython modules, these modules are compiled during the wheel-building phase
of the distribution package. If the Cython module uses "c
Another fact that annoys me about monorepo is the versioning of the components.
There is no right or wrong here, just preferences.
In the monorepo scenario you’ll have subcomponents released and they (usually)
will all have matching version numbers.
This is easy to figure out what you should use
> On 11/10/2021, at 15:07, Matthias Koeppe wrote:
>
> On Sunday, October 10, 2021 at 5:49:05 PM UTC-7 François Bissey wrote:
> To package these I pull the full tree :( and then I don’t go to
> SAGE_ROOT/pkgs/pkg_name and build from there.
> If I want to patch it doesn’t work from there becau
On Sunday, October 10, 2021 at 6:00:50 PM UTC-7 wst...@gmail.com wrote:
> it is possible to use Git to only pull a selected directory
> (or directories) from a Git repo with no history. See, e.g., the
> discussion of "sparse checkout" here.
>
>
> https://stackoverflow.com/questions/600079/how-d
On Sunday, October 10, 2021 at 5:49:05 PM UTC-7 François Bissey wrote:
> To package these I pull the full tree :( and then I don’t go to
> SAGE_ROOT/pkgs/pkg_name and build from there.
> If I want to patch it doesn’t work from there because patch doesn’t apply
> across symbolic links. So, inste
On Sunday, October 10, 2021 at 7:04:22 PM UTC-7 François Bissey wrote:
> > On 11/10/2021, at 15:02, Matthias Koeppe wrote:
> > https://trac.sagemath.org/ticket/32062 is for adding this (and
> publishing to PyPI) as an automatic step on GH Actions.
>
> I am presuming the upload will be automati
> On 11/10/2021, at 15:02, Matthias Koeppe wrote:
>
> On Sunday, October 10, 2021 at 5:49:05 PM UTC-7 François Bissey wrote:
> For proper releases, I am hoping for separate tarballs (eventually) which
> means that there won’t be any issues with symbolic links.
>
> Anyone can create the packa
On Sunday, October 10, 2021 at 5:49:05 PM UTC-7 François Bissey wrote:
> For proper releases, I am hoping for separate tarballs (eventually) which
> means that there won’t be any issues with symbolic links.
>
Anyone can create the package tarballs by just using "setup.py sdist" in
the distribut
> On 11/10/2021, at 14:00, William Stein wrote:
>
> On Sun, Oct 10, 2021 at 5:49 PM François Bissey wrote:
>>
>> One annoying thing about monorepo from a downstream perspective - but only
>> for people crazy enough to package a development branch (OK that would be me
>> and not many other
On Sun, Oct 10, 2021 at 5:49 PM François Bissey wrote:
>
> One annoying thing about monorepo from a downstream perspective - but only
> for people crazy enough to package a development branch (OK that would be me
> and not many other people :) ).
> The split packages have their setup.py or equiv
One annoying thing about monorepo from a downstream perspective - but only for
people crazy enough to package a development branch (OK that would be me and
not many other people :) ).
The split packages have their setup.py or equivalent in SAGE_ROOT/pkgs/pkg_name
and some links to the single sag
As we are making progress on preparing the Sage library for modularization (
https://trac.sagemath.org/ticket/29705), here's a discussion of three
things that need to be decided whenever a portion of the Sage library is
modularized:
*(1) Namespace:* Will it be imported as (+) "from sage.hermeneu
On Sunday, October 10, 2021 at 1:57:55 PM UTC-7 Nils Bruin wrote:
> I think it is worthwhile to have something like "sage --pip install --user
> ..." work [...] The target audience also has no knowledge of venv [...]
>
The user scheme (--user) is an outdated mechanism. Python, by design,
disabl
On Sunday, October 10, 2021 at 1:57:55 PM UTC-7 Nils Bruin wrote:
> a good document telling exactly what to execute should be given
>
We have tickets for this, including https://trac.sagemath.org/ticket/29784,
which need contributions.
--
You received this message because you are subscrib
Reiterating:
I think it is worthwhile to have something like "sage --pip install --user
..." work, because people may well have a sage-install on which they don't
have write permission, or on which they don't *want* to write. If it needs
to be something else, like "sage --pipuser install ..." t
On Sunday, September 26, 2021 at 10:44:14 AM UTC-7 Matthias Koeppe wrote:
>
> *2. Do not import CLASS just to run an isinstance(..., CLASS); likewise,
> remove uses of is_CLASS functions*
>
> Instead, create abstract base classes that can be imported without pulling
> in the actual implementatio
As we are making progress on preparing the Sage library for modularization
(https://trac.sagemath.org/ticket/29705), here's a discussion of three
things that need to be decided whenever a portion of the Sage library is
modularized:
*(1) Namespace:* Will it be imported as (+) "from sage.hermeneu
On Sun, Oct 10, 2021 at 2:11 PM Antonio Rojas wrote:
> Yes, that matches the emails I have received. So the missing emails were
> never sent (eg. every comment in #32656 -in which I'm CC'd- after my
> comment #9)
>
I looked in the logs, and I am sure I e.g. can trace the moment the emails
on htt
On Sun, 10 Oct 2021, 13:10 Michael Orlitzky, wrote:
> On 2021-10-10 04:41:19, Antonio Rojas wrote:
> > Hi all,
> > I'm having an issue for a long time where many of the email
> > notifications I should be receiving from trac are getting lost (many
> > being over 50%) Is anybody else experienc
On 2021-10-10 04:41:19, Antonio Rojas wrote:
> Hi all,
> I'm having an issue for a long time where many of the email
> notifications I should be receiving from trac are getting lost (many
> being over 50%) Is anybody else experiencing this?
I think these are all relayed through sagemath.openbs
Yes, I experienced this too on one machine; I ended up making a new keypair
and putting the public key on the trac server
On Sun, 10 Oct 2021, 12:39 Antonio Rojas, wrote:
> Hi all,
> I'm unable to push to git-trac since updating to openssh 8.8, getting a
> permission denied error. This versio
Hi,
I run the mail server sending trac emails. I don't think I saw your emails
ever stuck in the queue. Anyhow, please email me the addresses to look for
in the logs, so that I can tell you more.
Cheers,
Dima
On Sun, 10 Oct 2021, 12:41 Antonio Rojas, wrote:
> Hi all,
> I'm having an issue for a
Hi all,
I'm having an issue for a long time where many of the email notifications
I should be receiving from trac are getting lost (many being over 50%). I
thougt it might be a problem with my mail provider, but the same thing
happens after changing to a different address. Is anybody else exper
Hi all,
I'm unable to push to git-trac since updating to openssh 8.8, getting a
permission denied error. This version disables RSA/SHA1 signatures by
default [1], is it possible that the server is using that to chack the keys?
[1] https://www.openssh.com/txt/release-8.8
--
You received this m
24 matches
Mail list logo
